Google Links

Follow the links below to find material targeted to the unit's elements, performance criteria, required skills and knowledge

Elements and Performance Criteria

  1. Determine quality requirements statement which will enable product release
  2. Define test plan to enable testing of required quality as defined by agreed quality requirements statement
  3. Install and configure test plan defined test support software
  4. Manage testing process to enable defined quality requirements
  5. Finalise testing for release

Required Skills

Required skills

analytical skills to define test plan details and identify bugs or issues

communication skills to

determine and define quality requirements statement

manage and coordinate testing processes and finalisation of testing

literacy skills to produce technical documentation and reports

planning skills to define test plan details

technical skills to

manage test environment

develop test plan details

select install and configure test plan support software

Required knowledge

client requirements for platforms hardware and software

client system requirements both functional and nonfunctional

procedures for bug or issue management and identification

test reporting requirements

testing techniques methods test types system dissection

Evidence Required

The evidence guide provides advice on assessment and must be read in conjunction with the performance criteria required skills and knowledge range statement and the Assessment Guidelines for the Training Package

Overview of assessment

Critical aspects for assessment and evidence required to demonstrate competency in this unit

Evidence of the ability to

define quality requirements and an associated test plan for software

install and configure testing support software

manage testing process

identify bugs or issues accurately and concisely

finalise software testing process to enable product release

Context of and specific resources for assessment

Assessment must ensure access to

system undergoing development with associated specifications

client requirements verbal or written for system quality requirements

testing support software

test environment

appropriate learning and assessment support when required

modified equipment for people with special needs

Method of assessment

A range of assessment methods should be used to assess practical skills and knowledge The following examples are appropriate for this unit

direct observation of candidate identifying or finding bugs and issues

review of reports prepared by candidate showing plans and management of testing

Guidance information for assessment

Holistic assessment with other units relevant to the industry sector workplace and job role is recommended where appropriate

Assessment processes and techniques must be culturally appropriate and suitable to the communication skill level language literacy and numeracy capacity of the candidate and the work being performed

Indigenous people and other people from a nonEnglish speaking background may need additional support

In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge


Range Statement

The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.

Types of requirements may include:

functional, such as audio and visual

installation, such as new, upgrades, database and software

non-functional, such as performance, load, stress and cultural

platform or environment.

Outstanding bugs may include:

defined priorities

with or without defined priorities.

Limited release may include:

alpha and beta release options

environment-specific release

internal or in-house release options

external release options

platform-specific release.

Test cycles may include:

delivery of testable product to client

delivery of testable product to test team

in-development tests, such as source-code updates or retrievals from source control, initial implementation complete time, pre-implementation time.

Types of testing may include:

acceptance

data functionality

functionality

graphical user interface (GUI)

load

performance

regression

smoke

stress

unit.

Testing methods may include:

automated, such as coded testing or using automation-tool

manual, such as exploratory or testing of specific test cases

static and dynamic analysis.

Testing technique may include:

boundary value analysis

equivalence

way of designing test cases.

Test-support software may include:

bug tracking software

test automation software, such as:

WinRunner

LoadRunner

test case-management software, such as Test Director.

Implementation details and reporting details may include:

communication and interaction levels between departments for cycles, such as development may or may not be approachable during particular processes or cycles

details of all processes and procedures

required documentation repositories, templates, structures and locations.

Completeness techniques may include:

interdepartmental reviews

intradepartmental reviews

system dissection.