Introductory Info

Question 1

What are some examples of requirements forms?

Answer 1

• Formal requirements prepared by business analysts
• Technical requirements documents
• User stories
• Informal diagrams from workshops

Question 2

Verifying requirements is dependent on _______.

Answer 2

The clarity of the requirements.

Question 3

Define fit for purpose.

Answer 3

The software must work for the people who will be using it, in the environment in which they will be using it.

Question 4

Define risk prioritization.

Answer 4

Used to limit testing to what is needed to mitigate risk to an acceptable level.

Question 5

Define defect.

Answer 5

Also called bugs, flaws in the system that cause it to function incorrectly or cause the user to use it incorrectly.

Question 6

What are the differences between a technical tester and non-technical tester?

Answer 6

Technical testers are test engineers and are expected to have skills needed to write test automation, conduct performance testing, or participate in code/design reviews.

Non-technical testers are test analysts and are expected to conduct functional testing and consider usability and domain/environment attributes of the software.

Question 7

Define highly-structured testing.

Answer 7

Has high levels of documentation, to include formatted test strategies, well-defined test plans, explicit data sets, controlled test data and environments, and a well-managed defect life cycle.

Question 8

List common documents found in structured testing.

Answer 8

• Test strategy
• Test plan
• Test conditions
• Test case
• Defect reports

Question 9

Define test strategy.

Answer 9

Organization-wide document that defines how testing will be conducted across all comparable types of projects in the organization.

Question 10

Define test plan.

Answer 10

Implementation of the test strategy for a particular project.

Question 11

Define test conditions.

Answer 11

Capability or characteristic of the software that needs to be tested.

Question 12

Define test case.

Answer 12

Information required for a tester to test a condition. This includes pre-conditions, inputs and actions, and post-conditions.

Question 13

Describe how a defect should be captured and what a defect report should include.

Answer 13

Each defect should be captured in a report that is then processed through a workflow to record all the actions taken to resolve the issue. This includes the environment used, steps to reproduce, the priority or severity, and expected or actual results.

Question 14

Define who can be a software tester.

Answer 14

Anyone can be a soft tester. Developers, business users, and everyone on the Agile team. This varies across different organizations.