1.3) Principles in Software Testing Flashcards

In addition to the principles of software quality assurance, targeted fundamental attributes and phenomena relating to software testing are described.

1
Q

Please list the steps related to the Principles of Software testing.

A
  • Testing shows the presence of errors
  • Complete testing is not possible
  • Accumulation of errors
  • Repition has no effects
  • Testing depends on the environment
  • Fallacy: No errors does not automatically mean the system is usable
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What does software testing demonstrate about errors in a system?

A

Testing demonstrates the presence of errors in a system, but it cannot prove the absence of errors. Extensive testing reduces the probability of undetected errors but does not guarantee error-free software.

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

Why is complete testing of industrial software systems impossible?

A

Complete testing is impossible because of the vast number of possible input values and system states. It would require impractical resources, making exhaustive testing infeasible for economic operation.

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

What is “error clustering,” and why is it important in software testing?

A

Error clustering is the phenomenon where most errors are concentrated in a few system components. If one error is found in a component, more errors are likely nearby, so testing in that area should be more focused.

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

Why does repeating the same test under identical conditions not provide new insights?

A

Repeating the same test with identical input data and system conditions will not reveal new errors or information beyond what was discovered in the initial test.

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

How does the testing environment influence test case design?

A

Test case design depends on the specific system requirements, project constraints, and quality objectives. Testing must be tailored to each project, effectively becoming a “software project within a project.”

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

Why might a thoroughly tested system still be considered unusable by users?

A

A system may meet all specified requirements and pass all tests but still fail in usability due to untested user-relevant aspects, such as poor performance under high load or limited availability in real-world conditions.

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