Learn Software Testing

With TechPartnerz

http://www.techpartnerz.com

Session 1

In this presentation..

What is Verification & Validation? Session 1

Verification Strategies.
Validation Strategies. Establishing a Software Testing Methodology. Test Phases. Session 2 Metrics. Configuration Management. Session 3 Test Development. Defect Tracking Process. Deliverables.
http://www.techpartnerz.com Your Partner for Professional Success 2013 TechPartnerz

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.

http://www.techpartnerz.com

Your Partner for Professional Success

2013 TechPartnerz

Verification Strategies
Verification Strategies comprise of the following:

1. Requirements Review. 2. Design Review. 3. Code Walkthrough.

4. Code Inspections.

http://www.techpartnerz.com

Your Partner for Professional Success

2013 TechPartnerz

Validation Strategies
Validation Strategies comprise of the following:

1. Unit Testing. 2. Integration Testing. 3. System Testing. 4. Performance Testing. 5. Alpha Testing. 6. User Acceptance Testing (UAT).

7. Installation Testing.
8. Beta Testing.
http://www.techpartnerz.com Your Partner for Professional Success 2013 TechPartnerz

Verification Strategiesin detail

Verification Strategy
Requirements Review

Explanation
The study and discussions of the computer system requirements to ensure they meet stated user needs and are feasible.
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. Formal analysis of the program source code to find defects as defined by meeting system design specification.

Deliverable
Reviewed statement of requirements.

Design Review Code Walkthrough Code Inspection

System Design Document, Hardware Design Document. Software ready for initial testing by the developer. Software ready for testing by the testing team.

http://www.techpartnerz.com

Your Partner for Professional Success

2013 TechPartnerz

Validation Strategiesin detail

Validation Strategy
Unit Testing

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

Deliverable
Software unit ready for testing with other system component. Portions of the system ready for testing with other portions of the system.

Integration Testing

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

System Testing

Testing of entire computer system. This Tested computer kind of testing can include functional and system, based on structural testing. what was specified to be developed.
Testing of the application for the performance at stipulated times and stipulated number of users. Stable application performance.

Performance Testing

http://www.techpartnerz.com

Your Partner for Professional Success

2013 TechPartnerz

Validation Strategiesin detail

Validation Strategy
Alpha Testing

Explanation
Testing of the whole computer system before rolling out to the UAT.

Deliverable
Stable application.

User Acceptance Testing (UAT) Installation Testing

Testing of computer system to make sure it will work in the system regardless of what the system requirements indicate. Testing of the Computer System during the Installation at the user place.

Tested and accepted system based on the user needs. Successfully installed application.

Beta Testing

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

Successfully installed and running application.

http://www.techpartnerz.com

Your Partner for Professional Success

2013 TechPartnerz

Establishing a Software Testing Methodology.

In order to establish software testing methodology and developing the framework for developing the testing tactics, the following eight considerations should be described: Acquire and study the Test Strategy. Determine the Type of Development project. Determine the Type of Software System. Determine the project scope. Identify the tactical risks. Determine when testing should occur. Build the system test plan. Build the unit test plan.

http://www.techpartnerz.com

Your Partner for Professional Success

2013 TechPartnerz

Type of Development Project

Type Traditional System Development Characteristics Uses a system development methodology. User knows requirements. Development determines structure. Requirements unknown. Structure pre-defined. Test Tactic Test at end of each task/step/phase. Verify that specs match need. Test function and structure. Verify that CASE tools are used properly. Test functionality. Test structure. Works best with release methods. Requires regression testing. Verify that functionality matches need. Test functionality. Test fit into environment.

Iterative development / Prototyping / CASE System Maintenance

Modify structure.

Purchased / Contracted Software

Structure unknown. May contain defects. Functionality defined in user documentation. Documentation may vary from software.
Your Partner for Professional Success

http://www.techpartnerz.com

2013 TechPartnerz

When Testing should occur..?

Testing can and should occur throughout the phases of a project. Requirements Phase Determine the test strategy. Determine adequacy of requirements. Generate functional test conditions. Design Phase Determine consistency of design with requirements. Determine adequacy of design. Generate structural and functional test conditions. Program (Build) Phase Determine consistency with design. Determine adequacy of implementation. Generate structural and functional test conditions for programs/units.
http://www.techpartnerz.com Your Partner for Professional Success 2013 TechPartnerz

When Testing should occur..?

Test Phase Determine adequacy of the test plan. Test application system.

Installation Phase Place tested system into production.

Maintenance Phase Modify and retest.

http://www.techpartnerz.com

Your Partner for Professional Success

2013 TechPartnerz

Types of Testing.
Two types of testing can be taken into consideration.

Functional or Black Box Testing. Structural or White Box Testing.

Functional testing ensures that the requirements are properly satisfied by the application system. The functions are those tasks that the system is designed to accomplish. Structural testing ensures sufficient testing of the implementation of a function.

http://www.techpartnerz.com

Your Partner for Professional Success

2013 TechPartnerz

Structural Testing.
Technique Explanation Example

Stress

Determine system performance with expected volumes.

Sufficient disk space allocated.

Execution

System achieves desired level of Transaction proficiency. turnaround time adequate. System can be returned to an operational status after a failure. Evaluate adequacy of backup data.

Recovery

http://www.techpartnerz.com

Your Partner for Professional Success

2013 TechPartnerz

Structural Testing.
Technique Explanation Example

Operations

System can be executed in a normal operational status.

Determine systems can run using document. Standards follow.

Compliance

System is developed in accordance with standards and procedures. System is protected in accordance with importance to organization.

Security

Access denied.

http://www.techpartnerz.com

Your Partner for Professional Success

2013 TechPartnerz

Functional Testing.
Technique Explanation Example

Requirements

System performs as specified.

Prove system requirements.

Regression

Verifies that anything unchanged still performs correctly. Errors can be prevented or detected and then corrected.

Unchanged system segments function. Error introduced into the test.

Error Handling

http://www.techpartnerz.com

Your Partner for Professional Success

2013 TechPartnerz

Functional Testing.
Technique Explanation Example

Manual Support

The people-computer interaction works.

Manual procedures developed.

Inter Systems

Data is correctly passed from system to system.

Intersystem parameters changed.

Control

Controls reduce system risk to an acceptable level.

File reconciliation procedures work.

Parallel

Old systems and new system are run and the results compared to detect unplanned differences.
Your Partner for Professional Success

Old and new system can reconcile.

2013 TechPartnerz

http://www.techpartnerz.com

End of session 1

http://www.techpartnerz.com

Your Partner for Professional Success

2013 TechPartnerz

About TechPartnerz

TechPartnerz is an IIT NIT alumni company providing end to end IT training solutions to Corporates, working professionals and Freshers TechPartnerz provides certification training programs for ITIL-Foundation, ITIL-Intermediate, PRINCE2-Foundation, PRINCE2-Practitioner, COBIT 5, Cloud Computing etc Our Software Training Portfolio includes training on QTP, Selenium, Loadrunner, Jmeter, SoapUI etc.

http://www.techpartnerz.com

Your Partner for Professional Success

2013 TechPartnerz

Thank You
For any queries feel free to contact TechPartnerz info@techpartnerz.com Follow TechPartnerz on facebook, Linkedin, twitter

http://www.techpartnerz.com

Your Partner for Professional Success

2013 TechPartnerz