Week 10
Upcoming SlideShare
Loading in...5
×
 

Week 10

on

  • 479 views

 

Statistics

Views

Total Views
479
Views on SlideShare
479
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Week 10 Week 10 Presentation Transcript

  • Testing Amy Power Tim Read Shanon Hentges
    • Test Plan
    • Test Plan Standards
    • Types of Test Plans
    • What is a Test Case?
    • Why Write Tests?
    • Testing Software
      • NUnit
      • Cactus
      • Visual Studio.NET 2005
    • Questions?
    Agenda
  • Test Plan
    • The role of a test plan is to prescribe the scope, approach, resources, and schedule of the testing activities. To identify the items being tested, the features to be tested, the testing tasks to be performed, the personnel responsible for each task, and the risks associated with this plan.
  • Test Plan Standards
    • IEEE Standard 829 on Software Testing Documentation
      • ( http://72.14.207.104/search?q=cache:ww1LAhB3ST8J:se.inf.ethz.ch/teaching/ss2005/0050/exercises/IEEE%2520Std%2520829-1998%2520test.pdf+IEEE+Standard+829+&hl=en )
  • Types of Test Plans
    • Unit Test
      • Tests which check the correctness of a particular module of code. By testing the parts of a program first and then testing the sum of its parts will make integration testing easier.
    • Integration Test
      • Tests that are executed to ensure there is a connection with the different logic layers
    • System Test
      • Occurs when the project is implemented with business computers outside the test area
    • Acceptance Test
      • Occurs when the finished project is implemented and is tested by users within the company
  • What is a Test Case?
    • A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement of the program.
  • Why Write Tests?
    • Tests Reduce Bugs in New Features
    • Tests Reduce Bugs in Existing Features
    • Tests Are Good Documentation
    • Tests Reduce the Cost of Change
    • Tests Improve Design
    • Tests Allow Refactoring
    • Tests Constrain Features
    • Tests Defend Against Other Programmers
    • Testing Forces You to Slow Down and Think
    • Testing Makes Development Faster
    • Tests Reduce Fear
    • http://www.onjava.com/pub/a/onjava/2003/04/02/javaxpckbk.html?page=last
  • Testing Software
    • CSUnit
    • JUnit
    • NUnit
    • Cactus
    • Visual Studio.NET 2005 Team System
  • NUnit
    • NUnit is an open source unit testing framework for Microsoft .NET. It serves the same purpose as JUnit does in the Java world.
    • Initially ported from JUnit, the current release, version 2.2, is the fourth major release of this xUnit based unit testing tool for Microsoft .NET.
    • It is written entirely in C# and has been completely redesigned to take advantage of many .NET language features.
    • http://www.nunit.org/
  • NUnit
  • Cactus
    • Cactus is a simple test framework for unit testing server-side java code (Servlets, EJBs, Tag Libs, Filters, ...).
    • The intent of Cactus is to lower the cost of writing tests for server-side code. It uses JUnit and extends it.
    • Cactus implements an in-container strategy, meaning that tests are executed inside the container.
    • http://jakarta.apache.org/cactus/
  • Visual Studio.NET 2005
    • Writes test cases for you to test your Business Logic Layer for C#, J#, VB and ASP.Net
    • Bradshaw Marina
      • Shows an example of how VB.Net code from the business logic layer is analyzed and test cases are generated for that code.
  • Visual Studio.NET 2005
  • Questions?