The document provides a glossary of key terms and expressions related to quality assurance in software, outlining definitions for concepts such as acceptance criteria, test cases, and quality assurance itself. It includes descriptions of processes like acceptance testing and certification, alongside tools and techniques used in the testing phase. This glossary serves as a quick reference for professionals in the field to understand essential quality assurance terminology.

1. Quality Assurance
Glossary

2. Like others professions there are a few expressions
you should know to work daily.
Here, we will represent a short list with the most
important terms and expressions

3. Acceptance criteria
The requirements a component must meet in order to be accepted by client.

4. Acceptance testing
Specific test to warranty the acceptance criteria

5. Certification
The process of confirming that a component or system complies with its specified requirements

6. Tested Not tested
Code coverage
An analysis method that determines which parts of the software have been executed by the test suite and which
parts have not been executed

7. Component
A minimal software item that can be tested in isolation
Hi!

8. Cyclomatic complexity
The number of independent paths through a program

9. Monitor
A software tool that run concurrently with the component or system under test and supervises the
behavior of the component or system

10. Non-conformit
Non fulfillment of a specified requirement

11. Quality Assurance
Part of quality management focused on providing confidence that quality requirements will be fulfilled

12. Requirement
A condition or capability needed by a user to solve a problem or achieve an objective that must be met or
possessed by a system or system component to satisfy a contract or especification.

13. Review
An evaluation of a product or project status to evaluate it from planned results and to recommend
improvements

14. State diagram
A diagram that depicts the states that a component or system can assume, and shows the events or
circumstances that cause and/or result from a change from one state to another

15. Test case
A set of input values, execution preconditions, expected results and execution postconditions, developed for a
particular test condition, such as to exercise a particular program path or to verify compliance with a specific
requirement

16. Test plan
A document describing the scope, approach, resources and schedule of intended test activities. It identifies
amongst others test items, the features to be tested, the testing tasks, who will do each task, degree of tester
independence, the test environment, the test design techniques and test measurement techniques to be used,
and the rationale for their choice, and any risks requiring contingency planning. It is a record of the test planning
process.

17. Test suite
A set of several test cases for a component or system under test, where the postcondition of one test is often
used as the precondition for the next one

18. User story
Description in natural language which explain the user needs as part of his job

19. Validation
Confirmation by examination and through provision of objective evidence that the requirements for a specific
intended use or application have been fulfilled

20. Detestable (adjective)
Software that isn't testable.
Also, we gonna close this post with an extra term from Martin Fowler:

21. THANKS!
Any questions?
@jorgebfe
jorgebarroso@datiobd.com
datio-big-data