Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Software Testing Types, Methods and Levels

Information from http://www.tutorialspoint.com/software_testing/index.htm

Kimberly Rodriguez

on 4 February 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Software Testing Types, Methods and Levels

Software Testing Levels of Non-Functional Testing Unit Testing White Box Testing Types of Software Testing Portability Testing Usability Testing Load Testing vs Stress Testing Performance Testing Alpha Testing vs Beta Testing Acceptance Testing System Testing Integration Testing Levels of Functional Testing Grey Box Testing Methods of Software Testing TutorialsPoint.com References Security Testing Regression Testing 5 Steps for Functionality Testing Black Box Testing Manual
Automated Black Box Testing
White Box Testing
Grey Box Testing No Knowledge or Access to Source Code
User Interacts with System Interface
Data Driven & Functional Testing
Performed by End Users, Testers & Developers
Testing Based on External Expectations
Not Suited for Algorithm Testing Limited Knowledge of Internal Workings
Tester Has Access to Design and Databases
Better Prepared to Gather Test Data & Scenarios
Testing Done on Design & Database Diagrams
Not Suited for Algorithm Testing Investigating Internal Logic & Structure of Code
AKA ‘Glass Box Testing’ or ‘Open Box Testing’
User Has Access to Internal Workings of Code
Investigating Source Code to Find the Issue
Most Exhaustive and Time Consuming
Suited for Algorithm Testing Unit Testing
Integration Testing
System Testing
Regression Testing
Acceptance Testing Determine Functionality App is Meant to Perform
Create Test Data Based on App Specs
Output Based on Test Data & App Specs
Write Test Scenarios & Execution of Test Cases
Compare Actual & Expected Results Performed by Developers Before Given to Team

Separate Test Data Than the QA Team

Goal to Isolate Each Part of App & Ensure Working Correctly Testing Combined Parts to See if Work Together
Bottom Up: Begins with Unit Testing
Top Down: Highest Level Modules Tested First
Bottom Up is More Common
Concluded With Multiple Tests of Complete App
Tries to Mimic Scenarios the Customer will Encounter Tests the System as a Whole
1st step in Software Development Life Cycle
Rigorous Testing for Quality Standards
Performed by a Specialized Testing Team
Enables Parties to Test, Verify and Validate Business Requirements and Architecture Performed When a Change is Made in App
Ensures Changes did not Cause Other Issues
Increases Speed of App to the Market
Helps to Minimize Compromises to Timeline
Ensures a Business Rule was not Violated Most Important & Performed by QA Team
Does it Meet Intended Specs & Client Requirements?
Points Out Cosmetic Errors & Interface Gaps
Points Out Bugs That Result in System Crashes
Points Out Major Errors in Application
Alpha vs Beta Beta
After Successful Alpha Testing
AKA Pre-Release Testing
Tested on a Sample of Intended Audience
Users Install & Run App & Give Feedback Alpha
First Stage in QA & Developer Teams
Combination of Unit, Integration & Systems Testing
Spelling Mistakes, Broken Links, Unclear Directions
Test Loading Times & Latency Problems Performance Testing
Usability Testing
Security Testing
Portability Testing Identifies Bottlenecks & Performance Issues:
Network Delay | Client Side Processing |
Database Transaction Processing | Server Load Balancing
Data Rendering
Testing: Speed | Capacity | Stability | Scalability
Qualitative or Quantitative
Load Testing vs Stress Testing Stress Testing
Test Under Abnormal Conditions
Apply Load Beyond Limits
Identifies the Breaking Point
Example: Restart a Network Port Load Testing
Apply Max Software Access
Manipulate Large Input Data
Normal & Peak Conditions
Identifies Max Capacity A Black Box Testing Technique
Observes Users Through Operation
Many Definitions of This Level of Testing (Nielsen)
Efficiency of Use
Errors & Safety
Satisfaction Usability Testing Different than UI Testing Identifies Security & Vulnerability Issues
Confidentiality | Integrity | Authentication
Availability | Authorization | Data Security
SQL Insertion Attacks | Injection Flaws
Session Management Issues
Cross-Site Scripting Attacks
Buffer Overflow Vulnerabilities
Directory Traversal Attacks Investigate Whether Can Re-use or Move Software
-Transfer Software from One Computer to Another
-Build an Executable to Run on Different Platforms
A Sub-Component of Systems Testing
-Testing on Different Environments
-Differing Hardware, Operating Systems & Browsers Types | Methods | Levels
Full transcript