Update README with reference to exported Ghost Inspector tests

This commit is contained in:
Jay R. Newlin (PromptWorks)
2019-10-31 16:32:23 -04:00
parent fbe0963071
commit 8c7a5e7e5f

View File

@@ -220,12 +220,20 @@ To generate coverage reports for the Javascript tests:
yarn test:coverage yarn test:coverage
### Ghost Inspector Tests ### UI Test Automation
AT-AT uses [Ghost Inpsector](https://app.ghostinspector.com/) for AT-AT uses [Ghost Inpsector](https://app.ghostinspector.com/), a testing PaaS
integration testing. These tests do not run locally as part of the for UI test automation and as a form of integration testing.
regular test suite but do run in CI. To run them locally, you will These tests do not run locally as part of the regular test suite,
need the following: but they do run in CI.
Ghost Inspector was developed to make it easier to create, maintain, and
execute UI tests than vanilla Selenium. Ghost Inspector tests and steps can
be exported to files that the Selenium IDE can import. We export these tests/steps
regularly and archive them with the AT-AT codebase in the `uitests` directory.
To run the Ghost Inspector tests against a local instance of AT-AT,
you will need the following:
- [docker](https://docs.docker.com/v17.12/install/) - [docker](https://docs.docker.com/v17.12/install/)
- [circleci CLI tool](https://circleci.com/docs/2.0/local-cli/#installation) - [circleci CLI tool](https://circleci.com/docs/2.0/local-cli/#installation)