• Testing concepts
  • Sunday, 25 August 2013

    Regression Testing and Retesting

    Regression Testing and Retesting:

    Regression Testing: This is type of testing where If any modification has been done in the application
    which has already been developed before has instantaneously effected the current application is known as Regression effect.
    Like an simple example:
    If A and B has been developed as two different modules but in later part some other developer comes and
    modifies that requirement which was been already developed so it might direct cause an effect to A module. This is known as Regression effect. So testing has to be done as Regression Testing where to detect bugs where the exact modification has been done and try to fix the issue

    Retesting: This type of testing is different from Regression testing wherein this type of testing is just
    and Retesting of same test case which was prepared by Tester before and after the issue as fixed by the developer the bug or test case has to be tested once again. So this is known as Retesting

    Like an simple example:
    If A test case is been prepared and an issue or bug is posted by Tester, it goes to developer where he has to fix it immediately as per priority and then further after fixing the issue.
    Tester tests or Retests it again known an Retesting

    Friday, 16 August 2013

    V-Model and Agile Model

    Difference between V-Model and Agile Model

    V-Model is the approach of SDLC where both Verification and Validation goes on parallel

    After every development phase it is been passed and sent it on for Testing

    Verification phase are:
    1. Requirement analysis :  All documents are prepared and gathered.
    2. High level design:     Modules are been broken into sub modules
    3. Low Level design:   Further sub modules are broken to minor modules for coding
    4. Coding:                  Here Coding and scripting is done

    Validation phase are:
    1. Acceptance testing: Prepared Acceptance test plan and done both Alpha and Beta testing
    2. System Testing:  Test Plan and Test cases are written into system
    3. Integration Testing: Both modules are integrated and tested
    4. Unit testing:   Code review or White Box testing

    Agile Model:

    Agile Model includes Scrum methodology 
    Scrum includes team members including moderator, team members, reviewer
    Every week Scrum meeting goes on and prepares a full week Scrum cycle 
    Agile model in more advantageous because of the flow of SDLC as even a small module is prepared and sent for testing so lesser amount of bugs will be reported. It is common now in the companies where they follow Agile process of development 

    Thursday, 1 August 2013

    Testing Document preparation

    Test Doc should be prepared as per the requirements of SRS before starting the Testing to understand the flow of application

    Testing documentation mainly helps in preparing all types of how much of testing has to be done, the effort required, how much test coverage has to be covered, whether all the requirements are been covered. here it includes few concepts :

    Mainly Test Plan is prepared from the scratch by given Requirements document which is prepared by some of the senior team members.
    Secondly the Test Scenario is prepared from the given test plan where we can understand the flow of the test plan and cover all the scenarios.
    After preparing some test scenarios or test conditions detail Test Case are prepared and divided into number of test steps.
    Final part of Testing requires to know whether all test cases are been covered and it will be known from the result of Traceability Matrix....

    Detail explanation of Test Plan:
    A Test plan mainly consists of different strategies prepared from the given SRS and will get to know the flow of the application and what and all needs to be covered and resources what needs to be used and how much time is required to complete the schedule activities.

    Here a Test plan mainly will consist of.

    Test Plan document Introduction

    Divide the application into number of test cases

    Features to be tested and not exceptions which are not be tested

    The deliverables required for testing

    Hardware/Software requirements

    Any risks involved while testing on the given schedule

    Test Scenario

    A Statement which is prepared from the given test plan or known as test condition
    deriving into different  scenarios and further making it to test cases.
    Test cases are in detail functionality but test scenarios are just the overview
    which satisfies the functionality.

    Test Case doc

    Test cases involves in the detail step by step procedure of testing each test condition or scenarios where different types of testing is done like functionality testing, smoke testing, system testing etc. To prevent from bugs test cases are prepared and execution. Mainly test cases comprises more of negative test cases than positive test cases which is known as destructive methodology.

    Test case ID. Pre-Conditions. Description . Expected Condition. Actual Condition . Result

    Traceability Matrix is a table which is used mainly to know whether all requirements have been covered and executed in the given application it is either prepared from the excel sheet or tool.