Suppose the test fails due to an error from some other library or some service fails, Nightwatch seem to not care about such situation and doesn't fail gracefully leaving behind hanging selenium session. Also, the xml report is not generated.
This is not reported on TeamCity as a failure.
Is there a config item which I can set or do something my own to take care of such exceptions?
Related
It's a weird bug that I am experiencing.
My test fails due to a detached element from DOM(this is not the issue) and it auto-triggers a retry since I have retries enabled and set the number of attempts to 2.
However, as soon as cypress begins executing the second attempt, I am getting the following uncaught exception.
The point is, cypress passes the test where the uncaught exception occurred during the second attempt.
It's causing me to believe that the tests have passed, whereas, in reality, no cypress commands were executed during the second attempt.
I am unable to reproduce this in any other code, and unfortunately, cannot share the scripts due to company policy.
Any tips, resolution, debug guidance here would be helpful.
Sometimes, for whatever reason, one of the tests in cypress will get stuck and continue to run indefinitely until I manually stop the test suite. It completely ignores any timeouts already set up in cypress.
What is the best way to safeguard and automatically fail just that one test -- without halting the entire test suite?
So I've noticed that the CLI option --continue is often used to handle test failures but it's not specific to them. Is there a means by which I can handle ONLY test failures and not other types of Task failures? If another non-test task fails that would seem to be something worth halting the build over even if tests are not in that specific instance. Also, my integration tests seem to be ignoring it. My setup is the one specified here, in this HOWTO:
http://bit.ly/1S5PKlr
How do you (or even can you) amend the expected HTTP status codes in a Visual Studio Web Performance Test?
I'm checking some new bits of a clients site, so using some Visual Studio Web Performance Tests to drive the pages.
Run the tests and the expected actions occur on the server ... BUT the tests are failing
The reason is there are a few hidden links to some missing GIF files, which are returning a 404 status
I can't get the client to add the files, but I don't want to check the various tests each time to check whether the "fail" is one of the expected 404's, or a real fail
In the properties of the request you can change "Expected HTTP Status Code" to the expected (Int32) Http Status Code.
Instead of expecting a different status code you can write a web test plugin that removes dependant requests. Basically the plugin scans the dependant requests and any that match some criteria are removed. I have done this on a few performance test projects to avoid getting test failures for things that I know would fail every test. Of course your test report should describe the missing files. See also See http://blogs.msdn.com/b/edglas/archive/2008/07/17/dependent-request-filter.aspx
My email notifier in teamcity works well when the compilation fails. I have it set to notify me of failures and also the first success after the failure.
But when one test fails, I don't get an email. The build is set to fail when at least one test doesn't pass. I have nice red dot next to the build number.
The weird thing is, sometimes I get a success email after the test has been fixed, but not always. Does anyone know of any logs I can use to figure out why I'm not getting my email?
Here is another weird thing: I set the notifications to send me an email when the build fails and when the build succeeds. When the tests fail, I still get no email.
I do get notified properly in the windows try program, however.
There is teamcity-notification.log, especially useful if you enable DEBUG logging:
http://confluence.jetbrains.net/display/TCD65/Reporting+Issues#ReportingIssues-LoggingEvents
Are the rules for email and tray notifiers the same? If yes, most probably that is a transportation failure, the error must be in the log.
BTW there is TeamCity 7.0 RC1 available:
http://confluence.jetbrains.net/display/TW/TeamCity+EAP
I'm dumb, they were in my spam folder all along.