ECITB Creatio and ECITB eAssess - Operational Testing Instructions

Firstly, thank you 

Thank you so much for your time, effort and attention to detail during our Operational Testing phase (known as ‘testing’ throughout this document). Your efforts are greatly appreciated and are an important part of system development. We could not have done this without you!
  

What is testing? 

testing is an important final step before platforms go live. It’s the stage before launch where we seek feedback through testing to ensure the system, flow and user interface perform as expected. 

• What is User Interface? 

User Interface is the visual and interactive elements you see and use on the platform – the layout and design of screens, buttons, icons, and menus. User interface is essentially about ensuring the platform looks good and is both easy to use and functional.

Why be involved in testing? 

Being involved in testing gives you the opportunity to preview our new platforms, gain a deeper understanding of platform functionality, assess if the platforms are fit for purpose and provide valuable feedback. 

Being a tester is an important to platform development. Your attention to detail, valuable feedback, and commitment to testing will help us deliver the right product for you and other customers, and we thank you for your time, effort and support. 

When is testing happening? 

External testing is from 2^nd February – 13^th February, but we ask that you start testing as soon as you can and inform us as soon as you have completed your testing, so we can investigate any issues straight away. 

Workbooks: You will be emailed two excel files, which we refer to as ‘workbooks’. You need to complete both workbooks. Workbooks are allocated to each tester, so they all have personalised names. Please do not change the workbook name. Workbooks are named as follows 

• Provider name (2) UAT 2 test script
• Provider name UAT 2 test script

Each workbook has several tabs at the bottom. Each tab is a ‘test script’ – basically a set of steps for you to follow. The tabs have names like C3.1, which is for our reference. Please do not change these names and make sure you complete all tabs. 

Test scripts: testing is about checking everything works as expected. You do this by following the 'test scripts' to complete ‘tasks’. The tasks you will be asked to complete will be tasks you would complete in your role. 

You will need to have both the test script and ECITB Creatio open whilst testing, so it may be better to print scripts or have them on another screen if you use 2 monitors. 

The test scripts are set so that every step you need to take for each task is clearly listed in the order they need to be followed. Following test scripts in the correct order and selecting the correct information will ensure there is a systematic approach to testing. All steps will be detailed and will describe the expected outcomes at each step to make this easy for you. 

Failed test scripts: testing is about finding any snags or issues in a platform before launch. These may be a test script that does not work well or flow well, tasks that do not link up, or simply buttons that look confusing. If you find any issues in your testing, this is what the process is for, so please make sure you let us know! We cannot fix things if we are not aware. 

Test scripts have a pass/fail column at the end of each step. Where there is a failure, we ask that you take a screenshot and save images on the test scripts and add any notes about the failure. Please make these as clear and as detailed as possible. Instructions on taking a screenshot are below.

How do I conduct testing?

Test scripts have been prepared for each process undertaken in Creatio and eAssess.  Following the test scripts will ensure there is a systematic approach to testing.

Completing testing – Before you start

If you did not attend the briefing session, please watch the recording here. 

Please complete the test scripts as soon as possible. You will need to have both the test script and ECITB Creatio and ECITB eAssess open whilst testing so it may be better to print scripts or have them on another screen if you use 2 monitors, or you can flip between the screens. 

Completing testing – Step by step  

The system is available Monday to Friday, 8am – 8pm. Closed on weekends.

Testing is completed in a test site to ensure live data is unaffected.

Click the link to log into the testing environment test site

• A dummy employer account will be set up for you. You will receive two system emails from ecitb-system-notification@ecitb.org.uk.  The first will notify you of your username, the second will request that you reset your password. Once you have completed these actions you can start testing. If you have not received a system email please check your junk mail, and then contact cheryl.collett@ecitb.org.uk 

• Your workbooks may have multiple tabs - each tab is a separate test script. You need to complete the test scripts in order as some scripts will not work unless you have done a previous script. This is noted in the ‘prerequisites' on the script. 

• Work through the test script step by step
  • Make sure you add your name and test date in the columns provided
  • Where a script asks you to enter a reference, please use the one provided in the test script adding your initials at the end  

• If there is a failure, note this in the Pass/Fail column for the relevant step in the test script.  In the next column note the Actual Result providing as much detail as possible.  Please also provide screenshots by pasting them into the worksheet.  (How to take a screenshot).

• If it looks wrong, report it i.e. The script will tell you what to expect but can you see defects where performance or display is not what you expect? Let us know how the system feels for you in terms of display, how intuitive it is etc. 

• Upon completion of your test script follow the instructions at the bottom of the script for your next step. 
  • This may be moving on to complete a further script 
  • Or letting us know you have completed your tests by dropping a note into our testing teams’ call by clicking this link and emailing the test scripts to  helen.craig@ecitb.org.uk

Where a script or part of a script has failed, we may follow up with you. Where work is required in the background, we may come back to you for a re-test.  

Help! Support for testing 

If you have general non-testing related questions, contact helen.craig@ecitb.org.uk

For questions directly related to testing drop a message into the testing teams call by clicking this link or dial in for a discussion. Test failures should be logged on the test script; you do not need to email these separately. This is so general queries are handled efficiently, and specific test issues are properly documented. 

Thank you again for your time, testing is a very important final stage before we go live with ECITB Creatio and eAssess and ensures it is fit for purpose.