NTISthis.com

Evidence Guide: ICASAS513A - Develop detailed test plans

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICASAS513A - Develop detailed test plans

What evidence can you provide to prove your understanding of each of the following citeria?

Prepare test environment and gather tools

  1. Determine structure of system and user accounts to understand the test environment
  2. Determine areas to test and test objectives, according to organisational standards
  3. Ensure accessibility of documentation
  4. Notify user representatives or approval authorities of objectives and scheduled test
  5. Notify operations staff of scheduled test to ensure preparedness and an understanding of implications
Determine structure of system and user accounts to understand the test environment

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Determine areas to test and test objectives, according to organisational standards

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Ensure accessibility of documentation

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Notify user representatives or approval authorities of objectives and scheduled test

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Notify operations staff of scheduled test to ensure preparedness and an understanding of implications

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Prepare test data

  1. Gather test schedules, according to organisational standards
  2. Correlate schedules with related functionality, according to organisational standards
  3. Check testing schedule prior to validation, according to organisational standards
  4. Prepare test drivers or stubs for test harness, according to organisational standards
  5. Register test plan, and initiate log entries, according to organisational standards
Gather test schedules, according to organisational standards

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Correlate schedules with related functionality, according to organisational standards

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Check testing schedule prior to validation, according to organisational standards

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Prepare test drivers or stubs for test harness, according to organisational standards

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Register test plan, and initiate log entries, according to organisational standards

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Complete test plan and acceptance processes

  1. Use software metrics where appropriate
  2. Validate test and acceptance processes
  3. Ensure documentation and reporting comply with test plan and quality benchmarks
Use software metrics where appropriate

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Validate test and acceptance processes

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Ensure documentation and reporting comply with test plan and quality benchmarks

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

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:

interpret software specifications

consistently and accurately develop a comprehensive test plan that documents:

test conditions or cases to be applied

data to be processed

automated testing coverage

expected results

activities, dependencies and effort required to conduct the system test.

Context of and specific resources for assessment

Assessment must ensure access to:

appropriate learning and assessment support when required

modified equipment for people with special needs

system engineering management plan

test and evaluation program plan

system or application suitable for testing plus its associated documentation

organisational plans and documentation.

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 preparing test data

verbal or written questioning to assess candidate’s knowledge of:

items to be tested

features to be tested

tasks involved in testing

personnel involved

any risks requiring contingency planning

evaluation of candidate’s test plan describing the scope, approach, resources, and schedule of intended testing activities.

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.

Required Skills and Knowledge

Required skills

communication skills to:

conduct presentations

liaise with system users and other internal staff

participate in teams

literacy skills to:

analyse and evaluate information

interpret business and organisational requirements

prepare documentation and reports

planning and organisational skills to develop strategic initiatives

technical skills to:

participate in critical areas, including access control and pathing

identify, analyse and evaluate broad features of system testing and best practice in system testing.

Required knowledge

at least three different operating systems, with detailed knowledge of operating systems relevant to project requirements

automated test tools, with detailed knowledge of features and processes in some areas

organisational requirements

system or application being tested

testing techniques.

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.

Testing schedule may relate to:

complexity

dependency

importance

security

testability

X-factor, where X is an unknown and may or may not impact on the test schedule.

Quality benchmarks may include:

AS3925.1-1994 Software quality assurance - plans

AS4042-1992 Software configuration management plans

AS4043-1992 Software configuration management

AS/NZS 14102:1998 Information technology - guideline for evaluation and selection of computer-aided software engineering (CASE) tools

AS/NZS 4258:1994 Software user documentation process

AS/NZS ISO/IEC 12207:1997 Information technology - Software life cycle processes.