pk/atst
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add Testing Philosophy section

Browse Source
This commit is contained in:
Jay R. Newlin (PromptWorks) 2019-11-27 16:40:38 -05:00
parent 75aa82f938
commit 83d9000760
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
uitests/README.md
View File

@ -5,6 +5,18 @@ can be found [here](https://app.ghostinspector.com/suites/5d9e3d303ab5d56633c115
[Another suite](https://app.ghostinspector.com/suites/5d9603f1af31210914da04ca) of Ghost Inspector tests runs once daily against the Staging site. Status: https://api.ghostinspector.com/v1/suites/5d9603f1af31210914da04ca/status-badge
## Testing philosophy
The tests have been created to traverse the most common user flows in AT-AT. There are a few tests (e.g. "New Portfolio - no optional fields")
that check for regressions. Others (e.g. "Remove Portfolio Member") check less-common, "negative path" flows. Tests are added as necessary
to ensure fairly thorough checking of AT-AT.
The tests are constructed in a "stepwise" fashion; that is, no individual test depends upon another, and each test checks one step in complex
user flows. As an example, there are six tests for creating a new Task Order, one corresponding to each screen in the process plus one
for adding a second CLIN to a TO. These tests rely on Ghost Inspector's "Import steps from Test X" functionality to perform all the
necessary setup for the current test. This also ensures that tests can be run in any sequence because Ghost Inspector launches up to four
tests simultaneously.
## Running Ghost Inspector tests locally
To run the Ghost Inspector tests against a local instance of AT-AT,