Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This brings the tests over to the public repository as committed by @agervase and then updates them for updated eslint rules with some other cleanup.
The following are the previous pull request notes written by @agervase
Edited Tests Run with WebDriverIO v4
The automated tests have been updated to allow for testing through v4 of WebDriverIO. The new tests run synchronously on the XDMoD reference site, and the use of page objects has made the test spec files significantly less verbose. Versions of the files that run through the SauceLabs automated testing service have also been created.
Within the
tests/automated/test/specs/xdmod/
folder,o*.js
tests are the locally running synchronous WDIO v4 tests. They make use of the page objects in thepageObjects/
directory and, at the time of last test, all passed.s*.js
tests in thesyncTests/
directory run synchronously without the use of page objects.sauce_*.js
tests in thesauceTests/
directory run synchronously through SauceLabs using the page objects in the same directory. At the time of last test, all but the few skipped tests passed on the provided Chrome (chr
) and Firefox (ff
) configurations.Motivation and Context
Where the tests previously ran sequentially within the same browser window, each test now opens, runs within, and closes its own browser window. This not only allows for the tests to be run concurrently, but also prevents a failed test from one spec file affecting the tests from a different spec file. Also, the tests all passing and all being run on the reference set now provides for a baseline for further testing in the future.
The addition of passing SauceLabs tests allows the user to run the tests on different browsers and platforms and concurrently without the increase in loading times that running the tests concurrently and locally causes. The SauceLabs service also allows users to go back and watch videos of each test and view screen shots taken as each command is executed. The user also has the option to manually test in a browser and platform of their choosing, which will allow the tester to try to recreate the events of the tests.
Changes