Terminology
Name that Trait
7 Test Principles
Common Test Responsibilities
Project Team Roles
100
A factor that could result in future negative consequences, usually expressed as a likelihood.
What is a Risk.
100
Good testers want to know why a system behaves as it does.
What is Curiosity.
100
To find defects early, testing activities shall be started as early as possible in the system development lifecycle.
What is Early Testing.
100
We run our tests against the test object (the system under test).
What is Test Execution.
100
Designs and codes the system/software.
What is the software developer.
200
A human action that produces an incorrect result.
What is an Error or Mistake.
200
Good testers expect to find defects and failures.
What is Professional Pessimism.
200
Testing can show that defects are present, but cannot prove that there are no defects.
What is Testing Shows the Presence of defects.
200
We establish the scope, approach, resources, schedule, and specific tasks in the intended test activities that comprise the rest of the test process. We should identify test items, the features to be tested/not tested, the roles and responsibilities of the participants and stakeholders, the test environments required, appropriate test design techniques entrance and exit criteria, and how project risks will be handled.
What is Test Planning.
200
Responsible for creating an end-to-end test plan; executing the plan and managing all activities in the plan to ensure that all the objectives are met and that the solution works as expected.
What is the QA Tester.
300
The degree to which a component, system or process meets specified requirements and user/customer expectations.
What is Quality.
300
Good testers notice everything, even the smallest detail details.
What is Attention to Detail.
300
Finding and fixing defects does not help if the system built is unusable and does not fulfill the users' needs and expectations.
What is the Absence-of-errors fallacy.
300
We identify what to test, choosing the test conditions we need to cover. Example of test conditions: functions, transactions, features, quality attributes, quality risks, or structural elements.
What is Test Analysis.
300
Analyzes an organization and documents its business or processes or systems, assessing the business model or its integration with technology.
What is the Business Analyst.
400
Deviation of the component or system from its expected delivery, service or result.
What is a Failure.
400
Good testers not only know a defect when they see one, they also know where to look for defects.
What is Experience.
400
If the same tests are repeated over and over again, eventually the same set of test cases will no longer find any new defects.
What is the Pesticide Paradox.
400
We report out our progress against the exit criteria. This often involves details related to the status of the project, the test process, and the quality of the system under test.
What is Test Results Reporting.
400
Defines the architecture of a computerized in order to fulfill certain requirements. (Architecture is the conceptual model that defines the structure, behavior, and more views of a system).
What is the System Architect.
500
A flaw in a component or system that can cause the component or system to fail to perform it's required function.
What is a Defect, Bug or Fault.
500
Good testers couple professional pessimism with a natural inclination to doubt the correctness of software work products and their behaviors as they look at them.
What is A Critical Eye.
500
Testing efforts shall be focused proportionally to the expected and later observed defect density of modules. A small number of modules usually contains most f the defects.
What is Defect Clustering.
500
We compare the actual results against expected results to determine the pass/fail status of the test.
What is Checking Results.
500
Responsible for the oversight of the planning, procurement and execution of a project, in any domain of engineering.
What is the Project Manager.
M
e
n
u