…ns cron integration tests from gh-pages branch instead of master
Our release process right now is merge completed features into master, let those features accumulate until we're happy to release, and then merge the release PR into the gh-pages branch. Our integration tests that run every day currently check out the latest version of master and run them against whatever is deployed in prod. So our tests from the latest unreleased features will be run against the current release and will fail.
This PR changes the github action that builds master and creates a release PR to include package.json, nightwatch.conf.js, and the test-browser folder. This will allow us to check out the gh-pages branch (instead of master) in the integration test actions, run yarn install, and run yarn test_chrome/firefox with the correct set of tests.
…ns cron integration tests from gh-pages branch instead of master
Our release process right now is merge completed features into master, let those features accumulate until we're happy to release, and then merge the release PR into the gh-pages branch. Our integration tests that run every day currently check out the latest version of master and run them against whatever is deployed in prod. So our tests from the latest unreleased features will be run against the current release and will fail.
This PR changes the github action that builds master and creates a release PR to include package.json, nightwatch.conf.js, and the test-browser folder. This will allow us to check out the gh-pages branch (instead of master) in the integration test actions, run yarn install, and run yarn test_chrome/firefox with the correct set of tests.