This unit applies to IT personnel who take responsibility for managing testing games and interactive media.
The management of the testing of a product directly impacts on the quality and time lines of delivery to market of a product. Good test management can deliver a quality product. Badly designed products take longer to test but can still be of quality, when partnered with good test management. Well-designed software and good test management go hand in hand to produce quality, timely software products.
Not applicable.
1. Determine quality requirements statement which will enable product release | 1.1 Review picture of product in market place to determine high-level requirements provided by 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 client and development, agreement on product release enabling quality requirements statement |
2. Define test plan to enable testing of required quality as defined by agreed quality requirements statement | 2.1 Determine expected test cycles, during the software development life cycle, considering what development methodology is in use and what the quality requirements are for product release 2.2 Determine what types of testing will be performed during the test cycles to enable efficiency of processes and confirmation of quality requirements statement 2.3 Determine what testing methods will be used to implement testing types defined for defined test cycles 2.4 Determine testing technique to be used to determine test cases and analyse results 2.5 Perform test cycle until a combination is found that provides an acceptable balance of cost, quality and risk, for upper management and development to agree to 2.6 Selection test-support software to enable efficiency in testing and testing management 2.7 Define implementation details for agreed testing and team responsible for testing management 2.8 Define reporting details for testing throughout product life cycle to enable ongoing management of testing process 2.9 Confirm test plan completeness using available completeness techniques 2.10 Confirm test plan with development and management |
3. Install and configure test plan defined test support software | 3.1 Install and configure 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 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 status of product testing related to product release enabling quality requirements statement 4.5 Update test plan and schedule to deal with changing development conditions, and ensure management are informed 4.6 Manage bugs to ensure efficient bug handling and resolution 4.7 Manage 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 product, release enabling, and quality requirements have been met |
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 non-functional
procedures for bug or issue management and identification
test reporting requirements
testing techniques, methods, test types, system dissection.
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 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. |
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. |
Game development
This unit contains employability skills.
No licensing, legislative, regulatory or certification requirements apply to this unit at the time of endorsement but users should confirm requirements with the relevant federal, state or territory authority.