Acceptance testing
1 / 16

Acceptance Testing - PowerPoint PPT Presentation

  • Uploaded on

Acceptance Testing. CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 30, 2007. Outline. Role of Acceptance Testing Other Paths to Acceptance Agile Approach. Requirements. High-level Design. Low-level Design. Code. Unit Testing. Integration Testing.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'Acceptance Testing' - symona

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Acceptance testing

Acceptance Testing

CSSE 376, Software Quality Assurance

Rose-Hulman Institute of Technology

March 30, 2007


  • Role of Acceptance Testing

  • Other Paths to Acceptance

  • Agile Approach

Lifecycle testing relationships


High-level Design

Low-level Design


Unit Testing

Integration Testing

System Testing

Acceptance Testing

Lifecycle Testing Relationships

Requirements as use cases
Requirements as Use Cases

  • For each use case enumerate a set of scenarios

  • Construct a test case for each scenario

  • Construct a test suite to run the test cases

Other paths to acceptance
Other Paths to Acceptance

  • Beta testing

    • Distribute system to volunteers

    • Collect change requests, fix, redistribute

    • Collect statistics on beta use

  • Shadowing

    • Collect or redistribute real-time use of existing system

    • Compare results

    • Collect statistics

Agile approach framework for integrated test fit
Agile Approach: Framework for Integrated Test (FIT)

  • Developed by Ward Cunningham as an extension of xUnit framework

  • Encourages customer participation via simple tables

Story driven development
Story-Driven Development

  • Customers write stories

  • Developers develop code to realize each story

  • Customers and developers work together to create tests of each story

Why do we need a wiki
Why Do We Need a Wiki?

  • Lower the barrier to customer participation

  • Easy to keep up-to-date

Fixture connection between test system and application
Fixture: Connection Between Test System and Application

  • When "Test" button is pushed a fixture is called to process the table

  • The fixture delegates to underlying application code

  • Fixture code is like xUnit TestCase code

    • extends base class

    • may create objects for multiple tests

Common table formats
Common Table Formats

  • ColumnFixture

    • each row specifies one input and one output

  • RowFixture

    • first row is input, remaining rows are output

  • ActionFixture

    • each row is either an action to perform or a value to check