Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Tweak test organization #128
This is related to #121. When the Jenkins server is setup, we will regularly run all of the tests before PRs are merged. That will require that any contributor can exactly reproduce whatever tests are going to be run, to be sure that their feature branch passes and address any issues beforehand. Therefore, we should tweak the tests to remove hardcoded usernames.
I'm adjusting the title to add a few related items here.
We should organize the tests according to how often the are run: 1) at least before every PR (and afterwards automatically via jenkins) and 2) before every release (this should include larger scale, stress-testing). We should be able to run all tests in either category easily. @yadudoc had a great idea of for example having a bash script we could run to set env variables (for example, usernames on various resources). Alternatively, we could have a test config where devs could store that info.