Software Quality Management and Testing

2020

Testing is applied research into software quality using scientific approaches and evidence to help stakeholders make informed decisions

Defined as value to some person(s), which can include expectations met and positive feelings

Focus on people’s feelings as the indicator to quality but be careful to avoid being fooled by illusions

Quality is subjective, relative truth with an objective, relative analysis and is formed from relationships between people and software

Testing is journaling, note-taking and immersion resulting in a written evaluation of quality carefully supported by metrics where appropriate

Testing is scepticism, falsification and invalidation not confirmation, verification or demonstration

Testing is constantly building and falsifying hypotheses of quality using logical reasoning to uncover information

Testing scientific model and process of research question, background investigation, analysis, hypothesis, experiment, evaluation, action (reporting)

Quality is evaluated and communicated as stories of context known as events that contain the who, what, where, when, why and how of value to someone

Risk/threat modelling 1: Problems occur when value isn’t deliver or when additional harm occurs

Coverage mindmaps, requirements/risk, charters/questions, designs, environmental/personnel, journaling/noting results

Ability to complete tasks in reasonable and expected ways, possibly in multiple different ways (flexibility).

Ability to complete tasks in reasonable time and with reasonable responsiveness