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.
Required skills
communication skills to:
liaise with developers on programming matters
liaise with managers or leaders on report and result matters
seek requirements and information from business and technical experts
literacy skills to:
develop reports and documentation in relation to presentation of information
read and interpret program specifications developed by business and technical experts
problem-solving skills to apply basic debugging techniques in the context of software and application development
research skills to:
locate and interrogate complex and varied sources of information
source information from available sources
technical skills to:
develop a small scale application
execute an application.
Required knowledge
characteristics of programming language
detailed knowledge of input and output requirements
overview knowledge of software development life cycle
processes and techniques related to small-size application development.
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 types may include: | acceptance testing accessibility testing alpha testing beta testing component testing integration testing performance testing security testing system testing usability testing. |
Testing tools may include: | graphical user interface (GUI) test tools: AutoHotkey AutoIt Selenium White load and performance tools: BrowserMob QTest SiteBlaster Xceptance LoadTest static analysis tools: Coverity FindBugs FxCop PMD test coverage tools: JCover NCover test design tools: ADL AllPairs.java DGL Jenny Multi TSL unit test tools: csUnit MbUnit NUnit OCUnit xUnit. |
Terms must include: | defect failure quality verification validation. |
Test-case design techniques may include: | black box design techniques: boundary value analysis decision table test equivalence partitioning error guessing desk checking white box design techniques: basic path testing branch coverage condition coverage loop testing statement coverage. |
Unit test framework may include: | cppUnit jUnit mbUnit nUnit ocUnit pyUnit xUnit. |
Test procedures may include: | fake mock stub test class test fixture test method. |
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