View this PageEdit this PageAttachments to this PageHistory of this PageHomeRecent ChangesSearch the SwikiHelp Guide
Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007

Fall2004 Midterm Review: Testing and Refactoring

1) SUnit - A testing framework for creating and running Unit tests in Smalltalk developed originally by Kent Beck. It has self-testing and reporting, that is it will test and report which test is broken. It also initializes and cleans up before and after tests, respectively.

for automated testing

2) Scenario-based testing - taking a "blackbox" representation of the program and testing based on customer actions. Basically, capturing the tasks of the customer and testing based upon them. This allows testing without need for Exhaustive testing. It comes in different forms, such as Equivalence partitions and Boundary Value testing.

scenario-based testing is used when automated testing won't work. here's andrew sayman's answer from a few semester's ago: "Scenario based testing is a form where one tests your expectations by describing them as scenarios. A given scenario might be to say that "Bob will want to modify number of oranges produced." You would then test your system with that scenario, to see if Bob can actually change the number of oranges. This is an effective testing measure when automated tests aren't possible. It is helpful in designing what the system should do, and making sure that it does that. An example of this is in the QA process for Mozilla. With each new release they have people run "smoketests" which are just simple scenarios that everybody will go through with their browser on a given day." -ellie

3) Writing tests before the code helps you understand a) what the code must do and b) helps you know when the code is done.


Link to this Page