Software Testing

Question 1

Program testing

Answer 1

• Show that program does what is intended
• Execute program using artificial data
• Demonstrate that software meets requirements
• Discover defects

Question 2

Verification and validation

Answer 2

• System is fit for purpose

Question 3

Validation:

Answer 3

• Are we building the right product?

Question 4

Verification:

Answer 4

• Are we building the product right?

Question 5

Inspections provide:

Answer 5

• Analysis of the system to discover faults.
• Static verification.
• Code and document reviews.
• Manual process.
• A very effective ability to find hidden errors.

Question 6

Testing

Answer 6

• Exercising and observing product behaviour
• Dynamic verification

Question 7

Stages of testing

Answer 7

• Development testing, during which the system is tested to discover bugs and defects
• Release testing, during which the system is tested to check that it meets its requirements
• User testing, during which the system is tested in the user’s environment

Question 8

Development testing

Answer 8

• The system is tested to discover bugs and defects

Question 9

Release testing

Answer 9

• The system is tested to check that it meets its requirements

Question 10

User testing

Answer 10

• The system is tested in the user’s environment.

Question 11

Component testing

Answer 11

• Several individual units are integrated to create composite components. Component testing should focus on testing component interfaces.

Question 12

System testing

Answer 12

• Some or all of the components in a system are integrated and the system is tested as a whole. System testing should focus on testing component interactions.

Question 13

Unit testing

Answer 13

• Individual program units or object classes are tested. Unit testing should focus on testing the functionality of objects or methods.

Question 14

Testing strategies

Answer 14

• Partition testing
• Guideline-based testing

Question 15

Partition Testing

Answer 15

• Groups of inputs with common characteristics

Question 16

Guideline-based testing

Answer 16

• Based on experience in knowing types of errors and where they occur

Question 17

Equivalence partition

Answer 17

• A class of inputs or outputs of which it is reasonable to expect that the system will behave the same way for all members of the class—for example, all strings with less than 256 characters

Question 18

Test-driven development process

Answer 18

• Identify the increment of functionality required.
• Design tests for this functionality and implement them as executable programs.
• Run a test along with other implemented tests. The test will fail.
• Implement the functionality and re-run the test. Iterate until the test works.
• Move on to implement the next chunk of functionality.

Question 19

Alpha testing

Answer 19

• Users work with the development team to test the software as it is being developed.

Question 20

Beta testing

Answer 20

• The software is released to selected users for testing before the formal system release.

Question 21

Acceptance testing

Answer 21

• Customers test a system to check that it is ready for deployment.

Question 22

Release testing

Answer 22

• The software is tested by a team different than the development team.
• The purpose is to show that the system meets its requirements.

Question 23

Requirements-based testing

Answer 23

• Verify functionality of a system by executing test that correspond to system requirements.