• Created by Unknown User (benjamin.vanrietvelde.ext@imec.be), last modified by Unknown User (steven.machtelinckx.ext@imec.be) on Jun 20, 2018

Description

This page contains the manual for the usage of the SynapseRT plugin in order to perform tests.

Usage

Imec will provide a JIRA ticket where tests can be performed. This will have an issuetype called 'Test Plan'. This issue will always be used to perform the tests.

When it has been communicated that your application has to be tested (again), Imec will open the 'Test Plan', assign the ticket to your tester and provide the tests.

Once the 'Test Plan' has been assigned to your tester, you can start testing.

Performing the tests

This contains the detailed explanation on how to perform the tests (screenshots are also provided beneath the explanation):

  1. Navigate to the Test Plan.
    1. The Test Plan can be found in your JIRA project. It will have the name 'Test Plan <Name of Application>'. If your project has multiple Applications, then the same amount of Test Plans will exist. Make sure to pick the correct one.
  2. Set the status of the ticket to 'In Progress'.
  3. Go to the 'Test Cycle' segment within the ticket. This segment contains all Test Cycles for your application.
    1. A Test Cycle will contain the tests that have to be performed and allows for the ability to alter the results.
  4. Open the correct Test Cycle by clicking on the cycle name (in the Cycle column, this should always be a date).
    1. Only 1 Test Cycle will ever be active at a time. It is this Active Test Cycle that you have to open.
  5. A new page should have opened up. This is the Test Cycle Page. This will list and link all the tests that have to be performed  for this cycle. It will also contain a small summary of the test details.
  6. The 'Key' column will link you to the JIRA ticket of a test.
  7. In the description of this ticket, you will find a link to where you can find the test.
    1. All details on how to perform the test itself can be found here. The name of the ticket will be the test that you have to perform.

  8. While performing the test, make sure you attach the various prints that the Application can generate (which one is necessary should be clear from the test description), together with all the files that EVS generates (these can be found in the processed folder) and screenshots of the UI.

    In case a test contains a writing aspect (tests that do contain this, will always have 'W-' in its name), perform the EVS action EXPORT on the used test patient after the test case has been completed. The files that EVS generates from this action have to be attached (these can be found in the processed folder). One of these files is the validation file (with a .val extension). This file should contain no validation errors.

  9. After a test is finished, you can navigate back to the Test Cycle Page.
  10. Click on the 'Execute' button of the test that you have just performed.
  11. This will open the Test Run Page. Change the values of the 'Result' column to what you have observed from the results. The values can be 'Passed', 'Failed', 'Blocked, 'Not Tested' or 'NA'.
    1. It is important to note that the result of the entire Test Run will be derived from this, depending on priority. The priority goes like this: 'Failed' → 'Blocked' → 'Passed' → 'Not Tested' → 'NA'. This means that once a single Test Step Result is tagged as 'Failed', the entire Test Run will be considered failed. In order for a Test Run to be considered as 'Passed', each Test Step Result must be either 'Passed' or a value with lower priority than 'Passed'.
    2. You will notice that the Test Steps contains codes like 'TS-1'. This points to the 'Expected Results' part of a test (on the Confluence page).
  12. In the 'Attachment' segment, attach all the prints, files and screenshots that you have saved for this test.
  13. Once the results have been altered and the attachments were added, you can click on the close button.
  14. Steps 6 to 13 have to be done for each test in the Test Cycle.
  15. Once all tests have been completed, navigate back to the Test Plan ticket.
  16. Leave a comment on the Test Plan ticket in order to give notification that the Test Cycle has been executed. This comment should include the name of the Test Cycle that was executed.








Workflow

This describes the actions that have to be performed by the Vendors in short. All details on how to perform said actions can be found in this manual.

  1. Navigate to the Test Plan of your project
  2. Set the ticket to 'In Progress'
  3. Open the 'Active' Test Cycle Page
  4. Perform the tests that are required for the Test Cycle
  5. Alter the results of the Test Steps in the Test Run Page
  6. Attach prints, generated processed files and UI screenshots to the Test Runs
  7. When finished, leave a comment in the Test Plan ticket and include the name of the Test Cycle.
  • No labels