10 events
when toggle format what by license comment
May 9, 2019 at 14:20 comment added Moro In Java tests are run via junit. I ve seen junit implementation for js. This one: npmjs.com/package/junit mentions the flags you need (fail on unhandled) etc. Maybe use it as a test runner?
May 9, 2019 at 13:50 comment added tehbeardedone @Moro My problem is not with the test itself it is with a test step. If a step fails due to a timeout, then the next step will execute and again wait for the default timeout interval before failing. Instead of executing subsequent steps, I want to immediately fail on the first timeout and move on. To put it simply, Lets say my test has 5 steps. If step two times out for some reason, element not present/interactable, etc., then steps 3-5 will also attempt to execute and wait for the full timeout interval before failing. There is a lot of unnecessary waiting happening in this scenario.
May 9, 2019 at 4:27 comment added Moro Why would a next test start if the first one throws a TimeoutException? If something like this is thrown, the test fails and results in an error. Unless the second test is dependent on the first one, it should not matter, if it is then this is what should be fixed as making test dependent on each other is bad practice.
Apr 13, 2019 at 9:00 comment added Vishal Aggarwal +1Excellent question.
Apr 13, 2019 at 8:57 answer added Vishal Aggarwal timeline score: 1
Mar 13, 2019 at 6:16 history edited João Farias CC BY-SA 4.0
added 1 character in body
Mar 12, 2019 at 16:17 comment added tehbeardedone I guess a better way to describe it is that if I use ExpectedConditions.visibilityOf() or ExpectedConditions.elementToBeClickable() the test will not fail if these functions timeout before the element is visible in the DOM or becomes clickable. It just throws a timeout error and moves on the the next step. Looking for some ideas on how to explicitly fail if something like that happens that could be reused for multiple scenarios. Maybe I'm overthinking it. I don't know. Just having a hard time picturing how this would work.
Mar 12, 2019 at 16:09 comment added tehbeardedone Hmmm, yeah not quite what I'm looking for. It's working fine if an assertion fails. That's completely different. I'm talking about a situation where you need to complete a certain number of steps in the test case before you get to the assertion and one of the steps has failed. Making it impossible to complete any of the additional steps before the assertion. I want to fail the test on the first step that fails and move on instead of waiting for all the steps to run their course and then fail on the assertion.
Mar 12, 2019 at 15:32 comment added anonygoose I can't answer the question, as I don't know anything about Protractor tests yet. I'm familiar with other automated testing though, and can say Protractor should automatically be failing the current test case and moving on to the next on any fail/error. There's been a bug open for this for 2 years: github.com/angular/protractor/issues/3234 Last update suggests if you're on the latest Protractor maybe it just works correctly now. Good luck!
Mar 12, 2019 at 14:30 history asked tehbeardedone CC BY-SA 4.0