Computer Science & Software Engineering
Testing isn’t algorithms, problem solving, solution building or process management but a knowledge of both is important for testing
Expectations & Oracles
Expectations are mental models of how software works or delivers value; built from references which can be used as oracles to evaluate and identify problems
Cost/Value vs Building/Researching
Agile quadrants of high customer value vs low business cost and building software vs studying software
Left vs Right
Continuous, parallel testing in throughout the software DevOps lifecycle
Idea & Artefact
Software starts with an idea which is communicated and refined through artefacts tested with heuristics and imaginations
Capability
Ability to complete tasks in reasonable and expected ways, possibly in multiple different ways (flexibility).
Performance
Ability to complete tasks in reasonable time and with reasonable responsiveness
Usability
Ability to complete those tasks reasonably easily, simply and intuitively.
Accessibility
Ability to complete those tasks reasonably well as accessibility-needs users
Security
Ability to reasonably guard against completing or altering tasks as unauthorised users or prevent authorised users from doing so
Reliability
Ability to complete tasks reasonable accurately and when needed
References
Ideas or artefacts that form the basis of expectations and utilised as comparison oracles
Auth
Authentication vs Authorisation: Confirming users are who they say they are and assigning what users can do and access
MAC/DAC/RBAC
For authentication and authorisation, logical access control can be mandatory, discretionary or role-based
MFA
Authentication via multiple method types of knowledge, possession (token) and inherence (biometric) where needed
Process
Process are repeatable tasks to achieve something modellable as flow diagrams
Motivation
Measurement management via theory X external vs delegation management via theory Y internal, plus values and relationships
Assurance vs Control
Proactive vs reactive approaches to putting good things in and taking bad things out of testing processes to assure and control testing quality
Mentor
Process where seniors help/assist/teach/advise/guide juniors/interns/apprentices to onboard, upskill, achieve goal, get promoted informally/ad-hoc or part of a programme
1:1
(One-to-one) Regular, private, non-status update, tester-driven agenda meetings to build human connections, trust and rapport with manager