2c: Software Testing

Top/public/assessment/Outcomes/1/1a/csci3030

2c: Software Testing
Responsibilities for CSCI 3030

Note. Before teaching this course, consult the Response section of the assessment data page for a recent term of this course. Be sure to do what the Response section says should be done.

Reinforcement and initial assessment
Here, the topic is reinforced with additional instruction and the student continues to put the topic to use. Student learning is assessed. The setting for student learning In CSCI 3030, general software testing concepts are introduced, including different levels of testing (unit testing, integration testing, system testing), different testing objectives (acceptance testing, alpha and beta testing, regression testing), and different classifications for testing (white-box and black-box testing). Information on using unit testing tools, focusing on JUnit, is reinforced. Students are required to develop a test plan for their projects, including a traceability matrix linking test cases to specific requirements, and must document the steps for each test case. Students are required to use automated unit testing tools. Rubric Good. Students score a composite of 2.5 on test-related questions on the exam (normed from 0 to 3 points). The student test plan includes detailed tests, and the traceability matrix is complete. Automated tests are repeatable with possible manual intervention. Satisfactory. Students score a composite of 2.0 on test-related questions on the exam (normed from 0 to 3 points). The student test plan includes tests with most details present, and the traceability matrix is mostly complete, with 80% of requirements covered. Automated tests are repeatable with possible manual intervention. Unsatisfactory. A student's work is unsatisfactory if it does not meet any of the above criteria. Goal At least 75% of students that pass CSCI 3030 are rated as either satisfactory or good. At least 25% of students that pass CSCI 3030 are rated as good.

Reinforcement and initial assessment

Here, the topic is reinforced with additional instruction and the student continues to put the topic to use. Student learning is assessed.

The setting for student learning

In CSCI 3030, general software testing concepts are introduced, including different levels of testing (unit testing, integration testing, system testing), different testing objectives (acceptance testing, alpha and beta testing, regression testing), and different classifications for testing (white-box and black-box testing). Information on using unit testing tools, focusing on JUnit, is reinforced. Students are required to develop a test plan for their projects, including a traceability matrix linking test cases to specific requirements, and must document the steps for each test case. Students are required to use automated unit testing tools.

Rubric

Good. Students score a composite of 2.5 on test-related questions on the exam (normed from 0 to 3 points). The student test plan includes detailed tests, and the traceability matrix is complete. Automated tests are repeatable with possible manual intervention.

Satisfactory. Students score a composite of 2.0 on test-related questions on the exam (normed from 0 to 3 points). The student test plan includes tests with most details present, and the traceability matrix is mostly complete, with 80% of requirements covered. Automated tests are repeatable with possible manual intervention.

Unsatisfactory. A student's work is unsatisfactory if it does not meet any of the above criteria.

Goal

At least 75% of students that pass CSCI 3030 are rated as either satisfactory or good. At least 25% of students that pass CSCI 3030 are rated as good.