Acceptance Criteria

Defining the acceptance criteria for any project for release becomes a very difficult ask. The acceptance criteria is so because , not all project can have the same acceptance criteria, yet the client expects the same acceptance criteria for all projects. This is the irony.

In any case, the following list can be used as a starting point, with some variations

Acceptance Criteria	Goal/Target	Status
Code/ Feature completion	90 % of the planned code/feature to be completed	Accomplished more than 90 % planned code and have a mutual understanding for the remainder.
BVT cases pass	100 % BVT cases pass	100 % BVT cases passed. Refer the attached results
Final Test Pass	85 % Test cases pass	95 % passed in the final release build.
Bugs Resolved and closed	90 % of  P1-S1 & at least 70 % of P2-S2 bugs should be resolved and closed	Criteria met, 732 defects regressed & verified.
Bug convergence	a. The number of open defects to be decreased in the last two weeks. b. The convergence rate should not exceed one P1-S1 defect for 8 hrs of testing during the last week. c. No open defect exists in Active state during the release.	Criteria met. The bug convergence graph is depicted
Code Coverage	70 % block coverage from Automation & Manual testing	Criteria met. The combined code coverage is 74% .
Automated Test cases %	60 % of the test cases are automated which are identified for automation	Criteria met. 65% cases were automated
Automation pass %	80 % of Pass of Automation Test Suite	Criteria met. 81 % pass achieved.
Reliability Index for automated cases	90 % for previous sprint and 75 % for current sprint to be achieved	Criteria Met. 97 % for previous sprint and 78 % for current sprint. Refer Health index
All Test code checked in		Refer branch
Any explicit Performance /Security parameters called out in SOW

Read more

Sample Release checklist

[Me]: Guruji, can you please help me with a sample release checklist for any product?

[Guruji]: Well, i can help you with only a sample. You may have to moderate it with respect to your project

	Activities	Person Responsible
Engineering activities
1	Create install and configuration scripts as needed.	Dev Lead
2	Remove debugging and testing code from the software (including disabling assertions).	Dev Lead
3	Update version strings with final version information	Dev Lead
4	Cleanup of Resource file	PGM
Quality Assurance Activities
1	Verify all source code meets coding standard; run Checkstyle or other style-checker and do manual inspection	Dev Lead
2	Check that all defects on current defect list have been resolved & have a changelist attached	PGM
3	Smoke test/regression test final build number	Test Lead
4	Verify that all demo scenarios and BVT;s are passing	Test Lead
5	Verify all manual  tests run on the current build and coverage is good	Test Lead
6	Verify all system test scripts run on the actual released software & code coverage	Test Lead
7	Verify all non-functional system tests like performance are documented	Test Lead
8	All fixed defects have been verified as fixed and closed	Test Lead
9	Ensure that all open bugs have been either fixed or moved to an other release.	Test Lead
10	Verify installation by installing system on clean machine	Test Lead
11	Have someone not on your team install and run your system without assistance by following your installation directions.	Test Lead
12	Install program on machine with older version of program (upgrade install)	Test Lead
13	Verify all steps in the deployment plan are completed	Test Lead
14	Verify all acceptance criterias are met	Test Manager/Project Manager
15	Automation deliverable - scripts & installer made available to customer	Test Lead
16	Consistency check:  SRS, User Manual, System Tests, Staged Delivery Plan, and Software must all match	PGM
User Experience
1	Any new or changed functionality is deemed usable	Test Lead/PGM
2	All error messages are friendly & appropriate	Test Lead/PGM
Release Activities
1	Final version of exit report is ready for sending	Test Manager
2	Schedule Acceptance Test date with customer (and instructor)	Onsite PGM
3	Verify the URL of  Web app application is working as expected	Test Lead
4	Synchronize date/time stamp on all release files	Dev Lead
5	Tag and Branch the source code repository.	Onsite PGM
6	Create a backup of the build environment and place the development environment under change control	Onsite PGM / Test Manager / Project Manager
Documentation Activities
1	Verify that User Documentation matches current Release.	PGM/Tech Writer
2	Create a "ReadMe" text file with installation instructions	PGM
3	Write "Known Issues" List	Test Manager
Other Activities
1	Project Visiblity Calculations are current and accurate	Project Manager
2	Road map for the product	Account Manager / Group Project Manager
3	Schedule project Survival Assessment or Post-Mortem meeting	Project Manager

Read more

Test Activities during phases

[Me]:- Guruji, We all know that Test activities varies with the model and also the type of project. So is there a generic list of items which we can safely follow.

[Guruji]:- Yes, You can always do it at any point when enough data is available

Requirement Phase	· Invest in analysis at the beginning of the project · Start developing the test set at the requirement analysis phase · The correctness, consistency and completeness of the requirements should be analyzed.
Design Phase	· Analysis of design to check its completeness and consistency · Analysis of design to check whether it satisfies the requirements · Generation of test data based on design · Setting up of test bed
Programming/Coding Phase	· Check code for consistency with design · Perform system testing in an organized manner - Buddy testing, feature testing, integration testing, System testing etc · Use available tools · Apply stress to the program · Test one at a time · Measure test coverage
Maintenance Phase	· Retest/Regress

Read more