Our QA process for first 4 years of the launch of the new platform was all done as manual End to End testing. While new features were constantly pushed every week, we split the testing between 3~5 team members from dev, marketing and account/production team.
The dev team wanted to build automated browser tests with a BDD tooling/process. So we started rewriting our module tests into automated test scripts/specs with the goal in mind to do eventually do End to End in the future.
Specifications:
We decided to write the scenarios in Gherkin so it is readable and writable by anyone.
We used CucumberJS because it merges specification and test documentation together.
Since our platform was built on an AngularJS framework, we used Protractor.
By using Selenium Webdriver with we were able to test across all browsers on BrowserStack.
Tests were executed from Jenkins whenever new code was push to the Dev portal/branch.
If any test failed, the dev team would recheck the push for the reason.
https://github.com/brianeng87/qa-automation-beta/
Resources:
https://docs.cucumber.io/
https://www.protractortest.org/#/server-setup
https://www.browserstack.com/automate/protractor
https://medium.com/simdevelopers/end-to-end-gherkin-testing-with-cucumber-js-and-protractor-make-your-team-amazing-4f3e2e1a2adc
