| 1 | 1a. Test engineering software | 1.1 | Work safely at all times, complying with health and safety legislation, regulations and other relevant guidelines |
| 1.2 | Plan the software testing activities before they start them |
| 1.3 | Prepare for the software testing activities, by carrying out all of the following: • check that the working environment is in a safe and appropriate condition and that all working equipment is in a safe and usable condition (such as cables undamaged, correctly connected, safely routed) • start the appropriate software test tool • set up the testing environment and select a suitable template/folder • identify relevant software requirements/design to be tested against • identify the required standards and all relevant sources (such as software requirements, design and software test methods) |
| 1.4 | Use appropriate sources to obtain the required information for the software testing activity |
| 1.5 | Use three of the following to obtain the necessary data to produce the required test script/case: • change order/modification request • technical publications • calculations • software requirements • technical notes (such as meetings/discussions, e-mail) • standards reference documents • specifications • regulations • software design • other available data |
| 1.6 | Demonstrate how the software testing takes account of six of the following: • function • quality • testing method • resources (such as memory, performance and bandwidth) • cost • lifetime of the product • accuracy • design structure • run time sequencing • operating environment • interfaces • safety • software requirements • system/software safety requirements |
| 1.7 | Carry out all of the following before producing the software test script/case: • ensure that the data and information they have is complete and accurate • analyse the data and information to identify the test script/case requirements • recognise and deal with problems (such as technical issues and lack of, or incorrect information) |
| 1.8 | Use one of the following modelling methodologies to produce the software test script/case: • black box • white box |
| 1.9 | Create/modify the software test script/case using four of the following: • objects • functions • change requests • classes • procedures • test rigs specifications • types • data |
| 1.10 | Access and use the correct software test tools |
| 2 | 1b. Test engineering software (continued) | 2.1 | Use appropriate techniques to create the software tests |
| 2.2 | Use references that follow the required conventions |
| 2.3 | Run the test script using one of the following: • target simulator environment • host environment • target environment |
| 2.4 | Produce the finished test script/case, with sufficient detail to allow execution |
| 2.5 | Make sure that the test script/case is checked and approved by the appropriate person |
| 2.6 | Check the test script/case for all of the following: • completeness • sequencing • traceability • coverage • accuracy |
| 2.7 | Save and store the test script/case and results in appropriate locations, to include carrying out all of the following: • check that the test script/case and results are correctly titled, referenced and annotated • ensure that their test script/case and results have been checked and comply with company procedures • save the test script/case and results to an appropriate location (such as storage device, configuration database) • register and store the test script/case and results in the company information system (where appropriate) • record and store any changes to the test script/case and results in the appropriate company information system • ensure that a separate backup copy is created and placed in safe storage |
| 2.8 | Execute a test script/case and record the results |
| 2.9 | Review the results of the test script/case |
| 2.10 | Produce a test script/case which complies with one of the following: • company standards and procedures • customer standards and requirements • statutory regulations and codes of practice • software standards • BS, ISO or BSEN standards and procedures • other international standards |
| 2.11 | Deal promptly and effectively with problems within their control, and seek help and guidance from the relevant people if they have problems that they cannot resolve |
| 3 | 2a. Know how to test engineering software | 3.1 | Explain the specific safety precautions to be taken when working with software development environment hardware (to include such things as safety guidance relating to the use of visual display unit (VDU) equipment and work station environment such as lighting, seating, positioning of equipment; repetitive strain injury (RSI); the dangers of trailing leads and cables; how to spot faulty or dangerous electrical leads, plugs and connections) |
| 3.2 | Explain the importance of good housekeeping arrangements (such as cleaning down work surfaces; putting disks, manuals and unwanted items of equipment into safe storage; leaving the work area in a safe and tidy condition) |
| 3.3 | Describe the relevant sources and methods for obtaining any required technical information relevant to the test script/case being produced (such as new model brief/request, drawing briefs, specification sheets, request for changes or modifications to code; technical publications, calculations, software requirements) |
| 3.4 | Explain test methodologies and national, international and relevant company software test procedures (such as black box, white box testing) |
| 3.5 | Describe the identification of the correct version of software tool, and the various testing techniques that are supported by the tool |
| 3.6 | Explain how to use and configure the testing environment (such as target, host and target simulator) |
| 4 | 2b. Know how to test engineering software (continued) | 4.1 | Explain the basic principles of software testing, and how to create suitable tests for the particular application |
| 4.2 | Explain how to access the specific software requirements, design model and code to be tested |
| 4.3 | Explain the national, international and organisational standards and conventions that are used for the test script/case and results |
| 4.4 | Explain the application and use of software testing tools |
| 4.5 | Explain how to access, recognise and use a wide range of standard components and symbol libraries from the testing tools |
| 4.6 | Explain the need for configuration control on all test artefacts (such as ensuring that completed test script/case and results are approved, labelled and stored on a suitable storage device) |
| 4.7 | Explain why it is necessary to be able to recall previous issues of test script/case and results |
| 4.8 | Explain when to act on their own initiative and when to seek help and advice from others |
Don't show this message again.