Test Cases - PowerPoint PPT Presentation

1 / 11
About This Presentation
Title:

Test Cases

Description:

... created at the beginning of the system development life cycle ... System Testing. Requirement -Ensures that the integration testing didn't introduce new errors. ... – PowerPoint PPT presentation

Number of Views:171
Avg rating:3.0/5.0
Slides: 12
Provided by: Autho201
Category:
Tags: cases | test | testing

less

Transcript and Presenter's Notes

Title: Test Cases


1
Test Cases
  • Danny Roes
  • Karam Yousif
  • Kris Koch

2
Introduction
  • Test cases are a series of tests that each have a
    specific objective and will be conducted by the
    testers
  • Should be created at the beginning of the system
    development life cycle
  • Continuously updated as development evolves

3
Developing a Test Case
  • Need to know the
  • Purpose of the test
  • Attributes being tested
  • Event that will cause the attribute to change
  • Expected result
  • Actual result
  • Pass or fail

4
Unit Testing
  • Black-Box
  • - Focus on if the class meets
    the requirements
  • Used for normal testing
  • White-Box
  • - Reviewing code for errors that may not be
    found from Black-Box testing
  • Used for when the complexity is high

5
Integration Testing
  • User Interface
  • -Test every control on the UI (such as menus and
    keyboard shortcuts)
  • Used for normal integration testing
  • Use-Case
  • -Go through every use case
  • Used with interface testing since it does not
    test all of the interfaces

6
Integration Testing continued
  • Interaction
  • -Testing each class on its own until all tests
    are successful, then test all classes together
  • Used for data processing
  • System Interface
  • -Testing communication and data transfers
    between systems
  • Used when the system exchanges data with another
    system

7
System Testing
  • Requirement
  • -Ensures that the integration testing didnt
    introduce new errors.
  • -Checks for improper actions (ex. Entering blank
    records)
  • Used for normal testing
  • Usability
  • -System ease of use
  • Used for when the user interface is important

8
System Testing continued
  • Security
  • -Testing the system infrastructure for security
    holes and risks, as well as disaster recovery
  • Used when security is important
  • Performance
  • -Testing system and database load (large volume
    of users and data)
  • Used for when system speed is important

9
Acceptance Testing
  • Alpha
  • -Internal testing of previous tasks to ensure
    they accept the system
  • Used for normal acceptance testing
  • Beta
  • -Users monitor system for errors or improvements
    by entering real data
  • Used for normal acceptance testing

10
Sample Test Plan
11
Questions?
Write a Comment
User Comments (0)
About PowerShow.com