General Test Overview

Question 1

Why do we engineer software?

Answer 1

To solve customer’s problem.
To produce quality product within budget and scheudle.
To show the product (software) is indeed high quality.

Question 2

What is a problem?

Answer 2

A difference between things as desired and things as perceived.

Question 3

Stakeholders

Answer 3

Those who have a stake in the change being considered and who stand to gain or lose from the change.

Question 4

Testing Original Purpose:

Answer 4

Demonstration of proper behavior or quality demonstration.

Question 5

Testing New Purpose:

Answer 5

Defect Detection and Reduction.
Archieve defect-free software.

Question 6

Oracle

Answer 6

The expected behavior of an operation.

The actual output should be compared with the “Oracle”

Question 7

Ad-Hoc Testing

Answer 7

“Run and Observe”
One way to structure is to build a checklist

A type of informal testing that is performed without any formal test plan or test cause creation.

Question 8

Ad-Hoc Drawbacks

Answer 8

Lack of structure
Likely to miss and repeat oneself.
Whole Process is hard to repeat.

Question 9

Systematic Testing

Answer 9

Process is explicitly defined.
Testing with checklists.

Question 10

Reliability

Answer 10

Probablity of failure-free operation for a specific period or a given set of input under a specific environment.

Question 11

Creativity

Answer 11

Ability to produce work that is both Novel and Appropriate.

Question 12

How to measure creativity in RE?

Answer 12

Rate the requirements at a 5 point Likert Scale.
Kappa Statistic : Show the level of agreement among participants.

In recent Years, we rate Clarity, Novelty and Usefulness.

Question 13

Requirement Based Testing

Answer 13

Address 2 Major Issues:
1. Check/Validate the requirements for Correctness, Completeness, Ambiguity, and Logical Consistency.

2. Designing a set of test cases for requirements from a black box perspective.

Question 14

Quality Assurance:

Answer 14

To ensure that few , if any, defects remain in the software when it is delivered to its customers or released to the market.

Question 15

Error

Answer 15

A mistake made by a programmer or software engineer which caused the fault, which in turn may cause a failure.

Question 16

Fault

Answer 16

Condition/ Internal characteristic that may cause a failure in the system.

Question 17

Failure

Answer 17

Inability of the system to perform a function according to its specification due to some fault.

Question 18

Defect Relationship

Answer 18

Errors causes Faults.
Faults causes Failures.

Question 19

TDD

Answer 19

A software development process where a unit’s test are written before the unit’s implemention and guide the unit’s development as the tests are executed repeatedly until they all succeed, signaling complete functionality.

Question 20

TDD Process Steps

Answer 20

Red:
Write a new test for a section.
Verify failure of the new test and the success of existing tests.

Green:
Write code to implement, modify or develop the unit.
Repeat until the tests pass.

Refactor:
Refactor the code to improve non-functional code structure, style, and quality.
Confirm tests pass.

Repeat.

Question 21

Unit

Answer 21

The smallest executable or testable component of a system.

Question 22

Unit Testing vs TDD

Question 23

Input Domain

Answer 23

Space of all allowable test points

Question 24

Input SubDomain

Answer 24

Subset of input domain defined with a concrete relationship

Question 25

Domain Partition

Answer 25

Partition the input domain into a series of subdomains.

Question 26

Specification

Answer 26

Defines each dimension separately

Question 27

Boundary

Answer 27

Where 2 subdomains meet.

Question 28

Different Types of Points

Answer 28

Boundary Point: Point on Boundary Interior Point: Point on subdomain but not on boundary Exterior Point: Point not in the subdomain nor boundary. Vertex Point: Point where 2 or more boundaries meet.

Question 29

Boundary Types

Answer 29

Closed - All boundary points belong to the subdomain. Open - None of the boundary points belong to the subdomain

Question 30

Problems in Partitioning

Answer 30

Ambiguity: Under-defined/incomplete Contradictions: Over-defined/Overlap Key: Sub-Domians form a partition.

Question 31

Types of boundary Problems

Answer 31

Closure Problem Boundary Shift Missing Boundary Extra Boundary

Question 32

EPC

Answer 32

Extreme points test the limits of the system. # Test Case = 4^n + 1 Good for Closure and Missing Boundary Problems.

Question 33

Weak Nx1

Answer 33

Pick the OFF point so close to the boundary that any small amount of boundary change would change the processing mode of the test points/cases defined.

Question 34

ON Point

Answer 34

ON the boundary

Question 35

OFF Point

Answer 35

OFF the boundary Should be on the side of the boundary that will receive different processing than the boundary points. Should be x away from boundary

Question 36

Weak Nx1 Test Cases Function

Answer 36

Total Points = (n + 1) x b + 1 n = boundary points b = boundaries

Question 37

Strong Nx1

Answer 37

1 set of tests for each segment

Question 38

Test management Function

Answer 38

T = H / (t + f * r) T = # of tests H = Total Hours for testing t = Time each test takes f = % of faulty tests r = Time to remove a fault

Question 39

Black Box Testing

Answer 39

Functional Testing Tests external functions

Question 40

White box Testing

Answer 40

Structural Testing Tests interanl implementation.

Question 41

Function (in Math)

Answer 41

A relationship from a domain X to a codomain Y such that for every element x in X. Every input has only one output.

Question 42

Checklist

Answer 42

A list of item that need to be covered in a test. Ensure that all the important areas of the applications are covered. Could include structural or functional aspects.

Question 43

A partition is a "mutally exclusive and exhaustive" set of inputs? What does this mean?

Answer 43

Mutally exclusive: No two partition have any elements in common. Exhaustive: The union of all partitions is the entire input space.

Question 44

Why is creativity important in SE?

Answer 44

Its more critical in modern software industry. - Competition in the industry. - Multiple system in the same application domain.

Question 45

Requirements Engineering

Answer 45

Discovering stakeholder's needs and desires. Communicating these to system implementers.

Question 46

RBT Approach Steps

Answer 46

1. Validate requirement 2. Define test completion criteria 3. Design test cases (define logical test cases) 4. Execute Tests 5. Verify test results. 6. Verify test coverage. 7. Manage and track defects/improvements. 8. Manage the test library.