Manual Testing - V-Model

 V-Model:

• V stands for Verification and Validation.
• In V model Verification and Validation are running parallelly.
• In V model development stages are mapped with testing stages.
• In V model process, if one stage get completed and 2^nd is running, and changes occurred in 1^st phase than we can revert back to 1^st phase.
• But for this changes customer have to pay some amount.
• Duration of V model is also 3 months.

Verifaction Phase 1 :-

1.  Information Gathering: 

• Business Analyst (BA) is responsible for information gathering.
• Information gathering is nothing but collecting information requirements from customer.
• BA will collect all requirements and creates one document called as BRS (Business Requirement Specification).
• BRS is nothing but bridge between customer to Developer and Testers.
• Domain of Project  get identified.
• So, for BRS document responsible person is Business Analyst.

2.Analysis:

• Here also is Business Analyst involve.
• Analysis is the detail representation in the form of documents.
• It include Main Module, Sub Module, Functionality, Desire input, Desire output, Relationship between Module.
• Here Business Analyst will creates SRS (Software requirement specification) document with help of BRS.
• Business Analyst will prepare SRS document after BRS document.
• SRS is also called as FRS (Functional Requirement Specification)
• SRS document includes:
1. Functional Flow Diagram
2.  Functional Requirement
3. Use Cases
4. Snap Shots

Validation Phase 1 :-

1.Assessment Development Phase: 

• Assessment Development Process means to make strategy for testing.
• Here we have to plan which testing is going to be used.(Manual, automation, database, API)

2.Test Plan Preparation: 

• Project Manager is responsible for Test plan preparation implementation.
• He will prepare a team and distribute work to all team member.
• Estimation is nothing but how much time will take the functionality to complete the task.

3.Requirement of phase Testing:   

• Phase is nothing but unit.
• All estimated requirements for the specific phases are get finalized.

Verifaction Phase 2 :-

1.Coding:  

• Coding is nothing but programming.
• If developer writes a single line than also it’s a code.
• Multiple line is called as Program.
• Collection of program or set of program written by developer creates the software.
• There are 2 types of Developer.
1. Front End Developer
2. Back End Developer
• Front End Developer: FED will develop UI functionality, function flow, process, and etc. things.
• Back End Developer: BED is responsible for data management, data gathering, data security, and etc. things.
• NOTE: The Developer /person who works as FED as well as BED is called as FULL STACK DEVELOPER.

2.Testing:

• Testing is the process of checking completeness and correctness of software.

Validation Phase 2 :-

1.Test Case Design :

• For designing the test cases, Tester are responsible.
• Test case design goes into 2 parts
1. Positive Test case
2. Negative Test case
• On the basis of SRS document tester will prepare (drive) the test case.

2.Design phase Test & Program Phase Test:

• Phase is nothing but unit or code testing.
• This Program phase testing starts with small unit of program.
• Developer is involved in this process.
• This phase is like WBT.

Verifaction Phase 3 :-

1.Integration Testing: 

• Integration is nothing but mapping new module with old module.
• Developer is responsible for integration.

Validation Phase 3 :-

1.Sanity Testing: 

• Sanity testing comes under validation process.
• Test Core and basic functionality of application.
• Important defects are found and are documented.
• Tester will perform Sanity testing.

2.Functionality & System Testing: 

• After sanity testing we have to do system and functionality testing.
• Black Box tester is responsible for system and functionality testing.
• BBT have to check all Functionality of the application with the help of requirement.
• Tester found any defect than tester log defect and send to developer.

3.User Acceptance Testing: 

• UAT is nothing but collecting feedback from the customer.
• In UAT developer, tester, customer are involved.
• We have to show all functionality to the customer as per the requirement.
• After getting positive feedback from the customer we can send product to the final production.

4.Test Documentation: 

• Test Document is nothing but report of testing.
• Tester is responsible for test documentation.
• After creation of document Tester send report to Team leader.
• Team Leader will view it and send it to Project Manager'
• Project manager will view it and send to B.A.
• B.A. will view it and send to Customer.

Verifaction Phase 4 :-

1.Maintenance:

• Is nothing but we have to provide some service after delivery of the product.
• In Maintenance part Technical support as well as non-technical support is involved.
• Technical support is called as KPO (Knowledge Process Outsourcing).
• Non-technical support called as BPO (Business Process Outsourcing).

Validation Phase 4 :-

1.DRE (Defect Removal Efficiency):

• In that we have to check that how well we are in testing?
• DRE can calculate by formula 
• DRE=a/(a+b)
• a= defect found by tester
• b= defect found by customer during UAT 
• Remarks:-
• DRE Value = 0.8 to 1.0---------->Good Testing
• DRE Value = 0.5 to 0.8---------->Avg. Testing
• DRE Value = 0.1 to 0.5---------->Bad Testing

2.Request for change: (RFC) 

• If customer want some changes in product at the time of release, to do so customer request for change.
• The changes in product are mention in SRS document. At the end of SRS there is a section ”CR” it is in red color.
• Customer have to pay extra money for this.

3.Regression Testing: 

• Regression Testing is subset of Sanity Testing.
• As we know there are 4 Test Environment

• It is the process of checking newly corrected or newly added functionality working properly or not and their impact on other working modules.
• Regression Tester (We are) responsible for this testing.

4.Postmortem Testing:

• It is work of White Box Tester.
• After change in requirement, developer will develop the functionality and Regression tester will test it and product is ready for production but product is not producing desired output.
• Then White Box tester have to check all modules in detail.