Job description
Software Quality Assurance Analysts and Testers
Job purpose
To design and execute software tests, document defects and their causes, and set the standards by which product quality and release readiness are judged, so that faults in software and system modifications are found and resolved before implementation.
Skills
- Knowledge of computers and electronics — hardware, operating systems, network environments and applications — applied through test design, quality control analysis and systems evaluation, with enough programming to build automated test scripts and debug, and enough engineering grounding to judge a build against its requirements. A bachelor's degree is the most common qualification, with a substantial minority holding a two-year degree, plus several years of related experience and on-the-job training.
- Reports defects to the developers responsible for them and gives feedback on software usability and functionality; participates in design reviews on requirements, designs and schedules; collaborates with field staff and customers to diagnose problems referred by technical support; and coordinates user and third-party testing. Findings are frequently unwelcome, and disagreement over the severity of a defect must be handled without damaging the working relationship.
- Identifies, analyses and documents problems with function, output, on-screen display or content, then works back to the cause: reviewing configuration files, logs or fragments of code to locate the source of a breakdown, and running compatibility tests across applications, hardware, operating systems and network environments. The fault is known to exist but its cause is not, so diagnosis is systematic rather than precedented, and anything missed here reaches the customer.
- Plans test schedules and strategies against project scope and delivery dates, designs test plans, scenarios, scripts and procedures, and builds routines covering regression, negative, usability and database-impact testing. Keeps automated scripts current and monitors bug resolution to closure. The release timetable is set elsewhere; the testing within it is the postholder's to shape.
- Work is carried out seated at a workstation, with continuous keyboard and screen use and repeated hand motions in executing tests. No lifting or manual handling demands.
Responsibilities
- No line management. Coordinates others engaged in user or third-party testing, directs developers to the defects they must resolve, and coaches colleagues in testing practice. Judgements on release readiness shape what the organisation can deliver.
- Holds no budget. Evaluates and recommends software for testing and defect tracking, and may recommend purchase of equipment to control conditions where a system is installed. The decision to spend rests above the role.
- Installs, maintains and uses software testing tooling and configures recreations of production environments for realistic performance testing. Monitors software in operation to confirm it runs without fault. Ordinary care of a workstation otherwise.
- Owns the defect record: documents defects in a bug tracking system, maintains databases of known defects, and documents test procedures so results are replicable and standards-compliant. Reviews software documentation for accuracy and completeness, and specifies the standards determining product quality and release readiness. An unrecorded or wrongly described defect passes into production, so exactness governs the work.
Effort required
- Long stretches of exacting, repetitive execution in which small divergences must be noticed, combined with the diagnostic reasoning needed to trace a symptom to its cause. Decisions are frequent and taken under time pressure as delivery dates approach, with attention switching between test design, execution and reporting.
- The work consists largely of finding fault in colleagues' output, and conflict arises over a defect's severity or whether a release should proceed; holding a position on quality against schedule pressure calls for composure. Accountability for a defect reaching production falls here.
- Predominantly seated, with continuous keyboard and screen work and repeated hand motions. No lifting or exertion.
Working conditions
- Indoor, environmentally controlled office accommodation with no exposure to hazardous conditions, contaminants, noise or weather, and occasional visits to beta testing sites. Work is close-quarters, in physical proximity to colleagues and in near-constant contact by e-mail, telephone and face-to-face discussion. The only psychosocial exposure recorded is the conflict inherent in reporting defects.
- Almost all incumbents work a regular established schedule, but around two-fifths regularly work beyond forty hours and a small minority work irregular or seasonal patterns. Time pressure is pronounced as releases approach. Freedom to make decisions is substantial and priorities largely self-determined within the agreed test plan, though those decisions carry consequences for co-workers and company results.