raggedstaff/openfoodnetwork
1
0
Fork 0
mirror of https://github.com/openfoodfoundation/openfoodnetwork synced 2026-03-04 02:31:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated testing process to what is

Myriam
2018-07-10 18:32:37 +02:00
parent 1b1f843197
commit b078a5d8d8
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
Testing-process.md

@@ -3,9 +3,8 @@ Once you have submitted a PR and it has been reviewed and approved, it is ready
### 1- Staging a PR
In our distributed team, we are using various staging servers. For now in Australia, France, Iberica and UK.
<br/>The next available developer who has access to a staging server takes the top priority PR and stages it, then moves the PR into the "Testing "column and adds as a comment the URL of the staging server he deployed on.
<br/>The next available developer who has access to a staging server takes the top priority PR and stages it, add as a comment the URL of the staging server he deployed on + add the label of which staging it is on.
<br/>This should be done regularly for the delivery pipeline to be fluid. At least developers able to stage should check once a day and stage one PR if there are some. If a developer can pair and work synchrone with a tester, the process will be even more efficient.
<br/>[Pau do we need to add something on single password thing here?]
### 2- Seeds data
While provisioning your server you will need to load sample data, which are located [here](https://github.com/openfoodfoundation/openfoodnetwork/blob/master/lib/tasks/dev.rake).
@@ -13,7 +12,7 @@ This makes the testing task much lighter! We are building a comprehensive set of
<br/>**NOTE:** As a tester or developer, if you are missing some seeds data for your tests to be easy and smooth, please create a GH issue to add them. That way we can enrich step by step our common set of sample data.
### 3- Testing outcomes
The next tester available looks at the "Testing" column and assign her/himself on the PR they start testing.
The next tester available looks at the "Test ready" column and assign her/himself on the PR they start testing.
<br/>Please follow the [testing guidelines](https://github.com/openfoodfoundation/openfoodnetwork/wiki/Feature-Testing-Handbook) to ensure top quality tests.
- If it's all good, the tester comments the PR with link to the testing notes and moves the PR to the column "Ready to go" where an accredited developer can take it and merge.
- It there are some remaining issues, the tester sums them up in the PR with link to testing notes and moves back the PR to the "In dev" column for the developer to continue the work.