ITIS 3320 Introduction to Software Testing and Assurance

Projects

There will be two class projects:

• White-box Testing Project
• Black-box Testing Project.

White-box Testing Project

50 points

The white box testing project will consist of obtaining a specified program and testing it. The tester will be able look at the source code and run the program interactively to test and debug it. The tester can use any resources available in the computer lab in Woodward 335.

The program will have deliberately injected bugs for you to find. For the project you will create a test plan, create and execute tests, and document and report errors found. You may assume the product is still in development and this is the first release to you for testing. Assume an acceptance test has been run and it has passed. Some of the errors may be minor, e.g. misspellings, etc. The program is a Java applet and consists of two parts: an HTML file with the code execute the Java applet (TicTac.htm), and the Java module (TicTacMine.java is the source).

Again, you can use any tools available in the lab in Woodward 335. The minimal tools required will be an editor (Notepad would do) and the Java compiler. A tool like Netbeans could be used look at the code and utilize its formatting capabilities to analyze the source.

• Program:

  TicTac: a Java Applet

  Source code:

  • TicTacMine.java
  • TicTac.htm
• Access:
  • Run program:
    3320GlassBox\TicTac.htm
  • To view and copy source:
    3320GlassBox\TicTacMine.java

Basic specifications:

• The tic-tac-toe squares should look square on a monitor.
• Standard tic-tac-toe rules
• "X" starts
• "X" and "O" alternate
• 3 in a row wins
• across
• up-down
• diagonally
• "New Game" clears board
• "About": mouseover changes foot title to the "programmer's" name: ITIS3320 Glass Box
• Background squares should be light blue
• After a win is detected the winning squares should be changed to black

Find and document errors in the program in two passes. Schedule:

• Program will be bebugged and available by February 12 (Thursday)
• First pass testing errors to be found and reported by February 26 (Thursday)
• Those errors will be "fixed" by the program group by March 5 (Thursday)
• Final test results report due March 26 (Thursday)

Deliverables:

• February 26 (Checkpoint - 20 pts)
  • Basic test plan
  (First Cycle)
  • Inputs and outputs
  • Boundaries
  • Test sets
  • Test results
  • Source code printout with your "fixes"
          Either:
    • Highlighted errors with fixes hand printed
    
    -or-
    • Fixed code with comments (and highlighted)
  • PR "tickets"
  • Errors found for to be fixed for next test cycle
  • Use your forms
• March 26 (Final Report - 50 points)
  • Complete Test Plan
  (First and Second Cycle)
  • Overview
  • Definitions
  • Test cases
  • Any support material
  • Fixed source code printout with your "fixes"
          Either:
    • Highlighted errors with fixes hand printed
    
    -or-
    • Fixed code with comments (and highlighted)
  • Regression test plan
  • PR "tickets"
  • First Cycle
  • Second Cycle
  • Summary

Notes:

1. You may use the instructor as a resource in the role of:
• the programmer
• the designer/architect
• the project manager
2. There have been between 5 and 20 deliberate errors injected into the code
3. There are an unknown number of unintentional bugs (I would hope 0 but we know better)

GB PTR Status

Return to top

Black-box Testing Project

100 points

The Black-box Testing project will consist of testing a product only using its inputs and outputs. The source code will not be available. The main tools available to the testers will be their own wits. For the black box text the tester will not need to test the whole program, just a significant single function of it.

The program you select most likely will still have errors remaining. It will not be necessary for you to find errors (but it would be nice). Your task is to create a test plan, create tests, execute the tests and document the process and results.

• Program:
  • Any program installed on the Windows computers in the Woodward 335 Computer lab
  • Select a significant portion of the program function to test
  • Report selection of your program and functions to be tested (Instructor approval required)
• Teams:
  • ~33 students
  • 8 teams
  • 5, 4, 4, 4, 4, 4
  • Random Draw
  • Team do decide their own structure
• Grade:

  Black Box Testing Grade Criteria

  Points	Area
  60 pts	Team project grade
  40 pts	Individual contribution*
  *Instructor interview of the team members

• Documentation!
  • Team Members
  • Team Structure
  • Test Plan
  • Test Results
  • Conclusion
• Bonus points:
• Collaboration
• 10% bonus
• Collaborate/coordinate test with another group
• Same program, different function
• Must be documented
• Presentation
• 10 point Homework bonus for each team member who actively participates in the Black Box Project Presentation
• End sheet with typewritten names and signature
• No signature - no grade!

Overall:

View the documentation level as if this was going to be audited e.g.: All work should be documented W.R.T. team members, structure, roles, etc. Include dates, and where appropriate, locations.

Teams and Project Dates:

Return to top