Manual Testing Stages – Acceptance, Release and Maintenance Testing


Manual Testing Stages – Acceptance, Release and Maintenance Testing.

Acceptance Testing:

After completion of sprint or software testing level by testers in ST, PO and SM can plan sprint review meeting ( 2 – 4 hours). In this meeting PO and SM can join with developers in ST and testers in ST, Stakeholders, customer and CEO to collect feedback on corresponding sprint or software from customer.


We have two ways to collect feedback from customer, such as  ‘α’ test and ‘β’ test.

                               α   Test                            β  Test
1. In our company

2. To collect feedback from customer

3.Release after demo


1. In customer site

2. To collect feedback from customer

3.Release before demo (β version or trail version)

Yellow box Techniques



If feedback is not good, developers can perform changes and testers can test those changes.


Release Testing:

PO can select few ST members to go to customer site or on site for  sprint release. The selected release team members can install sprint in customer site computers and observe below factors:


  •   Complete Installation
  •   Overall Functionality
  •   Input devices support
  •   Output devices support
  •   Secondary storage device support
  •   Operating system support
  •   Other Existing software support



The above points are also called as green box testing techniques.



After completion of release testing, scrum team people can go back to company and concentrate on next sprint.


Maintenance Testing:

PO can recruit few freshers as change control board members. They are responsible to handle changes in released sprints.

Sprint or software testing, testing stages, Advanced SDLC Models, Manual testing for beginners, manual testing, Software Testing, Tutorialskey , Automation Testing,Manual to automation, Old SDLC Models, Prototype Model, SDLC Life cycle models, Software Development Life Cycle, Waterfall model, Manual testing tutorials, Functional and non-functional testing, SOA,API/SOA Testing,Compatibility testing, performance testing, load testing,Stress testing, Spike testing,Durability or Soak testing, Multilanguity testing,Localization,Globalization, Security testing, Encryption and Decryption testing,Maintenance Testing


PO can use below formula to calculate efficiency of the testing team.


Defect removal efficiency DRE of testers = A/A+B.

A = Number of bugs found by testers during testing.

B = Number of failures faced by customer site people.


In general most of the testers DRE is 0.7 to 0.9.


Case Study:

Testing Stage Purpose Tested by Testing Techniques
1. Documents Testing Completeness and Correctness of documents Authors of documents ex: PO Static Testing or Verification Techniques
2. Unit Testing Validating Programs Developers White Box testing techniques
3. Integration Testing Validating Interconnection of programs Developers White Box testing techniques
4. Sprint or Software Testing Validating Sprint or software w.r.t customer requirements and customer expectations. Testers Black Box Testing Techniques
5. Acceptance Testing Collecting feedback on sprint or software from customer PO + SM + ST + SH Yellow Box Testing Techniques (α and β)
6. Release Testing Validating Release process Few Developers and Testers Green Box Testing Techniques
7. Testing During Maintenance Test changes requested by customer CCB ( Change control board freshers) Grey Box Testing Techniques (White Box + Black Box)



In this article we have seen Manual Testing Stages – Acceptance, Release and Maintenance Testing. In next article we will see Software Testing Life Cycle (STLC).







Leave a Reply

Your email address will not be published. Required fields are marked *