Assessor Resource

ICTGAM511
Manage testing of games and interactive media

Assessment tool

Version 1.0
Issue Date: April 2024


This unit describes the skills and knowledge required to define requirements and manage the testing of games, and interactive media, to enable timely product release.

It applies to individuals who ensure the delivery of well-tested, quality software products in the marketplace.

No licensing, legislative or certification requirements apply to this unit at the time of publication.

You may want to include more information here about the target group and the purpose of the assessments (eg formative, summative, recognition)


Evidence Required

List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Determine the quality requirements statement that will enable product release

1.1 Review the picture of the product in the market place to determine high-level requirements provided by the product, for expected clients, considering all types of requirements

1.2 Define a releasable product in terms of outstanding bugs, to enable a limited release and a complete product release

1.3 Summarise findings into a product release, enabling quality requirements statement

1.4 Confirm that the client requirements and development specifications are in agreement for product release, to enable the preparation of a quality requirements statement

2. Define test plan that enables testing of required quality as defined by quality requirements statement

2.1 Determine expected test cycles during the software development life cycle, considering the development methodology in use and the quality requirements for the product’s release

2.2 Determine the types of testing to be performed during the test cycles, to enable the efficiency of processes, and the confirmation of the quality requirements statement

2.3 Determine the testing methods to be used to implement the testing types defined for the identified test cycles

2.4 Determine the testing technique to be used to determine test cases, and analyse results

2.5 Perform the test cycle until a combination is found that provides an acceptable balance of cost, quality and risk, and on which upper management and development team can agree

2.6 Select test-support software to enable efficiency in testing and testing management

2.7 Define implementation details for agreed testing and the team responsible for testing management

2.8 Define reporting details for testing throughout the product life cycle to enable ongoing management of the testing process

2.9 Confirm test plan completeness using available completeness techniques

2.10 Confirm the test plan with development team and management

3. Install and configure test plan defined test support software

3.1 Install and configure the bug tracking process, and define bug description fields to maximise efficiency, and minimise possibilities of bouncing bugs

3.2 Install and configure test case management software

3.3 Install and configure test cycle management and reporting software

3.4 Install and configure automated test tools

4. Manage testing process to enable defined quality requirements

4.1 Manage and report on the development of test cases

4.2 Manage and report on test cycle status

4.3 Manage and report on outstanding bug status

4.4 Manage and report on the status of product testing related to product release, enabling a quality requirements statement

4.5 Update the test plan and schedule to deal with changing development conditions, and to ensure that management is informed

4.6 Manage bugs to ensure efficient bug handling and resolution

4.7 Manage the test environment, including setup, receipt of test builds and clean-up

5. Finalise testing for release

5.1 Produce testing results for management review prior to release

5.2 Manage test product freeze for final release and final test run

5.3 Confirm the product, release enabling, and ensure that quality requirements have been met

Evidence of the ability to:

define quality requirements and an associated test plan for software

install and configure testing support software

manage the testing process

identify bugs or issues, accurately and concisely

finalise the software testing process to enable the product release.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

provide a detailed summary of client requirements for platforms, hardware and software

provide a detailed explanation of client system requirements, both functional and non-functional

outline the procedures for bug or issue management and identification

summarise test reporting requirements

explain testing techniques, methods, test types and system dissection.

Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the game development field of work, and include access to:

a system undergoing development with the associated specifications

client requirements (verbal or written) for system quality requirements

testing support software

a test environment.

Assessors must satisfy NVR/AQTF assessor requirements.

Submission Requirements

List each assessment task's title, type (eg project, observation/demonstration, essay, assingnment, checklist) and due date here

Assessment task 1: [title]      Due date:

(add new lines for each of the assessment tasks)

Assessment Tasks

Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Determine the quality requirements statement that will enable product release

1.1 Review the picture of the product in the market place to determine high-level requirements provided by the product, for expected clients, considering all types of requirements

1.2 Define a releasable product in terms of outstanding bugs, to enable a limited release and a complete product release

1.3 Summarise findings into a product release, enabling quality requirements statement

1.4 Confirm that the client requirements and development specifications are in agreement for product release, to enable the preparation of a quality requirements statement

2. Define test plan that enables testing of required quality as defined by quality requirements statement

2.1 Determine expected test cycles during the software development life cycle, considering the development methodology in use and the quality requirements for the product’s release

2.2 Determine the types of testing to be performed during the test cycles, to enable the efficiency of processes, and the confirmation of the quality requirements statement

2.3 Determine the testing methods to be used to implement the testing types defined for the identified test cycles

2.4 Determine the testing technique to be used to determine test cases, and analyse results

2.5 Perform the test cycle until a combination is found that provides an acceptable balance of cost, quality and risk, and on which upper management and development team can agree

2.6 Select test-support software to enable efficiency in testing and testing management

2.7 Define implementation details for agreed testing and the team responsible for testing management

2.8 Define reporting details for testing throughout the product life cycle to enable ongoing management of the testing process

2.9 Confirm test plan completeness using available completeness techniques

2.10 Confirm the test plan with development team and management

3. Install and configure test plan defined test support software

3.1 Install and configure the bug tracking process, and define bug description fields to maximise efficiency, and minimise possibilities of bouncing bugs

3.2 Install and configure test case management software

3.3 Install and configure test cycle management and reporting software

3.4 Install and configure automated test tools

4. Manage testing process to enable defined quality requirements

4.1 Manage and report on the development of test cases

4.2 Manage and report on test cycle status

4.3 Manage and report on outstanding bug status

4.4 Manage and report on the status of product testing related to product release, enabling a quality requirements statement

4.5 Update the test plan and schedule to deal with changing development conditions, and to ensure that management is informed

4.6 Manage bugs to ensure efficient bug handling and resolution

4.7 Manage the test environment, including setup, receipt of test builds and clean-up

5. Finalise testing for release

5.1 Produce testing results for management review prior to release

5.2 Manage test product freeze for final release and final test run

5.3 Confirm the product, release enabling, and ensure that quality requirements have been met

Evidence of the ability to:

define quality requirements and an associated test plan for software

install and configure testing support software

manage the testing process

identify bugs or issues, accurately and concisely

finalise the software testing process to enable the product release.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

provide a detailed summary of client requirements for platforms, hardware and software

provide a detailed explanation of client system requirements, both functional and non-functional

outline the procedures for bug or issue management and identification

summarise test reporting requirements

explain testing techniques, methods, test types and system dissection.

Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the game development field of work, and include access to:

a system undergoing development with the associated specifications

client requirements (verbal or written) for system quality requirements

testing support software

a test environment.

Assessors must satisfy NVR/AQTF assessor requirements.
Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.

Observation Checklist

Tasks to be observed according to workplace/college/TAFE policy and procedures, relevant legislation and Codes of Practice Yes No Comments/feedback
Review the picture of the product in the market place to determine high-level requirements provided by the product, for expected clients, considering all types of requirements 
Define a releasable product in terms of outstanding bugs, to enable a limited release and a complete product release 
Summarise findings into a product release, enabling quality requirements statement 
Confirm that the client requirements and development specifications are in agreement for product release, to enable the preparation of a quality requirements statement 
Determine expected test cycles during the software development life cycle, considering the development methodology in use and the quality requirements for the product’s release 
Determine the types of testing to be performed during the test cycles, to enable the efficiency of processes, and the confirmation of the quality requirements statement 
Determine the testing methods to be used to implement the testing types defined for the identified test cycles 
Determine the testing technique to be used to determine test cases, and analyse results 
Perform the test cycle until a combination is found that provides an acceptable balance of cost, quality and risk, and on which upper management and development team can agree 
Select test-support software to enable efficiency in testing and testing management 
Define implementation details for agreed testing and the team responsible for testing management 
Define reporting details for testing throughout the product life cycle to enable ongoing management of the testing process 
Confirm test plan completeness using available completeness techniques 
Confirm the test plan with development team and management 
Install and configure the bug tracking process, and define bug description fields to maximise efficiency, and minimise possibilities of bouncing bugs 
Install and configure test case management software 
Install and configure test cycle management and reporting software 
Install and configure automated test tools 
Manage and report on the development of test cases 
Manage and report on test cycle status 
Manage and report on outstanding bug status 
Manage and report on the status of product testing related to product release, enabling a quality requirements statement 
Update the test plan and schedule to deal with changing development conditions, and to ensure that management is informed 
Manage bugs to ensure efficient bug handling and resolution 
Manage the test environment, including setup, receipt of test builds and clean-up 
Produce testing results for management review prior to release 
Manage test product freeze for final release and final test run 
Confirm the product, release enabling, and ensure that quality requirements have been met 

Forms

Assessment Cover Sheet

ICTGAM511 - Manage testing of games and interactive media
Assessment task 1: [title]

Student name:

Student ID:

I declare that the assessment tasks submitted for this unit are my own work.

Student signature:

Result: Competent Not yet competent

Feedback to student

 

 

 

 

 

 

 

 

Assessor name:

Signature:

Date:

Assessment Record Sheet

ICTGAM511 - Manage testing of games and interactive media

Student name:

Student ID:

Assessment task 1: [title] Result: Competent Not yet competent

(add lines for each task)

Feedback to student:

 

 

 

 

 

 

 

 

Overall assessment result: Competent Not yet competent

Assessor name:

Signature:

Date:

Student signature:

Date: