Show minor edits - Show changes to markup
Added lines 1-51:
Assigned Date: Tuesday, Feb. 28, 2006
Due Date: Thursday, Mar. 16, 2006
Due Time: 11:55pm
Last modified on February 27, 2006, at 04:07 PM (see updates)
This assignment focuses on Unit Testing. You are expected to work in isolation (without access to any resources other than the class textbook, class notes, and the instructor).
Develop a thorough test suite for Dale's Chapter 3
SortedStringList ADT specification.
- First create a stubbed implementation of the given ADT.
- Again, do NOT implement the complete functionality.
- Within your classes, provide only method signatures, and empty bodies (for void methods) or dummy return statements (for non-void methods).
- Using BlueJ's jUnit functionality, implement your tests as jUnit test methods.
- Focus on functional cohesion, i.e., a test method should focus only one bit of functionality. The smaller, the better.
Your test methods should be documented via javadoc. One should look at your javadoc API to determine the extent of your test suite.
- Open your BlueJ project.
- Open (edit) each source file and generate the class interface (javadoc). This can be done within the editor window either by pressing CTRL/J , or selecting the Interface drop-down menu item (on the right). (Note: This is necessary to generate your documentation for grading.)
- Under the Project menu, click Create Jar File... . In the dialog box that opens, select Include Source, and press Continue.
- Verify that the
.jar file is correct, by using the '
jar xvf file.jar' command, where
file.jar is your archive. Your
.jar file should contain:
Readme.txt (see Widget for a sample).
- Any files generated automatically by BlueJ (e.g.,
- A doc subdirectory with the Javadoc API documentation generated by BlueJ, for each of the classes above.
In other words, I should be able to unzip your submission and run it without modifications or additions.
- Email the generated
.jar file to firstname.lastname@example.org, by the due date and time.