Welcome to the course software testing project
The project in this year will be done in four phases:
- Phase 1: Planning of unit testing
- Phase 2: Execution and reporting unit tests
- Phase 3: Planning of system testing
- Phase 4: Execution and reporting system tests
In the unit testing phases we first plan what we are going to test and how (phase 1). Then we execute the
unit test and write a report from the results of our testing effort (phase 2). In
system testing part we will go though the same plan-design-execute-report flow (phases 3 and 4).
Your role in this project is to assemble a team of two testers
(that is you and your team mate) and your job is to do the testing (planning, execution of tests, reporting) as instructed in
the Master Test Plan [Master Test Plan].
The course assintants will guide your work by a voluntary preliminary review of 20 minutes during every phase. In that your
can make sure that you have approached the phase's goal in a correct manner. At the end of the phase, teams submit their work
via the IDLE system. The teams will get final feedback in an obligatory feedback meeting (15 min) or by IDLE (depending on the phase, see details below).
Basic rules
- Deadlines are always strict.
- Because there is some automatic checking involved, you MUST be sure that the names of submission items are correct and that all
compressed files have a correct directory structure.
- The time for the submission is ALWAYS 12 o'clock at NOON.
- Faults can be found from the documentation or other support material used in this course. You are welcomed to
report those findings to chief assistant.
Description of phases and tasks
Preparation for the project
- READ this web page.
- Find a team mate, because the project is done in pairs (that is 2 persons in a group). You can use the news group to find
a team mate.
- 5.9.2011 Registration in IDLE opens and you can register you and your team in IDLE.
- 14.9.2011 The team must be assembled in order to attend to the first voluntary review meeting.
- Read the Master Test Plan (Master Test Plan) and understand the tasks.
Phase 1: Planning and designing unit tests
Instructional lecture 5.9.2011 12:00-15:00 (in English)
Preliminary review (voluntary) [PRE1]
- Create a draft version of your plan and discuss it with your team's assistant
- The documentation must contain information as requested in Master Test Plan. Most essential content:
- Drafts for at least three test cases
- Some sign of using proper unit testing techniques (such as boundary value analysi, equivalence partitioning etc.)
- Some sign that you have really thought of the testing and prepared for the meeting
- These are criteria for gaining the possible extra point for this submissions
- Attend to your voluntary review session. [21.-23.9.2011]
- Register your team to the meeting at least one day before your meeting.
Plan unit testing and design unit tests [TASK1]
- Write the test cases using JUnit.
- Deadline 28.9.2011 12:00 Submit the unit test plan.
- Attend to the obligatory feedback meeting on [5.-7.10.2011]
- Register your team to the meeting at least one day before your meeting.
Phase 2: Execution and reporting of unit tests [TASK2]
- Run run the unit tests.
- Write the test report.
- Fix the test plan if requested.
- Deadline 26.10.2011 12:00 Submit the unit test report and the
required files.
- The outline of the report is given in the Master Test Plan.
- Make sure that your submission package is correct.
- 2.11.2011 Feedback is available in IDLE.
Phase 3: Planning of system testing
Instructional lecture 24.10.2011 12:00-15:00) (in English)
Preliminary review (voluntary) [PRE3]
- Create a draft version of your plan and discuss it with your team's assistant
- The documentation must contain information as requested in Master Test Plan. Most essential content:
- A good description of your test approach and your reason for selecting it
- Some sign that you have really thought of the testing prepared for the meeting
- These are criteria for gaining the possible extra point for this submissions
- Attend to your voluntary review session. [9.-11.11.2011]
- Register your team to the meeting at least one day before your meeting.
Plan system testing and design system tests [TASK3]
- Write the system test plan
- Choose your team's approach to the testing
- Write the test plan
- The outline of the pland document is given in the Master Test Plan.
- Deadline 16.11.2011 12:00 Submit your system test plan
- Attend to the feedback meeting. [23.-25.11.2011]
- Register your team to the meeting at least one day before your meeting.
Phase 4: Execution and reporting of system tests [TASK4]
- Implement the system tests
- Perform the system tests
- Write a test report
- Finalise the test plan as needed
- Deadline 7.12.2011 12:00) Submit the system test report and the required files.
- 14.12.2011 Final feedback will be available in IDLE.
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 IDLE, Antti Jääskeläinen (antti.m.jaaskelainen(AT)tut.fi).
Antti will be at his office (TF216) on every Tuesday from 11:30-12:30.
Grading
An accepted report gives 0 to 4 points, where zero means 'no points' and it is not a rejected work. If you are asked to fix
something, you must have that fixed next time you submit your work i.e. if your test plan has something wrong, you must deliver the
fixed plan along with the test report. You have 16 points at maximum to collect from the project. In addition to that there are 2
compensation points available that compensates the loss of points in any phase. However, if you get 4 points from each phase and 2
compensation points, you will still get 16 points.
In both planning phase (unit and system) it is possible (but not obligatory) to attend a review meeting. Those students who attend the meetings
may be rewarded with one extra point IF they show preparation for the session and provide the test plan drafts as required.
The course assistants decide whether the team is worthy of the extra point.
There are total 32 points available in the course (half from the project and half from the exam). For the right to
take the exam, you must have at least 5 points from project and all four project phases must be accepted (i.e. you have zero or more
points from each submission). To pass the course, you must have at least 5 points from exam and
roughly half of the total points (about 16 points depending on the overall grading level in
the course).
At any point of the course, if it turns out that students have submitted copied work,
they lose mozillion points and the possibility to pass the course. They may also expect
other very unpleasant consequences [in Finnish] (at least for them who copied and for
those whom work they copied WILL loose their right to use Lintula accounts).
Feedback on the plans is given in the 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
from the team. Also it is advisable to attend to those voluntary review meetings.
- Instructions for this are in the Master Test Plan;
- Please follow those instructions very carefully. (Failing to follow the instructions will cost points.)
Course documents and instructions
Templates for documents students create
- Note on document formats: All .doc suffix document templates are in Microsoft Word 97-2003 format and also work well with OpenOffice
- Unit testing templates
- System testing templates
- Test log templates (for approach B) -- copy the log to an appendix of the report
- For your plans and reports you can if needed also use the following generic project document templates (there is no content just style and layout information):
- Empty Document Template (Finnish) OpenOffice, Microsoft Word
- Empty Document Template (Finnish) OpenOffice, Microsoft Word
- Additionally, templates in Ohjelmistotekniikan laitoksen dokumenttirunkopankki are also available.
- For comparison, note also the IEEE 829 based document templates and how IEEE istructs their use in
IEEE 829 standard:
Applications and tools
Checklists
Glossaries
- Finnish translation of Standard glossary of terms used in Software Testing. Two versions of it are sorted differently: En-Fi,
Fi-En (both contains English defitions too).
Standards
Other
|