General Questions

Question 1

• What is software?

Answer 1

o Collection of computer programs, procedure, rules, associated documentation and data
o Describe various views of a system for various stakeholder

Question 2

• Whom is it developed for?

Answer 2

o General – general market to be sold to multiple customers

o Customized – single customer according to their specifications

Question 3

• Commonly accepted challenges in large software systems

Answer 3

o Complexity – software represents knowledge
o Non-functional requirements – work and documentation distribution
o Team development – work and documentation distribution
o Long-lived – reusable documentation
o Lay-users – they are not CS

Question 4

• Goal Software Testing

Answer 4

o	Increase quality of the software by
o	Match requirements
o	Few Faults
o	Reliable
o	Usable

Question 5

• Role of Thumb cost of defect

Answer 5

o Specification 1x
o Implementation 10x
o Test 100x
o Production 1.000x

Question 6

• Test requirements

Answer 6

o Specific things that must be satisfied or covered during testing
o Every statement might be a test requirement and must cover every functional requirement

Question 7

• Test criterion

Answer 7

o Collection of rules and Processes that define test requirements over every statement and cover every functional requirement

Question 8

• Validation

Answer 8

o Process of evaluating software at the end of software development to ensure compliance with intended usage

Question 9

• Verification

Answer 9

o The process of determining whether the products of a given phase of the software development process fulfil the requirements established during the previous phase

Question 10

• What is software testing

Answer 10

o Process of executing a software system to determine whether it matches its specification and executes in its intended environment

Question 11

• Types of Testing

Answer 11

o Acceptance testing
 Fulfil users and customers expectations
o Reliability testing
 Tests reflect frequency of user input and reliability estimation
o Usability testing
 Checks usability point of view
o Defect testing
 Tests designed to discover system defects
o Compatibility testing
 Application works with different configurated systems
o Performance testing
 Evaluate and understand application scalability
o Stress testing
 Test system beyond maximum designed load

Question 12

• Testing levels

Answer 12

o Component (unit) testing
 Testing individual program components
o Integration testing
 Testing groups of components integrated to create a system or subsystem
o System testing
 Testing the entire software in its expected environment

Question 13

• Approaches to integration testing

Answer 13

o Top-Down testing
 Start with high level system and replace individual components by stubs
o Bottom-up testing
 Integrate individual components in levels until complete system is created

Question 14

• Software fault:

Answer 14

o A static defect in the software

Question 15

• Software error:

Answer 15

o An incorrect internal state that is the manifestation of some fault

Question 16

• Software failure:

Answer 16

o External, incorrect behaviour with respect to the requirements or other description of the expected behaviour

Question 17

• Fault and Failure Model

Answer 17

o RIPR – conditions necessary for failure to be observed
o Reaches:
 Location or locations in the program
o Infects
 The state must be incorrect
o Propagates
 Infected state must couse some output or final state to be incorrect
o Reveals
 Must observe the part of the incorrect portion of the program state

Question 18

• Software Observability

Answer 18

o How easy it is to observe the behaviour of a program in terms of its outputs, effect and other hardware and software components

Question 19

• Software Controllability

Answer 19

o How easy it is to provide a program with the needed inputs, in terms of values, operations and behaviours

Question 20

• Types of Test Activities

Answer 20

o Test Design (Criteria based and Human based)
o Test Automation
o Test execution
o Test evaluation

Question 21

• Test activity 1A)

Answer 21

o Test Design – Criteria Based
o Design test values to satisfy coverage criteria or other goal
o Knowledge of discrete maths, programming and testing

Question 22

• Test activity 1B)

Answer 22

o Test Design – Human Based

o Design test values based on domain knowledge of the program and human knowledge of testing

Question 23

• Test activity 2

Answer 23

o Test Automation

o Embed test values into executable scripts

Question 24

• Test activity 3

Answer 24

o Test execution

o Run tests on the software and record the results

Question 25

• Test activity 4

Answer 25

o Test evaluation

o Evaluate results of testing, report to developers

Question 26

• Other test activities

Answer 26

o Test management: set policies, organize team, interface with development
o Test maintenance: save test for reuse as software evolbes
o Test documentation: keep documentation, ensure traceability

Question 27

• Coloured Box testing

Answer 27

o Black box testing – derive tests from external description of the software, including specifications, requirements and design
o White Box testing – derive tests from the source code internals of the software, specifically including branches, individual conditions and statements
o Model based testing – derive tests from a model of the software (UML)

Question 28

• Advantages of coverage criteria

Answer 28

o Search for input space
o Minimize overlap in the tests
o Maximize the bang for the buck
o Provide traceability from software artefacts to tests