Testing Flashcards

1
Q

What is a Failure in SE?

A

any deviation/difference of observed behaviour from specified behaviour, informally also called “crash”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is an Error in SE?

A

system is in a state such that further processing can lead to failure (e.g. wrong user input, null
reference errors, concurrency errors, exceptions)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is a Fault in SE?

A

mechanical or algorithmic cause of an error, informally also called “bug

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Which types of faults are there?

A
  • Algorithmic fault: e.g. compass shows wrong values, missing test for null/ initialisation, incorrect branching condition, missing test for null
  • Usage fault: wrong usage of compass
  • Communication fault
  • Mechanical fault: very hard to find, e.g. operating temperature
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is validation in SE?

A

activity checking for deviations between observed and specified behavior

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Name the 4 types of testing.

A
  • Unit Testing
  • System Testing
  • Integration Testing
  • Acceptance Testing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Shortly describe Unit Testing and its goal.

A
  • Individual components (class or subsystem) are tested
  • Carried out by developers
  • Goal: confirm that the component is correct and carries out the intended functionality
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Shortly describe System Testing and its goal.

A
  • The entire system is tested
  • Carried out by developers
  • Goal: determine if the system meets the requirements (functional and nonfunctional)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Shortly describe Integration Testing and its goal.

A
  • test groups of subsystems and eventually the entire system are tested
  • Carried out by developers
  • Goal: test the interfaces of the subsystems
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Shortly describe Acceptance Testing and its goal.

A
  • Evaluates the system delivered by developers
  • Carried out by the client: may involve executing typical transactions on site
  • Goal: demonstrate that the system meets the requirements and is ready to use
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Describe the process of Unit Tests with Easy mock.

A
  1. Create the mock object
  2. specify the expected behaviour with expect(…).andReturn();
  3. Make the mock object ready to play
  4. Execute the SUT
  5. Compare observed with expected behaviour
How well did you know this?
1
Not at all
2
3
4
5
Perfectly