I have a strange bug when running tests in Ember (w/CLI) where the last test that is in my directory is added to any of the individual test modules. The last test always breaks and if I delete the last file it will move on to the penultimate test and append that test. The tests fails with a Global Error message
Any ideas why it would append the last test to any of my individual tests?
Related
Is there a gtest flag or any other way to re-run tests with google test that were previously successful ( and no change to any code).
It doesn’t seem that there is a specific option for rerunning tests.
You could run the test collection and generate a report in XML or JSON format. Then, you could parse the report, and create a --gtest_filter=... argument by joining the names of successful tests as a colon-separated string.
You could also imagine writing a custom test listener. This would need to write out successful test names to a file, and once again, you could write some simple code to generate the corresponding --gtest_filter argument.
I have a project where I am running 100 scenarios every day. After the run has complete, through listeners I am updating the pass/fail in an Excel sheet. I want to hear about a solution where, if I am running the test suite again, the passed test cases should be skipped and only failed test cases should run. I dont want to use retry.I tried to use skipException in beforeInvocation listener method but the test case is still executing the passed test case. How can I skip the passed test cases and execute only the failed one through listeners ?
Every time before the start of the scenario, it should go to the listener and check the excel sheet whether the scenario is passed or fail. If passed then the scenario should be skipped.
Any help will be greatly appreciated.
Update: I am able to do it through listeners, with skipException, but in my report it is showing test as failed and not as skipped
When you run bdd tests, qaf generates configuration file with name testng-failed-qas.xml under reports dir. You should use that config file to run only failed scenarios.
NUnit3 Console runner saves test results in xml at the end of the test run. But in my case I want to save the partial results on each test failure, so that in case console runner crashes or is stopped, I can still get partial results for completed tests.
Is there a way to do that?
Test Results are saved regardless of failures or successful test runs. The XML file is generated for every test run. You could also write every test result to a log file if the XML is not generated for a particular test run.
I have a small collection of integration tests that utilize selenium in a class. The idea is that these tests run every time there is a merge to the codebase, with the merge proceeding through the pipeline and having a series of tests running against the new code.
The thing is, these selenium tests have to run one at a time. They're using the browser to log into a website, and the account will just log out if more than one person tries to log into the account at once, it'll just log out, and the test will obviously fail, so I need these tests to run one at a time. I've tried using the #NotThreadSafe annotation, doesn't seem to have changed anything, and I've searched through for some sort of switch or parameter that defines how many tests run at once with no luck. These tests are using junit 4.12.
I have a bunch of tests that run individually and I would like to create one single test (let's call it root test) which will call the others one by one, so as I have the complete test suite able to run with a single click and have the results for all of them in a single page, respecting the fact that I want them to be in separate folders, etc.
So my question is: Is there a way to create such a test in DBFit?
I have a root directory for my tests called 'MyTests' and there are lets say 5 different tests in there in separate folders. I created a suite and I changed the context.txt file of the MyTests page where I would like to run the suite. In that file I added the line !see .MySuite?suite The suite contains calls to each report I want in its own content.txt file.