Unit of competency details

Release 

Comments 

Release 1

This Unit first released with ICA11 Information and Communications Technology Training Package version 1.0

Element 

Performance Criteria 

Elements describe the essential outcomes of a unit of competency.

Performance criteria describe the performance needed to demonstrate achievement of the element. Where bold italicised text is used, further information is detailed in the required skills and knowledge section and the range statement. Assessment of performance is to be consistent with the evidence guide.

1. Plan and design test

1.1 Analyse and review software development specifications 

1.2 Determine test context, scope, standard  and methodology 

1.3 Determine test types  and tools 

1.4 Determine test input data requirements

1.5 Design test plan and test cases using various test design techniques 

2. Prepare test environment

2.1 Analyse and review documents  to prepare test environment

2.2 Determine test environment requirements 

2.3 Build and set up test environment 

3. Implement and execute test

3.1 Build input data for testing

3.2 Create test suite or script from test cases

3.3 Execute test cases

3.4 Create test record to store test result

4. Manage defect and testing process

4.1 Evaluate and report test results

4.2 Track defect and verify fixes

4.3 Maintain and archive testware  

Overview of assessment 

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

Evidence of the ability to:

• develop test-plan document and test cases to verify the completeness, reliability and performance of an application according to requirement specifications
• analyse and prepare test environment, and execute test cases by using automated test tools
• document and manage test result by performing application debugging process and re-testing application.

Context of and specific resources for assessment 

Assessment must ensure access to:

• test environment that closely resembles production environment
• business, functional, system and user requirements
• system or application suitable for testing
• 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:

• review of test-plan document that follows a certain standard, such as AS/NZS15026:1999
• evaluation of candidate’s ability to:

• select and use features of automated testing tool to perform certain type of test (e.g. stress testing)
• analyse and document test results
• debug application.

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 non-English speaking background may need additional support.

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

Software development specifications  may include:

• budget requirements
• customer requirements
• functional design
• internal design specifications
• schedule requirements
• user stories.

Standard  may include:

• ASNZS15026:1999
• IEEE 829.

Methodology  may include:

• agile
• extreme
• rapid application development (RAD)
• spiral
• traditional plan driven development (TPDD)
• waterfall.

Test types  may include:

• accessibility testing
• load testing
• performance testing
• smoke testing
• stress testing
• usability testing
• volume testing.

Tools  may include:

• automated test
• configuration management
• defect management
• dynamic analysis
• modelling
• monitoring
• requirement management
• review
• static analysis
• test-data preparation
• test-design
• test-execution
• test-management.

Test design techniques  may include:

• black-box
• experience-based
• specification-based
• structure-based
• white-box.

Documents  may include:

• configuration guides
• installation guides
• reference documents
• user manuals.

Test environment requirements  may include:

• communications
• configuration
• hardware
• software
• versions.

Set up test environment  may include:

• obtain and install software releases
• set up logging and archiving processes
• set up or obtain test input data
• set up test tracking processes.

Testware  may include:

• automation tools
• defect repositories
• script
• test cases
• test plan
• test report
• test result
• testing framework.