Dynamic Testing

  Dynamic Testing: 

 It is a process of checking if the source code and the application are working as expected. Also called  dynamic testing or validation testing.

* Levels of dynamic Testing: dynamic testing will be carried out at 4 levels.

1) Unit Testing

2) Integration Testing

3) System Testing

4) User Acceptance Testing.

Unit Testing:  A smallest separatable portion in the source code of the application is called unit.
(functions, procedures, etc) Testing conducted on these units to check if the code behind the units
is working as expected or not is called unit testing.

 It is also called module testing or component testing

Integration Testing:  Once all units are tested the programmers will integrate all units and check interactions among the units which is called integration testing.

Note: Unit testing and Integration testing is collectively called white box testing.

White box Testing: Testing conducted on the source code by developers to check does the  source code is working as expected or not is called white box testing.

* What is the need of white box testing?

As the source code is visible, finding and rectifying the problems is easy for developers.The defects that are identified in white box testing are very economical to resolve. To reduce the defects as early as possible white box testing is helpful.
To ensure 100% code coverage.

***** White box testing is also called as glass box, structural, clear box testing.

Black box Testing:  Testing is conducted on the application by test engineers or by domain
experts to check whether the application is working according to customer requirements.

What is the need of Black Box Testing?

1) White box testing conducted by developer in a technical perception where as black box
testing is conducted by test engineers with end-user perception.

2) Programmers will conduct white box testing in a positive perception whereas tester will
conduct black box testing with a negative perception where there is a more chance of
finding more defects

The more defects you identify results in a quality system.

3) White box testing will not cover non functional areas. As functional requirements are
also very important for production system those are covered in black box testing.

4) The objective of white box testing is 100% coverage whereas the objective of black box
testing is 100% customer business requirement coverage.

5) Black Box Testing = System Testing + User Accepting Testing which is called as
requirement Based Testing (or) Specification Based Testing.

System Testing:  Validating the functional and non functional requirements of the system is
called system testing.

System testing broadly classified into two types i.e.

1) Functional system testing.

2) Non-functional system testing.

Functional system testing will be conducted both in a positive perception and also in a negative
perception.

Positive Testing (+ve ):  Testing conducted on the application in a positive approach to
determine what system suppose to do is called positive testing.

***Note :
Positive testing is helpful to check whether the customer requirements are justifying b y
the application or not.

Negative Testing (-ve): Testing a software application with a negative perception to check
what system not supposed to do is called negative testing.

***Note :
Negative testing is helpful to find defects from the software.

Validation

                                           

                                                                      Validation

Testing Approach:

Traditional testing approach:         Positive Testing (+ve).

   Show that the system:

*  D o e s what it should

 * G o a l : show working.

 * S u c c e s s : system works.

 * E a s y to write system cases

 * R e s u l t : faults left in.

Better Testing approach:                -ve Testing:

Show that the system:

* Doesn’t do what it shouldn’t.

* Does what is should

* Goal: find faults

* Success: system faults

 * Difficult to write test cases

 * Result: fever faults left in.

Most common defects :

• Incorrect functionality

• Incorrect data edits

•  Poor performance

•  Poor security

•  Incompatibility

•  Poor UI – User interface

•  Poor usability

Objectives of Testing :

1) To confirm whether the application is developed according to customer requirements or
not

2) Finding defects

3) To make sure all problems are resolved and close.

4) Finally testing is helpful to deliver a quality product and risk-free product to the
customer.

Software testing Principles:

Principles of testing:  Exhaustive principle is impossible.

Exhaustive Testing: If you test functionality with all possible valid inputs and invalid
inputs then it is called exhaustive testing.

*** Testing everything is called exhaustive testing.

• If you check the salary field 5000 , 5001,5002 .............50000 and 4999, 4998 etc is called exhaustive testing.

•  As exhaustive testing is impossible risk based testing is preferred (or) recommended..

Risk Based Testing:  Identifying the operations which most likely to cause failures and then
testing these functionalities on priority basis is called risk based testing.

Defect Clustering:  The small number of modules or functionality may contain more number of
defects. Concentrate more on testing these functionalities.

Pesticide Paradox: If prepared test cases are not finding defects, add/revise test cases to find
more defects.

 The prepared test cases are not helping to find defects then add or modify the test cases for better testing.

Testing shows presence of defects:1    We have to test a application with an intension of
showing defects. For this negative testing is the best approach.

Early Testing:  Testing should start as early as possible in the SDLC.

Testing is context dependent: We have to select or opt appropriate testing approach based
on the type of application we are testing.

Absence of Errors is a fallocy:  Finding and fixing defects. 100% bug free app is impossible.

***** (Fallocy = False statement)

Static Testing:  Verifying if we developing the right system or not is called static testing. It is
also called verification. T his static testing covers reviews and walk through.

Reviews : Examine any project related work or project related work is called reviews.

Types of Reviews:

1) Management Reviews

2) Technical Reviews

3) Code Reviews

4) Test case Reviews (formal, Informal)

Formal Reviews:  if any review is conducted with a prior plan and by following proper documentation and procedures are called formal reviews

Inspections and Audits are the best example of formal reviews.

Informal Reviews: if any review is conducted without following any procedures and documentation then reviews

Walk-through:  knowledge transfer sessions in the form of peer review

Objective of Reviews:  Reviews are helpful to determine

1) Defects in requirement.

2) Defects in design.

3) Deviations in coding standards.

4) To confirm if the prepared test cases are enough to validate a software

5) Reviews helpful improve the organization process.

Software Testing Techniques

             Testing: It is a process of verifying are we developing the right product or not and also
                              validating does the developed product is right or not.

                               Software testing = Verification + Validation.

* What is Verification?

It is a process of verifying: Are we developing the right product or not. Known as static testing.

* What is Validation?

It is a process of validating: Does the developed product is right or not. Also called as

dynamic testing.

                                                

***** 1,2,3,4,5, are verification and other side is validation.

  Software Testing Techniques:

•       Static Testing

•      White Box Testing

•       Black Box Testing

•       Grey Box Testing.

Early Testing

                                                                 

                                                                           Early Testing

Early Testing:    Conducting testing as soon as possible in development life cycle to find defects
at early stages is called early testing. Early testing is helpful to reduce the cost of fixing defects.

 Why does software have defects?

• Incorrect requirements
• Wrong design
• Poor coding
• Complex business logic
• Complex technology
• Work pressure
• Frequently changing requirements.

Software Testing

                                                        
                                          Software Testing

Fundamentals of software testing

Introduction:

This software testing blog is helpful resource to understand software testing and quality assurance concepts. We tried to make this blog simple to understand with practical information wherever possible.

This blog covers almost all testing terminologies which are useful for preparing for software testing job interview.

Besides this we have hundreds of articles covering everything from software testing industry.

                                                    Software development

Business Analyst     --->   Gathering Requirement --> BA-BRS >SRS/FRS

Project Planning      --->   Planning                    --> Project Plan

System Analyst       --->   Designing                  --> Project Archit

Developers            --->    Coding                      --> Source Code

Testing                  --->   Testing                     --> Test > Execution    

Production              --->Delivery & Maintenance  -->To find defects and                                                                                    Report to developer

Errors:  Any incorrect human action that produces a problem in the system is caller error.

Defect:  Deviation between expected behaviour to actual behaviour of the system is called defect.

Failure:  The deviation identified by end-user while using a system is called a failure