Complete list of all articles organised by category.
ScienceFundamental definitions and assessments of software testing and quality as science and scientific research
|
ApproachesHigh-level approaches to software quality management and testing that apply to every project
|
DimensionsDifferent ways in which value of a software product or project can be delivered or threatened
Capability (Functionality) Ability to complete tasks or user functions in reasonable and expected ways Performance Ability to complete tasks or user functions in reasonable time and responsiveness Usability Ability to complete tasks or user functions reasonably easily, simply and intuitively Accessibility Ability to complete tasks or user functions reasonably well as accessibility-needs users Concurrency Ability to complete tasks or user functions reasonably simultaneously with similar tasks and with other tasks Efficiency Ability to complete tasks or user functions with reasonable system resources and running cost Reliability Ability to complete tasks or user functions without unreasonable interruption and with reasonable recovery from interruptions Integrity Ability to complete tasks or user functions with reasonable accuracy Security Ability to reasonably guard against unauthorised access to complete or alter tasks or to prevent authorised access to do so Portability Ability to complete tasks or user functions on different devices and environments Localisation Ability to complete tasks or user functions reasonably well in different countries or cultures Scalability Ability of all Quality Criteria to reasonably scale with increased usage, size, complexity, market, time etc Operability Ability to reasonably deploy, install, configure, update and resolve problems in production with reasonable disruption and time scale Testability Ability to reasonably observe and configure the product for testing purposes Maintainability Ability to reasonably maintain the product for future development including bug fixing, expansion and repurposing Aesthetics Ability to otherwise give a good impression of quality and be reasonably marketable |
ConsistenciesDifferent ways in which threats to value can be identified and described
Specification Consistency with explicit claims made in project documentation Reference Consistency with software programs that share similarities in purpose or function Regression Consistency with past versions of the same software program Desire Consistency with implicit desires, wants and needs of stakeholders Purpose Consistency with the intended purpose of software Self Consistency within the software program itself Legal Consistency with governmental or judicial statutes, precedents or regulations Standards Consistency with standards, recommendations or best practices within the company or external authoritative bodies Image Consistency with the image that stakeholders want to project Problem Inconsistency with previously reported and resolved problems |
DesignsDifferent techniques used to design tests by modelling out software to some degree
|
UncategorisedOther posts |