Unit Testing

Unit Testing:-

After completion of coding in developed software build developers will do unit testing whether any errors are in developed coding

               Unit testing using white box testing technique(WBT) for testing

White Box Testing techniques:-

• Basic path coverage
• loops coverage
• Conditions coverage
• Programming technique coverage

Basic path coverage:-

During this coverage programmers are verifying each and every statement in program is correctly participating in execution or not

Loops coverage:-

During this coverage programmers are verifying each and every loop statement in a program is correctly terminating or not as per requirement 

Conditions coverage:-

During this coverage programmers are verifying each and every condition is providing corresponding output or not

Programming technique coverage:-

During this coverage programmers are verifying each and every program is implemented with less logical statements or not to get output or response fast

Fish model

Software Quality

Software Quality:

Technical:

Ø  Meeting Customer Requirements

Ø  Meeting Customer Expectations (User friendly, Performance, Privacy)

Non-Technical:

Ø  Cost of Product

Ø  Time to Market

Software Quality Assurance:

To monitor and measure the strength of development process, Organisation follows SQA concepts.

Software Project:

Software related problems solved by software engineers through a software engineering process

Regression Testing

Regression testing:-

Re execution of previous passed selected test cases on modified software build to find out any side effects

raised on previous tested functionalities with respect to the internal code changes 

                                   

User Acceptance Testing

User acceptance Testing:-

after successfully completion of system testing then project management people are inviting customer or user to development environment for user acceptance testing during this test customer will perform on developed software to find out whether our developed software is fulfilling his business needs or not

                                          User acceptance test is mainly categorized into two types

• alpha-test
• beta-test

Alpha-test:-

this is first level of user acceptance test done by customer or user at development environment or company environment with the involvement of development team testing team and project management team

Beta -test:-

this is second level of user acceptance test done by customer or user at customer environment with the involvement of release team

SOFTWARE DEVELOPMENT LIFE CYCLE(SDLC)

Software development life cycle:-

It defines step by step process of software developer from starting to ending to develop a software with in specified time,with in specified budget and to deliver quality software to customer

                                  In SDLC overall software development work is divided into below stages 

1. requirement gathering
2. analysis
3. design
4. coding
5. testing
6. delivery&maintenance

Requirement gathering:-

In this stage business analyst will gather information from customers and prepare business requirement specification in this brs business analyst will gather total project information from customer side people

Analysis:-

After completion of business requirement specification system analyst will receive BRS and system analyst prepare software requirement specification . in this srs document contain functional requirement specification and non functional specification.. project development and testing by using SRS

Design:-

After completion of SRS design architecture or system architecture will design project plan document. in this design two types of designs.high level design,low level design

Coding:-

after completion of design developers or programmers  will concentrate on to develop a project with respect to software requirement specification .to implement software build with the help of coding

Testing:-

After completion of developing a software build then test engineers are receiving developed software build to development team then test engineers are will concentrate on testing the over all software build with respect to the software requirement specification to release quality software to customers 

Delivery&maintenance:-

after completion of testing then deployment team or release team will receive quality software to customers

and they have change control board team and maintenance team to maintain the the software build and after software build is go to customer side people then we need to change any modification change control board team will do that modifications

Software Test Life Cycle

The different stages in Software Test Life Cycle -

Each of these stages have a definite Entry and Exit criteria  , Activities & Deliverables associated with it.

In an Ideal world you will not enter the next stage until the exit criteria for the previous stage is met. But practically this is not always possible. So for this tutorial , we will focus of activities and deliverables for the different stages in STLC. Lets look into them in detail.

Requirement Analysis

During this phase, test team studies the requirements from a testing point of view to identify the testable requirements. The QA team may interact with various stakeholders (Client, Business Analyst, Technical Leads, System Architects etc) to understand the requirements in detail. Requirements could be either Functional (defining what the software must do) or Non Functional (defining system performance /security availability ) .Automation feasibility for the given testing project is also done in this stage.

Activities

• Identify types of tests to be performed. 
• Gather details about testing priorities and focus.
• Prepare Requirement Traceability Matrix (RTM).
• Identify test environment details where testing is supposed to be carried out. 
• Automation feasibility analysis (if required).

Deliverables 

• RTM
• Automation feasibility report. (if applicable)

Test Planning

This phase is also called Test Strategy phase. Typically , in this stage, a Senior QA manager will determine effort and cost estimates for the project and would prepare and finalize the Test Plan.

Activities

• Preparation of test plan/strategy document for various types of testing
• Test tool selection 
• Test effort estimation 
• Resource planning and determining roles and responsibilities.
• Training requirement

Deliverables 

• Test plan /strategy document.
• Effort estimation document.

Test Case Development

This phase involves creation, verification and rework of test cases & test scripts. Test data , is identified/created and is reviewed and then reworked as well.

Activities

• Create test cases, automation scripts (if applicable)
• Review and baseline test cases and scripts 
• Create test data (If Test Environment is available)

Deliverables 

• Test cases/scripts 
• Test data

Test Environment Setup

Test environment decides the software and hardware conditions under which a work product is tested. Test environment set-up is one of the critical aspects of testing process and can be done in parallel with Test Case Development Stage. Test team may not be involved in this activity if the customer/development team provides the test environment in which case the test team is required to do a readiness check (smoke testing) of the given environment.

Activities 

• Understand the required architecture, environment set-up and prepare hardware and software requirement list for the Test Environment. 
• Setup test Environment and test data 
• Perform smoke test on the build

Deliverables 

• Environment ready with test data set up 
• Smoke Test Results.

Test Execution

 During this phase test team will carry out the testing based on the test plans and the test cases prepared. Bugs will be reported back to the development team for correction and retesting will be performed.

Activities 

• Execute tests as per plan
• Document test results, and log defects for failed cases 
• Map defects to test cases in RTM 
• Retest the defect fixes 
• Track the defects to closure

Deliverables 

• Completed RTM with execution status 
• Test cases updated with results 
• Defect reports

Test Cycle Closure

Testing team will meet , discuss and analyze testing artifacts to identify strategies that have to be implemented in future, taking lessons from the current test cycle. The idea is to remove the process bottlenecks for future test cycles and share best practices for any similar projects in future.

Activities

• Evaluate cycle completion criteria based on Time,Test coverage,Cost,Software,Critical Business Objectives , Quality
• Prepare test metrics based on the above parameters. 
• Document the learning out of the project 
• Prepare Test closure report 
• Qualitative and quantitative reporting of quality of the work product to the customer. 
• Test result analysis to find out the defect distribution by type and severity.

Deliverables 

• Test Closure report 
• Test metrics