From 57b40ee4a7733ef2bf2a36ecfb2228ec75be87a5 Mon Sep 17 00:00:00 2001 From: Myriam Date: Wed, 7 Feb 2018 11:48:02 +0100 Subject: [PATCH] Updated Testing process (markdown) --- Testing-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Testing-process.md b/Testing-process.md index 173eeaf..af7d18f 100644 --- a/Testing-process.md +++ b/Testing-process.md @@ -3,7 +3,7 @@ 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. -
The next available developer who have 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. +
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.
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.
[Pau do we need to add something on single password thing here?]