Software testing and quality assurance by sofiaie


									                  Software Testing and Quality Assurance

Businesses use to use computers as an aid but increasingly businesses are
dependent on their computer systems for their very survival. Effective testing
is essential for reliable, quality software. The need, therefore, is to ensure a
rigorous, visible, formal, measurable and repeatable approach to testing.

Testing accounts for a substantial part of the cost of software and there is
increasing concern to ensure that the time and money invested is used
effectively. As more people, from differing backgrounds, are involved in
testing; they need to understand their responsibilities and the responsibilities
of those around them.

A structured approach is the key to success, but testing relies on experience.
Our consultants share their experience and work through the essentials for
consistent, well documented testing based on sound strategies.

Who will the course benefit?

Everyone involved in the management or practice of software development,
testing and acceptance, including users, developers, project managers and
software purchasers. Managers, project managers, team leaders responsible
for preparing and implementing testing policies and strategies.

Course Objectives

To enable delegates to develop and implement an effective testing strategy;
plan and prepare appropriate tests for all phases of development and be able
to measure and control the quality of their testing.

Course Duration: 3 days
This course will enable delegates to:

      Manage, plan and prepare rigorous, formal, visible and repeatable
       tests that will fully exercise software, in the development of quality

      Apply different testing approaches (black box, white box, static and
       dynamic) to all stages of software development.

      Prepare test plans, strategy, specifications, procedures and controls to
       provide a structured approach to testing.

      Identify what is involved in acceptance testing, system testing,
       integration testing and unit testing, what should be tested when and by

      Document testing appropriately

      Apply the techniques and methods covered to testing packages.

      Describe the different types of testing tools available and identify the
       appropriate types of tools for their needs.
Course Content

Introduction and Approaches

      What is Testing
      Why Test
      Testing principles
      Types of testing, black box, white box, static and dynamic
      Testing throughout system development

Test Management

      The need to manage testing effectively
      Control and support of testing activities
      Identification of strategy, objectives, responsibilities
      Completion criteria and test environment
      Test policy
      Standards and procedures
      Quality

Acceptance Testing

      Users and operations’ testing responsibilities
      Scope and purpose of acceptance testing
      Combining business processes and test plans
      Development of acceptance test plans
      When to start testing
      Acceptance criteria

System Testing

      Scope and content of system testing
      Development of system test conditions and cases
      Test dependencies, run plans
      Control of testing and test documentation
      System test environment
      Sources of test data
      Expected results

Integration Testing

      Problems of integration
      Development of strategy and build plan
      Options available and their advantages and disadvantages
Unit Testing

      Definitions of unit testing
      Objectives, application of test strategies, procedures, planning and
      Development of conditions, cases, creation of data and expected

Testing Packages and RAD

      An overview of packaged software, selection and evaluation
      Applying testing techniques to packaged solutions and RAD

Testing Tools

      Types of tool available, their potential and limitations
      An approach to introducing test automation
      Sources of test automation information

Configuration Management

      Configuration management
      Change control
      Version control and release control
      Planning for change

To top