Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Software Testing Exam for BSc in Software Development & Networking, CIT, 2010, Exams of Software Engineering

An examination paper for the software testing module (soft 8017) in the bsc (hons) in software development and bsc (hons) in software development & networking programmes at the cork institute of technology. The exam consists of five questions and lasts for two hours. The questions cover topics such as software testing principles, testing techniques, bug reporting, and bug handling.

Typology: Exams

2012/2013

Uploaded on 03/25/2013

digvijay
digvijay 🇮🇳

4.4

(16)

236 documents

1 / 4

Toggle sidebar

Related documents


Partial preview of the text

Download Software Testing Exam for BSc in Software Development & Networking, CIT, 2010 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 2009/2010 Module Title: Software Testing Module Code: SOFT 8017 School: Computing Programme Title: BSc (Hons) in Software Development BSc (Hons) in Software Development & Networking 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 2010 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) “Software testing is partially intuitive, but largely systematic.” Do you agree/disagree? State your reasons. [5 Marks] (b) In the context of software testing: (i) What is meant by the expression “complete program testing”? (ii) State three reasons why the “complete” testing of computer software artefacts is not possible. (iii) Why is it impossible to make a serious attempt at path testing without having access to an up-to-date code listing? [8 Marks] (c) In an article, entitled “Reasons to repeat tests”, J. Bach compares the activity of testing a software artefact to that of searching a minefield for mines. He states that “if you just travel the same path through the field again and again, you won’t find a lot of mines”. However, Bach does suggest, for the testing of software artefacts, ten specific scenarios where the exact repetition of a test is not unreasonable. Identify, and elaborate on any six such scenarios. [12 Marks] Q2. (a) Are testers who complain/comment on joining a software project late justified in their complaint? State your reason(s). [4 Marks] (b) In the context of software testing: (i) What is a review meeting? (ii) Why are review meetings important during software project work? (iii) Differentiate, briefly, between each of the following types of review meetings: Walkthrough; Inspection; Technical review. [9 Marks] (c) (i) Explain the following testing terms: Structural testing; Functional testing; Path; Subpath. [4 Marks] (ii) Differentiate between the following path-testing coverage criteria: Line coverage; Branch coverage; Condition coverage. Support your answer with suitable illustrative examples. [8 Marks]
Docsity logo



Copyright © 2024 Ladybird Srl - Via Leonardo da Vinci 16, 10126, Torino, Italy - VAT 10816460017 - All rights reserved