I'm wondering why my Chrome browser doesn't show when I start testing my angularjs app with protractor. It does execute the test though. I can see the output on my console.
However, if I change the value of browserName to point to firefox and rerun protractor, Firefox will fire up. I'll also see protractor doing its test on the browser.
I also had the impression that my Chrome was not showing up, but I just did not see it as I had too many open Chrome browser windows to even notice the one extra. The real reason I did not see it, was, that I was in full screen mode and the chrome window could not go to the forground as MacOS does not always allow this to happen.
For me I quit my usual Chrome session and then I saw that there was actually a new Chrome session appearing as I started the tests. (I know this is so obvious, but after a long day at work the most obvious things can sometimes lead to be puzzled. So this answer is for the ones who just happened have a bad day ;) )
Related
When there is an error because of X, in Firefox I can only detect this by looking at the console. The components still render. I've had this happen on other projects too, on different computers, making me think this is something I am going to have to address specifically for FF.
Versus in Chrome, where the helpful "error component" (IDK what this is called) renders, definitely making the developer aware. I've attached an image of this.
It's the screen that says this at the bottom: "This screen is visible only in development. It will not appear if the app crashes in production. Open your browser’s developer console to further inspect this error. Click the 'X' or hit ESC to dismiss this message."
I really want this to appear in FF. Any clue how? I do have React devtools installed, but that is not the thing driving this, as you don't even need that tool in Chrome to see this rendered.
This was the cause of an extension getting in the way.
I solved this by disabling a handful of extensions at a time until I got the error screen to load. Then I reversed the process until I narrowed it down to one extension.
The culprit was a form auto-fill extension.
In my setup, I am running my tests for CucumberWithSerenity.class
The issue is after execution of my tests with safari browser, safari does not clear the cookies and other related data. e.g. After login steps are completed, i have to search for a user and set the user so i get relevant sections. But safari retains the set user information from previous test execution. To address this issue, i have set the following in serenity.properties file : safari.options.useCleanSession=true
however, this does not seem to work.
On other browsers, i do not have such an issue. Am i implementing the property incorrectly?
Are there other options in ensuring that every time safari browser is launched, i have fresh new session?
Can you please provide an example?
For some reason the iPhone devices are never able to load the url requested by Protractor, they always show a blank page. It tries to load the url several times and then gives up.
The other BrowerStack devices all seem to work, including Windows, Android, and Safari/Macbook.
Has anyone encountered a similar problem?
For reference, we're using Protractor v2.2.0 (have not been able to updated because we're stuck in an old version of NodeJS, but we could try if that is the cause of the issue).
weirdest thing just happened. My angular app was working fine until last night. This morning, when I run it, it doesn't work on Chrome. I haven't modified anything to the code, and I see no errors on the developer console. What makes it even more weird is, the app works just fine all other browsers and even in incognito mode in Chrome. I tried disabling some extensions but that didn't do the trick either. On the surface, what seems to be the problem is that the any paths following the hashtag is not being populated whether I use ui.router or ngroute. Manually typing the paths does not work either. Does anybody have the same problem? What is going on?!
Just clearing cache didn't work. I had to to clear the cookies and plugin data as well. I'm thinking it might be related to recent Auth0 implementation. Will need to look into it so the problem doesn't occur again. For now though, I will close the question.
I have a web-page written using AngularJS. When I open it using IE9, the top menu's templates aren't executed at all. However when I open the developer console in IE9 and reload, it all suddenly starts working fine and keeps working even if I close the console.
Can it be due to some "clever" IE9 optimizations, which are disabled when the console is open?
Has anyone encountered the same problem?
Is there something I can do about it? It seems impossible to debug it, since it works correctly when I am debugging it...
It's probably because you have used console.log used somewhere in the code which throws an error when the console is not active.