Skip to content

Manual System Tests

Jump to bottom Edit New page
Thomas Lohnert edited this page Jan 31, 2018 · 16 revisions

Wiki > Deployment > Manual system tests

Manual system tests should be performed as part of the release cycle and should be performed once a branch has been created. See Creating-a-release

  1. Create a shared spreadsheet to record test results

    1. Copy the manual system tests template to a shared folder.
    2. Set the spreadsheet as shared (Review -> share workbook). This means people can work on it in parallel, save to update your sheet with other peoples changes.

  2. Choose an instrument to test on (local or remote) and install the test version

    1. Navigate to the an ibex_utils folder and pull the latest changes from git
    2. Check instrument_deploy.bat contains the correct version number for the current release. If so, run it
    3. Follow the instructions on the command line interface. If you are unsure whether a step needs to performed, ask someone from the team.
    4. [DEMO only] run create_icp_binaries.bat in the EPICS directory. If the instrument never makes it out of "Processing" with the ISISDAE IOC throwing errors that read "CoCreateInstanceEx (ISISICP) : The system cannot find the path specified", this is how you fix it.

  3. Run through the tests on the spreadsheet. Each line is a test with a description which should contain actions to perform and what should happen should be noted. If that is not in the test then add what did happen/or should have happened to that test.

    • If a bug is discovered:

      1. Record it on the bugs sheet.
      2. If you know it is ticketed then add a ticket, record the ticket number and if it needs to be fixed for the release then add label "for release". If you are not sure then wait.

  4. After testing is done consider all bugs and decide for each whether you should:

    1. Create a ticket - if the fix is needed for this release, then append the "for release" label to the ticket.
    2. Ignore - write why it is ok to ignore this
    3. Fix - if it is a documentation error and can be fixed now.

  5. Once the tests are completed, add the spreadsheet containing the tests outcome here.

  6. Remove all test results and update the new template.

Add a custom footer
Add a custom sidebar
Clone this wiki locally