4. Verification Test Process (Static Testing) – Test Yourself

Please find the answers at the end of the test.

Q1. What best describes Static Testing?

  1. It involves checking that the Test Plan, produced by the Test Manager is correct
  2. It involves reviewing work-products (all the documents or code that have been produced in the Development Life Cycle)
  3. It involves executing the code and checking the results
  4. It involves a Developer producing tests to test his code components

Q2. Which of the following are benefits of Static Testing?

  1. Gaps in all documents can be identified
  2. Test Plans are easier to produce
  3. It improves Performance Testing 
  4. It allows a form of early testing (of documents / code reviews)
  5. Great savings can be made by identifying mistakes early in a Project 
  6. Improves communication with an SDLC Team

Q3. Where is Static Testing done?

  1. It is when we review any documents or review code itself
  2. It is when we run code and check the results
  3. It is when we write Design documents
  4. It is when we dynamically test the System

Q4. Who performs Static Testing?

  1. It is done by Business Analysts, Architects (Designers) and the Test Manager
  2. It is done by the Test Team
  3. All members of an SDLC Team can perform it, usually so long as they have the relevant skills to do so
  4. It is done by the Test Manager

Q5. What are the 2 types of Static Testing processes?

  1. Reviews
  2. System Testing
  3. Walkthroughs
  4. Capturing Requirements

Q6. Which of the following are we looking for when reviewing documents (by performing Static Testing)?

  1. Defects
  2. Bugs 
  3. Gaps in the document or code
  4. New ideas to improve things
  5. Expected results following execution of the System

Q7. When are Walkthroughs performed?

  1. Before a document has been produced
  2. After a document has been produced and issued for members of the SDLC Team to look at / review
  3. Only after a Requirements Specification has been issued
  4. Once a System Test has been executed

Q8. What is the difference between Static Testing and Dynamic Testing?

  1. Static Testing can be both reviewing documentation and checking the results after executing code, whereas Dynamic Testing is done after execution of the code
  2. Static Testing reviews the documentation or code of a Project, looking to improve them, whereas Dynamic Testing checks the results after executing the System / Code
  3. Dynamic Testing is done by all the SDLC Team, whereas Static Testing is only done by the Test Team
  4. Static Testing is performed prior to the code being produced, Dynamic Testing is done after it has been produced

ANSWERS:

Q1. What best describes Static Testing?

  1. It involves checking that the Test Plan, produced by the Test Manager is correct
  2. It involves reviewing work-products (all the documents or code that have been produced in the Development Life Cycle)
  3. It involves executing the code and checking the results
  4. It involves a Developer producing tests to test his code components

Answer:

2

Q2. Which of the following are benefits of Static Testing?

  1. Gaps in all documents can be identified
  2. Test Plans are easier to produce
  3. It improves Performance Testing 
  4. It allows a form of early testing (of documents / code reviews)
  5. Great savings can be made by identifying mistakes early in a Project 
  6. Improves communication with an SDLC Team

Answer:

1, 4, 5, 6

Q3. Where is Static Testing done?

  1. It is when we review any documents or review code itself
  2. It is when we run code and check the results
  3. It is when we write Design documents
  4. It is when we dynamically test the System

Answer:

1

Q4. Who performs Static Testing?

  1. It is done by Business Analysts, Architects (Designers) and the Test Manager
  2. It is done by the Test Team
  3. All members of an SDLC Team can perform it, usually so long as they have the relevant skills to do so
  4. It is done by the Test Manager

Answer:

3

Q5. What are the 2 types of Static Testing processes?

  1. Reviews
  2. System Testing
  3. Walkthroughs
  4. Capturing Requirements

Answer:

1, 3

Q6. Which of the following are we looking for when reviewing documents (by performing Static Testing)?

  1. Defects
  2. Bugs 
  3. Gaps in the document or code
  4. New ideas to improve things
  5. Expected results following execution of the System

Answer:

1,3,4

Q7. When are Walkthroughs performed?

  1. Before a document has been produced
  2. After a document has been produced and issued for members of the SDLC Team to look at / review
  3. Only after a Requirements Specification has been issued
  4. Once a System Test has been executed

Answer:

2

Q8. What is the difference between Static Testing and Dynamic Testing?

  1. Static Testing can be both reviewing documentation and checking the results after executing code, whereas Dynamic Testing is done after execution of the code
  2. Static Testing reviews the documentation or code of a Project, looking to improve them, whereas Dynamic Testing checks the results after executing the System / Code
  3. Dynamic Testing is done by all the SDLC Team, whereas Static Testing is only done by the Test Team
  4. Static Testing is performed prior to the code being produced, Dynamic Testing is done after it has been produced

Answer:

2

Return To Lesson ⇒ 4. Verification Test Process (Static Testing)