Testing Process

Testing Process
LiveTech
1. 2. 3. 4. 5.
What is Verification & Validation? Verification Strategies. Validation Strategies. Test Phases. Configuration Management.
6.
7.
Defect Tracking Process.

Deliverables.
LiveTech
What is Verification & Validation? Verification and Validation are the basic ingredients of Software Quality Assurance (SQA) activities. Verification checks whether we are building the right system, and
Validation checks whether we are building the system right.

LiveTech
Verification Strategies comprise of the following:
1. 2. 3. 4.
Requirements Review. Design Review. Code Walkthrough. Code Inspections.
LiveTech
Validation Strategies comprise of the following: 1. 2. 3. 4. Unit Testing. Integration Testing. System Testing. Performance Testing.
5.
6. 7.
Alpha Testing.
User Acceptance Testing (UAT). Installation Testing.
8.
Beta Testing.
LiveTech
Verification Strategies
Verification Strategy
Requirements Review
Explanation
Deliverable
The study and discussions of the computer system requirements to ensure they meet stated user needs and are feasible.
Reviewed statement of requirements.
Design Review
The study and discussion of the computer system design to ensure it will support the system requirements. Informal analysis of the program source code to find defects and verify coding techniques.
System Design Document, Hardware Design Document. Software ready for initial testing by the developer.
Code Walkthrough
Code Inspection
Formal analysis of the program source code to Software ready for testing find defects as defined by meeting system by the testing team. design specification.
LiveTech
Validation Strategies
Validation Strategy
Unit Testing
Explanation
Deliverable
Testing of single program, modules, or unit of code.
Software unit ready for testing with other system component.
Integration Testing
Testing of related programs, modules, or units of code.
Portions of the system ready for testing with other portions of the system. Tested computer system, based on what was specified to be developed.
Stable application performance.
System Testing
Testing of entire computer system. This kind of testing can include functional and structural testing.
Performance Testing
Testing of the application for the performance at stipulated times and stipulated number of users.
LiveTech
Validation Strategy
Alpha Testing
Explanation
Deliverable
Testing of the whole computer system before Stable application. rolling out to the UAT.
User Acceptance Testing (UAT)
Testing of computer system to make sure it will work in the system regardless of what the system requirements indicate.
Tested and accepted system based on the user needs.
Installation Testing
Testing of the Computer System during the Installation at the user place.
Successfully installed application.
Beta Testing
Testing of the application after the installation at the client place.
Successfully installed and running application.
LiveTech
Test Phases.
Requirements Review Design Review
Code Inspection
Code Walkthrough
Unit Testing
Integration Testing
Performance Testing
System Testing
Alpha Testing
User Acceptance Testing
Beta Testing
Installation Testing
LiveTech
Configuration Management Software Configuration management is an umbrella activity that is applied throughout the software process. SCM identifies controls, audits and reports modifications that invariably occur while software is being developed and after it has been released to a customer. All information produced as part of software engineering becomes of software configuration. The configuration is organized in a manner that enables orderly control of change.
LiveTech
The following is a sample list of Software Configuration Items: 1. Management plans (Project Plan, Test Plan, etc.)
2. Specifications (Requirements, Design, Test Case, etc.) 3. Customer Documentation (Implementation Manuals, User Manuals, Operations Manuals, On-line help Files) 4. Source Code (PL/1 Fortran, COBOL, Visual Basic, Visual C, etc.) 5. Executable Code (Machine readable object code, exe's, etc.) 6. Libraries (Runtime Libraries, Procedures, %include Files, API's, DLL's, etc.) 7. Databases (Data being Processed, Data a program requires, test data, Regression test data, etc.) 8. Production Documentation
LiveTech
Defect Tracking Process.

The Tester/Developer finds the Bug.
Reports the Defect in the Defect Tracking Tool. Status New
The concerned Developer is informed
The Developer fixes the Defect
The Developer changes the Status to Resolved
If the Defect re-occurs, the status changes to Re-Open
The Tester Re-Tests and changes Status to Closed
LiveTech
Deliverables.
The Deliverables from the Test team would include the following:
Test Plan. Test Scenario Documents. Test Case Documents. Defect Reports. Status Reports (Daily/weekly/Monthly). Test Scripts (if any). Product Sign off Document.
LiveTech

Testing Process

Uploaded by

Copyright:

Available Formats

Testing Process

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Testing Process

Uploaded by

Copyright:

Available Formats

Testing Process

Defect Tracking Process.

Validation checks whether we are building the system right.

Verification Strategies comprise of the following:

Requirements Review. Design Review. Code Walkthrough. Code Inspections.

Reviewed statement of requirements.

Testing of single program, modules, or unit of code.

Software unit ready for testing with other system component.

Testing of related programs, modules, or units of code.

User Acceptance Testing (UAT)

Tested and accepted system based on the user needs.

Successfully installed application.

Testing of the application after the installation at the client place.

Successfully installed and running application.

User Acceptance Testing

Defect Tracking Process.

Reports the Defect in the Defect Tracking Tool. Status New

The concerned Developer is informed

The Developer fixes the Defect

The Developer changes the Status to Resolved

If the Defect re-occurs, the status changes to Re-Open

The Tester Re-Tests and changes Status to Closed

You might also like