Principles Of Testing And Quality Assurance In ICT

1792 Words4 Pages

Written Research Report

COMP. 6115 Testing & Quality Assurance in ICT

Teina Ellison - 2006000658

Table of Contents
Q1. Ten Generally Accepted Principles of Quality Applied to Software Testing - (30 Marks) 3
Q2. Quality Assurance and Validation Techniques of Software Testing - (12 Marks) 4
Q3. Application of Review Procedures , Including Formal and Informal Reviews when Black Box Testing - (10 Marks) 5
Q4. Application of Review Procedures , Including Formal and Informal Reviews when White Box Testing - (10 Marks) 5
Q5. Distinguishing Properties of Different Types of Tests and Where They are Used : Explained - (12 Marks) 5
Q6. Differences Between Testing Axioms and Myths : Explained - (6 Marks) 6
7. Referencing and Citation - (6 Marks) 6

Q1. Ten Generally Accepted Principles of Quality Applied to Software Testing - (30 Marks)
The software testing principle of quality is correctly defined and explained, in description, in full; Answer presented as a paragraph of at least three or four sentences (10x3/30)
Principle 1 : A necessary part of a test case is a definition of the expected output or result.
Test cases must have two components, a. A description of the input data to the program, and b. A precise description of the correct output of the program for that set of data. If the result of outputs have not been predefined results can be misinterpreted as correct and be therefore erroneous. Outputs should be precisely defined in advance so the results can be examined to see if the test case meets the defined expectations or not.
Principle 2 : A programmer should avoid testing his or her own program.
When a programmer has "constructively" written a program it is very difficult to change to a "critical" perspective and...

... middle of paper ...

...ng.
A Myth is a widely held but false notion. Most myths in software testing relate that testing is expensive and time consuming, when it is appropriate to test and who can test programs and what the outcomes of testing should be. Testing a program early saves both time and costs, bugs are found quicker and it takes longer to fix bugs than to test and find them and it is more efficient to test a program during its development.
Testers are incorrectly perceived to be responsible for the quality of a product, that defects within a program are the fault of testers and a that tested program will be bug free while conversely another testing myth is that anyone can test a software program and being only responsible for finding bugs.
7. Referencing and Citation - (6 Marks)
Correct in-text citation; List of references in full accord, APA-6th (grouped by media sourced) (6)

Open Document