You are on page 1of 1

1.

Developer will develop the user story Pro_Mod_fun_15 and will do the unit testing, once It is
done will save that code to dev repository with version 9955.
2. Deployment team will deploy that code with version 9935 in the QA environment.
3. Tester will check the status of the user story, if it is in his bucket of tester then will check the
version of the code to be tested in the QA environment, if it is same as the version in the
master repository then tester will start testing the code/build. If the version of the code in
the master repository is not same as the code in the QA environment And if it is important or
urgent to test that code then the tester will send the email to the deployment team to
deploy the code with respective version in the QA environment.
E.g., In Dev repository, the current version of code is 9955.
The version of the code deployed by the deployment team in the QA environment is
9935.
In master repository, the current version of code is 9955.
Now, as the version of the code in the master repository is 9955 and the version of the
code in the QA environment, i.e., 9935 is not same, the tester cannot start testing the code.
Tester will wait, maybe for a day if testing that functionality can we postponed to next day.
Let's say, the next day the deployment team has deployed the code with version 9945 in the
QA environment. Tester will find that the newer version deployed in the QA environment is
not same so tester can't start testing the code. Tester can't wait further, so tester will send an
email to the deployment team to deploy the code with version 9955.
As a response deployment team has deployed the code with version 9962 in the QA
environment. Again, the tester will check the version of the code in the Q environment fish
same as the master repository. As the current version of the code in QA environment i.e.
9955, tester will perform testing.
4. Once the testing is done, If any bug is reported then developer has to fix the bug. Once the
bug is fixed, let’s say the new version of the code is 9956 will be saved by the developer in
the dev repository.
5. Tester has to test whether the bug is fixed or not, tester will repeat Step 3. After testing if the
code is bug free then the deployment team will deploy that code in the master repository
with the version , let’s say 9960.
6. It means, bug free code is deployed in the master repository.

You might also like