NTISthis.com

Evidence Guide: ICTSAS513 - 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

 

ICTSAS513 - 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

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

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

1. Prepare test environment and gather tools

1.1 Determine structure of system and user accounts to understand the test environment

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

1.3 Ensure accessibility of documentation

1.4 Notify user representatives or approval authorities of objectives and scheduled test

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

2. Prepare test data

2.1 Gather test schedules according to organisational standards

2.2 Correlate schedules with related functionality according to organisational standards

2.3 Check testing schedule prior to validation according to organisational standards

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

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

3. Complete test plan and acceptance processes

3.1 Use software metrics where appropriate

3.2 Validate test and acceptance processes

3.3 Ensure documentation and reporting comply with test plan and quality benchmarks

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

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

1. Prepare test environment and gather tools

1.1 Determine structure of system and user accounts to understand the test environment

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

1.3 Ensure accessibility of documentation

1.4 Notify user representatives or approval authorities of objectives and scheduled test

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

2. Prepare test data

2.1 Gather test schedules according to organisational standards

2.2 Correlate schedules with related functionality according to organisational standards

2.3 Check testing schedule prior to validation according to organisational standards

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

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

3. Complete test plan and acceptance processes

3.1 Use software metrics where appropriate

3.2 Validate test and acceptance processes

3.3 Ensure documentation and reporting comply with test plan and quality benchmarks

Evidence of the ability to:

interpret software specifications

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.

Note: Evidence must be provided for at least TWO systems.

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

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

compare and contrast key features of automated test tools, with detailed knowledge of features and processes of tools relevant to the project

discuss organisational requirements, including a testing schedule

analyse system or application being tested

describe quality benchmarks appropriate for testing

describe testing techniques and process relevant to the project.