IT2032 / IT702 - Software Testing -16 Mark Q & A

                    Year: IV                                                    Semester: VII

                         IT2032 / IT702 - Software Testing -16 Mark Q & A

PART B

UNIT 1 (INTRODUCTION)

1.      The Role of process in Software quality.

Process            -  Definition

Figure   - Components of an engineered process.

Capability Maturity Model.

Testing Maturity model ( TMM )

2.      Testing as a Process.

Validation      

Verification    

Figure : Example Processses embedded in the software development process.

Testing                       

Debuging       

3.      Overview of  the Testing Maturity Model(TMM) & the test related activities that should be done for V-model architeture.

Test releted issues

Benefits of test process improvement

Introduction to TMM

TMM levels

Figure : The internal Structure of TMM maturity level.

Figure : Five level Structure of TMM.

Figure : The Extended / Modified V model

4.      Software Testing Principles.

Define - Principle.

Principle 1  : Revealing defects and evaluating quality.

Principle 2  : Effectiveness of testing effort.

Principle 3  : Test results should be inspected.

Principle 4  : Test case must contain the expected output.

Principle 5  : Test case should be developed for both valid and invalid input conditions.

Principle 6  : Defects ratio.

Principle 7  : Testing should be carried out by a group.

Principle 8  : Tests must be repeatable and reusable.

Principle 9  : Tessting should be planned.

Principle 10: Testing activities should be integrated into software lifecycle.

Principle 11: Testing is a creative and challenging task.

5.      Origins of defects.

Sources of defects

Figure : Origins of defects.

Fault model.

6.      Defect Classes ,Defect Repository,and Test Design.

Figure:Defect classes and a defect repository.

Requirements and specification defects.

     Functional Description defects.

Feature defects.

Feature interaction defects.

Interface describtion defects.

            Design defects.

                Algorithmic and processing defects.

                Control ,logic, and sequence defects.

                Data defects.

                Module interface description defects.

                Functional description defects.

                External interface  description defects.

            Coding defects.

                Algorithmic and processing defects.

                Control ,logic, and sequence defects.

                Typographical defects.

                Initialization defects.

                Dataflow defects.

                Data defects.

                Module interface defects.

               Code document defects.

               External hardware and software interface defects.

            Testing defects.

                Test harness defects.

                Test case design and test procedure Defects.

7.      Defect  Examples: The Coin Problem

Precondition

Postcondition

Figure : a sample specification with defects.

Figure : a sample design specification with defects.

                Algorithmic and processing defects.

                Control ,logic, and sequence defects.

                Typographical defects.

                Initialization defects.

                Dataflow defects.

                Data defects.

                Module interface defects.

               Code document defects.

               External hardware and software interface defects.

            Figure : a code example with defects.

    Algorithmic and processing defects.

                Control ,logic, and sequence defects.

                Typographical defects.

                Initialization defects.

                Dataflow defects.

                Data defects.

                Module interface defects.

                Code document defects.

                External hardware and software interface defects

8.      The tester’s role in a Software Development Organization.

Cooperating with code developers.

Need the support of management.

TMM levels.

9.      Developer / Tester support for developing a defect repository.

Figure: The defect repository , and support for TMM maturity level.

UNIT 2 (TESTING ISSUES)

1.      Smart Tester.

           Reveal defects

           Evaluate quality

           Finite no .of testcase

2.      Test case design strategies.

   Positive consequences

  Two strategies

               Whitebox (clear or glass box)

                Black box(Functional or specification)

   Figure: The two basic testing strategies.

3.      Types of black box testing

   Random testing

               Randomly select the input.

               Three conditions.

   Equivalence class partitioning

               Adv of   Equivalence class partitioning

               List of conditions.

               Figure: A specification of a square root function

               Example of equivalance class reporting table

   Boundary value analysis

               List the conditions

               Figure: Boundaries of on Equivalence partition

               Example of Boundary value analysis.

4.      Other Black box test design Approaches

   Cause and Effect graphing

               Steps of testcases with a Cause and Effect graph

               Figure: Samples of Cause and Effect graph notations.

               The input conditions

               The output conditions

               The rules or relationships.

               Figure : Cause and Effect graph for the character search example.

               Table: Decision table for character search example.

   State Transition testing

               State

               Finite state machine

               Figure: Simple state transition graph

               Table: A state table for the machine

   Error Guessing

               Past experience

5.       Black Box Testing and COTS (Commercial Off-the-shelf) components.

   Usage Profiles

   COTS

   Certification

6.      Types of white box testing

   Coverage and control flow graph

               Three basic primes

               Sequential

               Condition

               Iteration

   Coverage code logic

               Figure: Code sample with branch and loop.

               Figure: A control flow graph representation for the code.

               Table: A test case for the code ,that satisfies the decision coverage criterion.

               Table: Test cases for simple decision coverage

               Table: Test cases for condition coverage

               Table: Test cases for decision condition coverage.

   Path Testing

               Path

               cyoclomatic complexity formula.

7.      Additional white box test design approaches.

               Dataflow and white box test design

               Variable.

               Figure: sample code with data flow information

               Loop Testing

               Mutation Testing

               The component programmer hypothesis

               The copying effect

8.      Evaluating Test adequacy Criteria

    Axioms –Set of assumptions

   Applicability Property

   Non exhaustive applicability property

   Monotonicity Property

   Inadequate Empty set

   Antientensionality Property

   General multiple change Property

   Anti decomposition Property

   Renaming Property

   Complexity Property

   Statement Coverage Property

  

UNIT- 3 (LEVELS OF TESTING)

1.      Need for levels testing.

Unit Test

Integration Test

System Test

Acceptance Test

Fig: Levels of Testing

Alpha And Beta Test

2.      Levels of testing and software development paradigm

   Fig: Levels of testing

         Two Approaches

                     Bottom_Up

                     Top_Down

         Two types of Language

                     Procedure Oriented

                     Object Oriented

3.      Unit Test

Functions, procedures, classes and methods as units

         Fig: Some components suitable for unit test

         Unit Test: Need for preparation

                                 Planning

                                 Both black box and White box

                                 Reviewer

                                 Several Tasks

4.      Unit Test Planning

Phase I:  Describe unit test approach and Risks

Phase II: Identify unit features to be tested

Phase III: Add levels of detail to the planning

5.      The class as testable unit

 Issue1: Adequately Testing classes

 Issue2: Observation of object states and state changes.

 Issue3: The retesting of classes-I

 Issue4: The retesting of classes-II

Fig: Sample stack class with multiple methods

Fig: Sample Shape class

6.      Test harness

·         The auxiliary code developed into support testing of units and components is called a test harness. The harness consists of drivers that call the target code and stubs that represent modules it calls.

               Fig: The test Harness

               Diver

               Stub

7.      Integration Test

Goals

Integration strategies for procedures and functions

         Top down

         Bottom up

         Fig: Simple Structure chart for integration test example

Integration strategies for classes

         Fig: An generic class cluster  

8.      System test: Different Types

         Functional testing

Performance testing

Stress testing

Configuration testing

Security testing

Recovery testing

     The other types of system Testing are,

Reliability & Usability testing.

                 Fig: Types of System Tests

                 Fig: Example of special resources needed for a performance test

UNIT 4 (TEST MANAGEMENT)

1.      Testing and Debugging goals and Policy

 Debugging goal

 Debugging policy

 Testing Policy: Organization X

 Debugging policy: Organization X

2.      Test planning

    Planning

    Milestone

        Overall test objectives

        What to test (Scope of the tests)

        Who will test?

        How to test?

        When to test?

        When to stop Testing?

   

3.      Test Plan Components

·         Test plan identifier

·         Introduction

·         Items to be tested

·         Features to be tested

·          Approach

·         Pass/fail criteria

·         Suspension and resumption criteria

·         Test deliverables

·         Testing tasks

·         Test environment

·         Responsibilities

·         Staffing and training needs

·         Scheduling

·         Risks and contingencies

·         Testing costs

·         Approvals

4.      Test Plan Attachments

·         Test design specifications

·         Test case specifications

·         Test procedure specifications

5.      Reporting Test Results

·         Test log

·         Test log identifier

·         Description

·         Activity and event entities

·         Test incident report

·         Test incident report identifier

·         Summary

·         Impact

·         Test summary report

6.      The role of the 3 critical groups

1.      Managers

·         Task forces, policies, standards

·         Planning

·         Resource allocation

·         Support for education and training

·         Interact with users

2.      Developers/ testers

·         Apply black and white box methods

·         Assist with test planning

·         Test at all levels

·         Train and mentor

·         Participate in task forces

·         Interact with users

3.      Users/clients

·         Specify requirements clearly

·         Participate in usability test

UNIT 5: CONTROLLING AND MONITORING

1.      Measurements and milestones for monitoring and controlling

·         Measurements for monitoring testing status

·         Coverage measures

·         Test case development

·         Test execution

·         Test harness development

·         Measurements to monitor tester productivity

·         Measurements for monitoring testing costs

·         Measurements for monitoring errors, faults, and failures

·         Monitoring test effectiveness

2.       Criteria for test completion

·         All the planned tests that were developed have been executed and passed

·         All specified coverage goals have been met

·         The detection of a specific number of defects has been accomplished

·         The rates of defect detection for a certain time period have fallen below a specified level

·         Fault seeding ratios are favorable

3.       Software configuration management

·         Identification of the configuration items

·         Change control

·         Configuration status reporting

·         Configuration audits

4.       Types of reviews

·         Inspections as a type of technical review

·         Inspection process

·         Initiation

·         Preparation

·         Inspection meeting

·         Reporting results

·         Rework and follow up

·         Walkthroughs as a type of technical review

5.       Components of review plans

·         Review goals

·         Preconditions and items to be reviewed

·         Roles, participants, team size, and time requirements

·         Review procedures

·         Review training

·         Review checklists

·         Requirements reviews

·         Design reviews

·         Code reviews

·         Test plan reviews