CURRENT UAT PROCESS

By: Lorlyn Toriaga

 CURRENT UAT PROCESS BY STEPS

Step 1: Team Lead can assign a developer, or a developer can assign themselves to work
around on enhancement requests or bug fixes that will be include on the app next
release.

Step 2: Assigned developer will work (code) on his assigned fixes or enhancements and finish it
(soon as possible) before the date of next release.

Step 3: If the developer is done on the fixes or enhancements and create PR/s (pull request),
the author of that fixes or enhancements will assign another developer in testing to
test his/her work.

Step 4: During the testing of PR, the reviewers will test (the bug fix and its full cycle) to ensure
that his/her fixes are working, and the enhancements are bugs free.

NOTE: If the assigned reviewers report that there are bugs on PRs, the author will work
on it to fix the reported bugs and become bugs free.

Step 5: If the reviewers report that a PR are bugs free and the enhancements perform well and
meet its requirements, they will approve the PR/s on the Bitbucket.

NOTE: If two (2) or three (3) people on the reviewers approved the PRs, it’s a go signal
for the team lead that the PR/s is working well and ready to merge.

Step 6: If PRs are approved by the reviewers, the team lead will merge the changes (fix and
enhancements) to the clean master branch.

Step 7: The team will test the clean master branch in a full cycle test (login to logout) to make
sure its bugs free.

Step 8: Team lead will ready the master and assigned developer to create ECR (Environment
Change Request) document.

NOTE: ECR consists of change details in an application and its reason for the changes.

Step 9: ECR will be send via email (with Jim and others) to ask an approval to the acting test
lead and to all affected parties.

Step 10: If the ECR are approve by the acting test lead, the developer will prepare the latest
version of apk.
 NOTE: ECR will not pass and will not continue to release if the team, Jim and others
will decide to postpone the release. Also, if the ECR is lack or consist of wrong
details (wrong date, lack of information in proposed changes and its justification)

Step 11: After preparing the apk, the developer will email Jim, the developers that are working
for the app and the affected parties the latest version of apk with the summary of
the changes, updates, fixes and enhancements in the app.