OHJ-3060 Software Testing Course Project

News

• 5.12.2006 Check your unit test report results from IDLE. They have been there officially since 30.11.2006. The deadline for boomerangs is 8.12.2006 12:00.
• 29.11.2006 Deadline for unit test report boomerangs is 8.12.2006 12:00.
• 29.11.2006 Feedback on unit test reports is available in IDLE. A post in the news group contains instructions how to read it.
• 1.11.2006 See the news group to see the changes in the system testing.

Checklist for the project

1. Read this web page.
2. Find a team mate. This project is done in pairs. Finnish and foreign students are encouraged to work together. (You can use the news group to find a team mate.)
3. (8.9.2006) Register your team in IDLE.
4. Read the master test plan.

   ---

5. [TASK 1] Read the RFCs 2396 and 2732 for Task 1 and design system tests.
6. [TASK 1] (13.9.2006) [Register your team to the first review meeting. Teams with foreign students students should book their time from Antti Kervinen, Finnish groups may choose their assitant freely. Do not change your assistant during the project.]
7. [TASK 1] (deadline 26.9.2006 12:00) Return the system test plan (preferably a couple of days before the deadline). Template in Finnish SXW, DOC, RTF, PDF.
8. [TASK 1] (28.9.2006) Register your team to the feedback meeting.

   ---

9. [TASK 2] Read the code for Task 2 and design unit tests.
10. [TASK 2] (4.10.2006) [Register your team to the second review meeting.]
11. [TASK 2] (deadline 17.10.2006 12:00) Return the unit test plan (preferably a couple of days before the deadline). Template in Finnish SXW, DOC, RTF, PDF.
12. [TASK 2] (20.10.2006) Register your team to the feedback meeting.

    ---

13. [TASK 3] Implement and run the unit tests. Write a report.
14. [TASK 3] (deadline 14.11.2006 12:00) Return the unit test report and and the required files (preferably a couple of days before the deadline). Template in Finnish SXW, DOC, RTF, PDF

    ---

15. [TASK 4] Implement and run the system tests. Write a report.
16. [TASK 4] (deadline 5.12.2006 12:00) Return the system test report and the required files (preferably a couple of days before the deadline). Template in Finnish SXW, DOC, RTF, PDF

All registrations are made through IDLE system. If you have questions that are not answered in this web page, in the master test plan and in the news group, send mail to Antti Kervinen or visit his office (TF213).

Grading

An accepted report gives 0 to 4 points. If a report and the other requested material in tasks 3 and 4 do not meet the requirements, the report is rejected and the team will be given about a week to fix and resubmit their work. (Accepted reports cannot be resubmitted.) Resubmitted report is either accepted with 0 points or rejected in case the requiremets are still not fulfilled. To pass the course, one report must have been accepted in each task and you must have at least 5 points.

In the first two tasks it is possible (but not obligatory) to attend a review meeting. Those who attend the meetings are rewarded with one extra point in case their reports are accepted and the report did not already get the maximum points.

Feedback on the first two reports is given in obligatory feedback meetings. Both students in each team must attend at least one feedback meeting, and both feedback meetings should be attended by at least one student. (Attending a meeting requires physical presence.)

Deliverables

• Task 1:
  1. system test design document (paper, electronic)
• Task 2:
  1. unit test design document (paper, electronic)
• Task 3:
  1. unit test summary document (paper, electronic)
  2. fixed unit test design document (electronic)
  3. stubs, cpp-unit tests (electronic)
  4. Makefile (electronic)
     Make sure the code and the makefile work as required in the Master test plan page 19.
• Task 4:
  1. system test summary document (paper, electronic)
  2. fixed system test design document (electronic)
  3. CTC data (MON.dat) (electronic) NOT REQUIRED
  4. Mozilla output (electronic)

Submitting reports and other files

• You should not return anything in review meetings. To get the maximal benefit out of the meetings, you should take the (incomplete) test plan with you, and a list of topics you would like to discuss about.
• You should always return both electronic and paper versions of the reports before the deadlines.
  • The paper version should be returned to box 37, 40, 43, 46 if your assistant is AnttiJ, AnttiK, MikaM, MikkoS, respectively. The boxes are located in TC1 corridor, next to Zip restaurant. You are allowed to print (at most) two pages on both sides of a sheet.
  • The electronic version of the report must be in PDF format.
  • In tasks 1 and 2, return the PDF file as it is via IDLE system. Name the file 2006.TASKa.SNUM1.SNUM2.pdf where TASK is either 1 or 2 and SNUM1 and SNUM2 are the student numbers of the authors. For example, 2006.1a.123456.142424.pdf.
  • In tasks 3 and 4 you are required to return also other files in addition to the reports. Pack all the files (that is, everything that is required, including the report in PDF format) to 2006.TASKa.SNUM1.SNUM2.tar.gz package, for example 2006.3a.123456.142424.tar.gz. The file format is gzipped tar. You can create the package with command tar czvf ../packagename.tar.gz * in the directory that contains the report and the other files (in Solaris use gtar intead of tar). The report in the package should be again named 2006.TASKa.SNUM1.SNUM2.pdf and the fixed test design 2006.DESIGNTASKf.SNUM1.SNUM2.pdf, for example

    2006.3a.123456.142424.tar.gz	contains files
    unit test report	2006.3a.123456.142424.pdf
    fixed unit test design	2006.2f.123456.142424.pdf
    makefile	Makefile
    stubs and drivers	other files

    and

    2006.4a.123456.142424.tar.gz	contains files
    system test report	2006.4a.123456.142424.pdf
    fixed system test design	2006.1f.123456.142424.pdf
    NOT REQUIRED	MON.dat
    parser output	output.txt

  • Boomerangs should be returned similarly, but then the filenames should be 2006.TASKb.SNUM1.SNUM2.pdf and 2006.TASKb.SNUM1.SNUM2.tar.gz. That is, "a" is changed to "b" in the returned PDF (tasks 1 and 2) or package (tasks 3 and 4). Files in the package (in tasks 3 and 4) are named exactly as in the above tables (no "b"'s needed inside the packages). Both electronic and paper versions must be returned. In IDLE, use the corresponding boomerang submission tasks. For example, submit the electronic version of system test design document named 2006.1b.123456.654321.pdf to "System Test Design boomerangs" page in IDLE. Return the paper version to your assistant's box.

  Links

  • URL specifications.
  • IPv6 extension for URLs.
  • IEEE standard for software test documentation