Document End-to-End testing strategy - Githubissues

ProvidenceGeeks / website-docs

Top level README and documentation space for development of the Providence Geeks website

https://www.pvdgeeks.org

4 stars 2 forks source link

Document End-to-End testing strategy #27

Open saimatsumoto opened 7 years ago

saimatsumoto commented 7 years ago

Testing Guide Wiki

Type of Change

[x] New Documentation
[x] Update to existing documentation
[x] Other (please clarify below)

Summary

Initial tasks:

[x] Discovery & Setup
Documentation tasks:
[x] Establish philosophy and strategy
[x] Scope of the test
[x] Tool(s) used
[x] Test cases / Acceptance Criteria

saimatsumoto commented 7 years ago

https://github.com/nightwatchjs/nightwatch/issues/1439 https://5pi.de/2017/04/17/selenium-webdriver-chromedriver-nightwatch-chrome-headless/

saimatsumoto commented 7 years ago

Detailed TODOs

[x] Test Plan to be completed and reviewed by 10/31
[x] Complete Discovery and get nightwatch running by 10/31
[ ] Write Test cases and document into Testing Guide
[ ] Execute the test
[ ] Document results

saimatsumoto commented 6 years ago

@thescientist13 Below may be tracked by another issue (https://github.com/ProvidenceGeeks/website-frontend/issues/92).

Write Test cases and document into Testing Guide
Execute the test
Document results