Software Testing Examination 2008-09, Cork Institute of Technology, Exams of Software Engineering

Download Software Testing Examination 2008-09, Cork Institute of Technology and more Exams Software Engineering in PDF only on Docsity! Page 1 of 4 CORK INSTITUTE OF TECHNOLOGY INSTITIÚID TEICNEOLAÍOCHTA CHORCAÍ Semester 2 Examinations 2008/09 Module Title: Software Testing 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_Y4 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. Page 2 of 4 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]