Engineering software testing

URN: SEMEM452
Business Sectors (Suites): Engineering and Manufacture Suite 4
Developed by: Enginuity
Approved on: 30 Mar 2017

Overview

This standard identifies the competences you need to test software as part of the product definition activity, in accordance with approved procedures. You will be given a detailed brief and will be required to assess these requirements and to extract all necessary information in order to carry out the software test activity. You will need to select the appropriate software test method to use, based on the type and complexity of the software functions/software design/requirements to be tested. You will be expected to use current British, European, international and company standards to test the software.  Peer review feedback will also need to be evaluated and undertaken, and any lessons learned from the activity will need to be shared within the business.

Your responsibilities will require you to comply with organisational policy and procedures for working in the software development team. You will be required to report any problems with the computer hardware, software or procedures that you cannot personally resolve, or that are outside your permitted authority, to the relevant people. You will be expected to work to verbal/written instructions and draft specifications, with a minimum of supervision, taking personal responsibility for your own actions and for the quality and accuracy of the work that you carry out.

Your underpinning knowledge will provide a good understanding of your work, and will provide an informed approach to applying software test procedures. You will understand the computer system and software used, and its application, and will know about the various tools and techniques used to test the software, in adequate depth to provide a sound basis for carrying out the activities to the required specification.

You will understand the safety precautions required when working in the software development team. You will be required to demonstrate safe working practices throughout, and will understand the responsibility you owe to yourself and others in the workplace.


Performance criteria

You must be able to:

  1. work safely at all times, complying with health and safety legislation, regulations, directives and other relevant guidelines
  2. plan the software testing activities before you start them
  3. use appropriate sources to obtain the required information for the software testing activity
  4. access and use the correct software test tools
  5. use appropriate techniques to create the software tests
  6. use references that follow the required conventions
  7. produce the finished test script/case, with sufficient detail to allow execution
  8. make sure that the test script/case is checked and approved by the appropriate person
  9. save and store the test script/case as the appropriate file type and in the correct location
  10. execute a test script/case and record the results
  11. undertake and evaluate peer review feedback, and identify what lessons can be learned from the feedback
  12. provide technical feedback on the engineering software testing activity undertaken including lessons learnt and those lessons which can be shared within the business
  13. review the results of the test script/case
  14. deal promptly and effectively with problems within your control, and seek help and guidance from the relevant people if you have problems that you cannot resolve

Knowledge and Understanding

You need to know and understand:

  1. the specific safety precautions to be taken when working with software development environment hardware (to include such items 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)
  2. the importance of good housekeeping arrangements (such as cleaning down work surfaces; putting media, manuals and unwanted items of equipment into safe storage; leaving the work area in a safe and tidy condition)
  3. 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)
  4. test methodologies and national, international and relevant company software test procedures (such as black box, white box testing)
  5. identification of the correct version of software tool, and the various testing techniques that are supported by the tool
  6. how to use and configure the testing environment (such as target, host and target simulator)
  7. the basic principles of software testing, and how to create suitable tests for the particular application
  8. how to access the specific software requirements, design model and code to be tested
  9. the national, international and organisational standards and conventions that are used for the test script/case and results
  10. the application and use of software testing tools
  11. how to access, recognise and use a wide range of standard components and symbol libraries from the testing tools
  12. 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)
  13. how to evaluate and undertake any peer review feedback and how any lessons learned from the engineering testing activity can be shared within the business
  14. why it is necessary to be able to recall previous issues of test script/case and results
  15. when to act on your own initiative and when to seek help and advice from others

Scope/range


Scope Performance

  1. Prepare for the software testing activities, by carrying out all of the following:

    1. check that the working environment is in a safe and appropriate condition and that all working equipment is in a safe, tested and usable condition (such as cables undamaged, correctly connected, safely routed)
    2. start the appropriate software test tool
    3. set up the testing environment and select a suitable template/folder
    4. identify relevant software requirements/design to be tested against
    5. identify the required standards and all relevant sources (such as software requirements, design and software test methods)
  2. Use four of the following to obtain the necessary data to produce the required test script/case:

    1. change order/modification request                                  
    2. standards reference documents
    3. technical publications                                                      
    4. specifications
    5. calculations                                                                      
    6. regulations
    7. software requirements                                                      
    8. software design
    9. technical notes (such as meetings/discussions, e-mail)      
    10. other specific available data
  3. Demonstrate how the software testing takes account of seven of the following:

    1. function                                  
    2. cost                       
    3. operating environment
    4. quality                                  
    5. lifetime of the product  
    6. interfaces
    7. testing method                          
    8. accuracy                 
    9. safety
    10. resources (such as memory, performance and bandwidth)        
    11. design structure      
    12. software requirements
    13. run time sequencing
    14. system/software safety requirements
  4. Carry out all of the following before producing the software test script/case:

    1. ensure that the data and information you have is complete and accurate
    2. analyse the data and information to identify the test script/case requirements
    3. recognise and deal with problems (such as technical issues and lack of information, or incorrect information)
  5. Use both of the following modelling methodologies to produce the software test script/case:

    1. black box
    2. white box
  6. Create/modify the software test script/case using five of the following:

    1. objects                        
    2. classes               
    3. types
    4. functions                            
    5. procedures           
    6. data
    7. change requests                     
    8. test rigs specifications
  7. Run the test script using one of the following:

    1. target simulator environment      
    2. host environment           
    3. target environment
  8. Check the test script/case for all of the following:

    1. completeness                           
    2. traceability                    
    3. accuracy
    4. sequencing                             
    5. coverage
  9. Save and store the test script/case and results in appropriate locations, to include carrying out all of the following:

    1. check that the test script/case and results are correctly titled, referenced and annotated
    2. ensure that your test script/case and results have been checked and comply with company procedures
    3. save the test script/case and results to an appropriate location (such as storage device, configuration database)
    4. register and store the test script/case and results in the company information system (where appropriate)
    5. record and store any changes to the test script/case and results in the appropriate company information system
    6. ensure that a separate backup copy is created and placed in safe storage
  10. Produce a test script/case which complies with one of the following:

    1. company standards and procedures
    2. customer standards and requirements
    3. statutory regulations and codes of practice
    4. software standards
    5. BS, ISO or BSEN standards and procedures
    6. other international standards

Scope Knowledge


Values


Behaviours

​Additional Information

You will be able to apply the appropriate behaviours required in the workplace to meet the job profile and overall company objectives, such as:

  • strong work ethic
  • positive attitude
  • team player
  • dependability
  • responsibility
  • honesty
  • integrity
  • motivation
  • commitment

Skills


Glossary


Links To Other NOS


External Links


Version Number

1

Indicative Review Date

31 Mar 2020

Validity

Current

Status

Original

Originating Organisation

Semta

Original URN

SEMEM452

Relevant Occupations

Corporate Managers and Senior Officials, Engineering, Engineering and Manufacturing Technologies, Functional Managers

SOC Code

1121

Keywords

engineering; leading; black box; white box; quality; testing method; design structure; interfaces