Scope

This page contains the Kmehrmessage(s) for testing the behaviour of the SUT when syncing schemes.

This test is applicable for every software package.

Purpose

The purpose for the read test is to ensure that the SUT syncs with the vault when opening the scheme.

The purpose for the write tests is to ensure that the alterations made by the SUT are uploaded to the vault.

Instructions for EVS use

Each test will contain this EVS export file that has to be uploaded using EVS-action REPLACE.

The EVS parameter writeAsIs must be set to false.


Description (Read)

A scheme will be opened and closed in the SUT (existing or new).
That scheme will be exported using EVS and the version number will be written down. The version number can be found here.

That scheme will be replaced by another scheme in EVS.

After reading the new scheme in the SUT, the test can be verified in the SUT.
The SUT UI should be used as comparison to the EVS PDF.

S21R10: Reading updated scheme

Preparation

  1. Open and close a scheme of a patient of your choosing in the SUT.
  2. Export the current scheme in EVS using the EVS-action EXPORT.
  3. In the processed folder of EVS, open the *.exp from the exported scheme. Write down the version number in the medicationscheme transaction.
  4. Alter the scheme of the same patient using the EVS-action REPLACE.
  5. Open the scheme of the same patient.

Expected results

  • TS-1: There is a scheme with 2 lines on the patient print.
  • TS-2: The contents of the scheme should be the same.
  • TS-3: The version number should be 1 higher than the previous version number.


Description (Write)

A scheme will be opened and closed in the SUT (existing or new).
That scheme will be exported using EVS and the version number will be written down. The version number can be found here.

An alteration to that scheme will be made with in the SUT.
The SUT will sync the changes to the vault.

After syncing with the vault, the test can be verified with EVS.
The EVS PDF should be used as comparison to the SUT UI.


S21W15: Alteration new line

Preparation

  1. Upload the EVS export file using the EVS-action REPLACE with a patient of your choosing. The scheme should have 2 lines.
  2. Open the SUT and add a new medication to the scheme. The scheme should now have 3 lines.
  3. Sync the scheme to the vault.
  4. Generate the EVS PDF by using the EVS-action EXPORT with same patient.
  5. Compare the EVS PDF to the scheme in the SUT.

Expected results

  • TS-1: There is a scheme with 3 lines on the patient print.
  • TS-2: The lines should be the same.
  • TS-3: The version number should be 1 higher than the previous version number.


S21W20: Alteration delete line

Preparation

  1. Upload the EVS export file using the EVS-action REPLACE with a patient of your choosing. The scheme should have 2 lines.
  2. Open the SUT and delete a medication from the scheme. The scheme should now have 1 line.
  3. Sync the scheme to the vault.
  4. Generate the EVS PDF by using the EVS-action EXPORT with same patient.
  5. Compare the EVS PDF to the scheme in the SUT.

Expected results

  • TS-1: There is a scheme with 1 line on the patient print.
  • TS-2: The lines should be the same.
  • TS-3: The version number should be 1 higher than the previous version number.


S21W25: Alteration change line

Preparation

  1. Upload the EVS export file using the EVS-action REPLACE with a patient of your choosing. The scheme should have 2 lines.
  2. Open the SUT and change a medication in the scheme. The scheme should now have 2 lines.
  3. Sync the scheme to the vault.
  4. Generate the EVS PDF by using the EVS-action EXPORT with same patient.
  5. Compare the EVS PDF to the scheme in the SUT.

Expected results

  • TS-1: There is a scheme with 2 lines on the patient print.
  • TS-2: The lines should be the same.
  • TS-3: The version number should be 1 higher than the previous version number.
  • No labels