


Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
An examination paper from the cork institute of technology, focusing on software testing for the bachelor of science (honours) in software development and bachelor of science (honours) in software development with computer networking programs. Instructions, duration, sitting, requirements, and five questions covering topics such as good testing practices, bug reporting, problem tracking systems, and equivalence classes. Questions require discussion, illustrative examples, and elaboration on various testing concepts.
Typology: Exams
1 / 4
This page cannot be seen from the preview
Don't miss anything!



Semester 2 Examinations 2008/
Module Code: SOFT 8017
School: Computing
Programme Title: Bachelor of Science (Honours) in Software Development – Award Bachelor of Science (Honours) in Software Development with Computer Networking - Award
Programme Code: KSDEV_8_Y4 and KDNET_8_Y
External Examiner(s): Mr. Ken Carroll Internal Examiner(s): Mr. John O’Brien
Instructions: Answer any four questions
Duration: 2 Hours
Sitting: Summer 2009
Requirements for this examination:
Note to Candidates: Please check the Programme Title and the Module Title to ensure that you have received the correct examination paper. If in doubt please contact an Invigilator.
Q1. (a) Good testing involves much more than just running the code a number of times to see if it “works”. Discuss. [10 Marks] (b) In the context of glass-box testing:
1. What does the term path testing refer to? 2. Coverage criteria specify a class of paths that should be tested. Elaborate on each of the following, commonly-used, coverage criteria: (i) Line coverage; (ii) Branch coverage; (iii) Condition coverage. Support your presentation with suitable, illustrative, examples. [15 Marks]
Q2. (a) In the context of reporting bugs in software artefacts, a good report is written, numbered, simple, understandable, reproducible, legible, and non-judgemental. Discuss. [15 Marks]
(b) Software bug reproduction is not always straightforward. There are many reasons why a tester or developer might not be able to achieve immediate bug reproduction. Elaborate on each of the following potential reasons: (i) Race conditions; (ii) Forgotten details; (iii) An effect of the bug makes replication impossible; (iv) The bug is a side-effect of some other problem; (v) Someone has interfered with the tester’s/developer’s work station. [10 Marks]
(c) Every interactive program moves from one visible state to another. A menu system is a simple example. Outline the steps involved in testing an interactive program that uses a menu system. [5 Marks]
Q5. (a) Test documentation facilitates the technical tasks of testing. Discuss. [10 Marks]
(b) Describe, in detail, James Bach’s 1998 “Framework for Good Enough Testing”. [15 Marks]
End of Exam!