| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Complete training for UAT (Kate’s team or project team?) - 1 w
finalize UAT test cases
show to UAT testers what is expected from them
demo for UAT testers on QA partition
show to UAT testers which test cases they will test
let UAT testers do first testing and help them with first questions or issues
choose test management tool and leader of UAT testing phase
make sure everything is ready for UAT - access to all tools and environments, login credentials for UAT testers
Pfx: finalize bug fixing from the last Feature Sprint
Complete initial data loads in QA & data verification
Complete Integration testing 1 w
check that all integration works correctly on QA partition
let UAT testers do first testing and help them with first questions or issues - they should feel comfortable about what is expected from them at the end of this week
make sure UAT testers have final version of E2E test cases and they are ready for testing
log bugs for integration issues to JIRA
Pfx: fix integration issues
retest bug fixes and confirm the integration is working at the end of this week
Complete E2E script testing 2 w
1st w:
start testing based on E2E test cases
top priority and long test cases first
log bugs to JIRA every day
report progress to UAT test leader every day
Pfx: bug fixing if possible - deployment should not be done during UAT testing
2nd w and all other weeks:
continue testing based on E2E test cases
all test cases should be finished this week
log bugs to JIRA every day
report progress to UAT test leader every day
Pfx: bug fixing if possible - deployment should not be done during UAT testing
Complete Bug fixing (requirements or regression issues) - 1w
Pfx: finish bug fixing, deploy all changes to QA partition
prepare scope of final week - bugs for retests, test cases to be tested again
Complete Bug testing - 1 w
final part of UAT
prepare scope for final regression
retest all reported bugs to verify they were fixed
retest selected UAT test cases to verify the application is working correctly on QA partition
log bugs to JIRA every day - there should not be any new issues this week, so just in case
report progress to UAT test leader every day
final regression testing after bugs were retested
...
Examples of project timelines and allocations
Pre-UAT | Pre-UAT | UAT | UAT | ||
# of sprints | Training and prep | SIT | E2E testing | Bug fixing & testing | Total UAT weeks |
3 | 1 | 1 | 1 | 1 | 2 |
4 | 1 | 1 | 2 | 1 | 5 |
4 or 5 | 1 | 1 | 2 | 2 | 4 |
6 | 1 | 1 | 3 | 2 | 7 |
6 or 7 | 1 | 1 | 3 | 3 | 6 |
Role | Allocation | ||||
PM | same as FS allocation | ||||
SA | 50 % of FS allocation | ||||
CE | 50-75 % of FS allocation | ||||
IE | 25% of FS allocation | ||||
QA | 50-75 % of FS allocation | ||||
Internal description as Packages
Customer can choose length of UAT based on his experience and size of the project:
small - 4 weeks (for 3 FS projects)
medium - 6 weeks (for 4-5 FS projects)
large - 7 weeks (for 6-7 FS projects)
Purpose of choosing the package is to involve customer in UAT phase and make sure the customer understands details about UAT. Size of the package must be selected before the final project timeline is created. Price of the selected package should be based on needed allocation for all project roles.
...
| Info |
|---|