Manual Testing for Beginners – Testing Stages or Phases

 

Manual Testing for Beginners – Testing Stages or Phases :

 

Documents Testing :

In fish model/V model /Agile model , the first stage of testing is documents testing. This testing is also called as verification or static testing .

PO is responsible to prepare product backlog document by specifying  all users stories. The same PO can review that  product backlog for completeness or  correctness.

PO along with scrum master are responsible for sprint back log preparation by selecting some user stories from product back log . They will verify completeness and correctness of that sprint backlog.

Developers in scrum team (ST) can study that sprint backlog and prepare HLD or LLD’s. Here, HLD is specifying overall architecture of sprint , every LLD’s specifying internal logic of specific model.

Case Study:

Document	Prepared by	Reviewed /Tested by	Techniques
PBL (All User Stories)	PO	PO	-> Walk through -> Inspection -> Peer review
SBL (Some  User Stories)	PO & SM	PO & SM	-> Walk through -> Inspection -> Peer review
HLD & LLD’s	Developers in ST	Some Developers in ST	-> Walk through -> Inspection -> Peer review

 

Walk through:   Study a document from first to last.

Inspection :    Search a document for specific factor/ issue.

Peer review :  comparison  of two similar documents point to point.

The above 3 techniques  are called as documents testing techniques/ Verification testing techniques/ Static testing techniques.

 

Unit  testing :

After completion of documents  preparation and testing, corresponding developers in scrum team can start coding. Here developers can write programs and test every programs , by using write box testing techniques.

A. Basic paths coverage :

Developers can use this technique to confirm that program is working or not without any runtime errors. Here developer can run corresponding programs more than one time to cover all regions of that program.

Step 1: Programmer can open program.

Step 2: Draw flow graph by emulating flow of execution of that program .

Step 3: Find No. of paths in that graph ( cyclamatic complexity ).

Step 4: Run program more than one time by covering each path of execution for runtime errors.

 

 

B. Control structure coverage :

After completion of basic paths coverage, the corresponding programmer can concentrate on that program is correctly working or not.

Here programmer can enter inputs and check correctness of output of that program. This technique is also called as debugging .

Note: Once in past , testing means debugging. Today debugging is a part of testing .

 

 

C. Program technique coverage :

When program is correctly working , corresponding programmer can calculate speed of that program execution . If speed is not responsible , then programmer can change that program structure without disturbing functionality .

Example:   Swapping two values

Logic 1	Logic 2
a = 10 b = 20 c = a a = b b = c a = ?  –> 20 b = ?  –> 10	a = 10 b = 20 a = a + b b = a – b a = a – b a = ?  –> 20 b = ?  –> 10
Take less time but need extra memory.	Take less memory but take more time.

 

 

D. Mutation coverage :

After completion of 3 tests on our program , corresponding programmer can perform changes in that program to perform retesting . If retesting was  effected because of changes , corresponding test coverage is good on that program. If retesting was  not affected  because of changes , corresponding test coverage is not good on that program and programmer needs to continue same program testing .

Manual Testing for Beginners – Testing Stages or Phases

Integration  Testing :

After completion of programs  writing and corresponding programs unit testing , programmers  can start interconnection  of those programs to build a sprint (or) software .

While interconnecting programs , programmer can follow any one of below approaches.

 

a) Top-down approach:

From this approach, programmers can interconnect main program with some of the sub programs. In the place of remaining sub programs, they can use temporary programs called as Stub.

b) Bottom-up approach:

From this approach,  programmer can interconnect sub programs without involvement of main program because main program is under construction. Here programmers can use a temporary program instead of under constructive main program, called as ‘Driver’.

 

c) Hybrid approach (or) Sandwich approach:

This approach is a combination of top-down and bottom-up approaches.

The above Top-down, Bottom-up and hybrid approaches are called as Incremental Integration approaches.

 

 

d) System approach (or) Bigbang approach:

From this approach, programs can interconnect programs after completion of 100% coding.

 

Sprint (or) Software Testing:

After completion of Integration of programs and integration testing, corresponding developers in scrum team(ST) can release sprint or software build to testers in ST.

Testers in scrum team can receive sprint or software build from developers and then conduct below specified functional and non-functional tests.

In this article we have seen Manual Testing for Beginners – Testing Stages or Phases. In next article we will see Functional and Non-functional Testing step by step.