Testing-Essentials ▪ Think Like a Tester ▪ Test Strategy ▪ Test Tooling, Automation ▪ Test Analysis and -Design ▪ Performing Tests and Reporting ▪ Appendix
Keywords
This content is a work in (slow) progress, still very much incomplete.
B
- black-box testing
-
Tests that do not use technical details of the system. This does *not mean* that the person designing the test ignores their knowledge of the internal workings of the system.
- business analyst
-
Business analysts work in change initiatives to identify and define solutions for business problems. Their responsibilities include requirements engineering - gathering requirements, documenting and modelling them, and managing these artefacts.
D
- dynamic testing
-
Software testing that involves running the system under test.
K
- knowledge work
-
The terms knowledge work and knowledge workers were coined by Peter Drucker in the mid-20th century. Knowledge work is marked by non-routine problem solving, and knowledge workers require a combination of skills such as the ability to learn, to think creatively and critically, and to generate ideas.
O
- oracle
-
The means by which we determine whether or not a test has passed, such as comparison with specifications. Oracles are heuristic devices, thus not infallible.
S
- stakeholder
-
People who have a vested interested in or are impacted by something such as an enterprise or project, product or service. Examples of stakeholders: customers, employees and suppliers.
- static testing
-
Testing that involves checking, analyzing or reviewing work items such as code, system design models or documentation.
U
- user experience design
-
UX designers work on optimizing the interfaces between products or services and users. The UX design process involves user research and the application of design conventions.
W
- white-box testing
-
Tests that use technical details of the system. Also known as glass-box testing.