You can now run your test suites within MuseIDE, watch the progress, cancel when desired and view the result and event log for each test in the suite. See the Run Test Suites in MuseIDE post for details.
Other enhancements include:
- IdListTestSuite editor supports adding ids of test suites…allowing suites containing other suites
- enhance expression grammar for simpler usage: <page.element> instead of <page:”page.element”>
- improved docking behavior (no floating sections, navigator not maximizable)
- When starting a test suite, start running immediately (don’t make user press 2 play buttons)
- StepTree is smarter about auto-collapsing only the branches that it auto-expanded when running a test interactively
- Support for the PhantomJS driver
- new step: SetBrowserSize
- new condition: ElementHasClassCondition (and expression support)
- Improvements to test execution support classes to improve the test suite reports
- Improvements to the JUnitReportRenderer
- Update to Selenium 3.4
- After deleting a step, undoing, redoing and undoing again results in 2 copies of the un-deleted step.
- Running a test in one editor results in the other test editors acting like a test is running.
- When importing SelniumIDE tests, if the last-used folder no longer exists, the select-files dialog does not open.
- Ignore exceptions thrown by WebDriver.quit()
- Tests always return a result, even when serious exceptions are thrown
- encode jUnit report XML in UTF-8 (for Jenkins)
- HTML-escape the test failure message in the jUnit report XML
- run VariableListContextInitializers in the order they appear in the config