Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Feature

User story

As a user
I want to be able to read a message
So that I am able to know what another user sent me

Use caseUC-402: Read message
Test data

The test data is added automatically when starting the automated test scripts.

The test data can be found in the project at:

  • src/test/resources/testdata/readMessages.json
Expected resultCheck the response of the webservice call.
Actual resultCheck the front-end of the application under test.
Test pass conditions

The following values need to be verified:

  • Document title
  • Document filename
  • Patient INSS
  • Is important
  • Is encrypted
  • Document content

The following values need to be verified for every attachment:

  • Annex title
  • Annex filename
  • Annex content

If the message is in the inbox:

The following values need to be verified:

  • Sender first name
  • Sender last name
  • Sender quality

If the message is in the sent box:

The following values need to be verified:

  • Destination first name
  • Destination last name
  • Destination quality

Scenarios (Cucumber)

Code Block
languagegherkin
titlereadMessage.feature
#Remove the @ignore-tag(s) of scenarios you want to start testing.

@ignore
Feature: TS-402: Read message
  As a user
  I want to be able to read a message
  So that I am able to know what another user sent me

  @ignore
  Scenario: Read a basic message from the inbox
    Given user is logged in
    When user is consulting the INBOX
    And user reads the 'read: basic' message
    Then the correct 'read: basic' message is shown correctly in the INBOX

  @ignore
  Scenario: Read a message from the sent box
 with two  recipients
Given user is logged in
    When user is consulting the SENTBOX
    And user reads the basic 'read: two recipients' message
Then the 'read:  Then the correcttwo recipients' message is shown correctly in the SENTBOX

  @ignore
  Scenario: Read an encrypted message
    Given user is logged in
    When user is consulting the INBOX
    And user reads the 'read: encrypted' message
    Then the correct 'read: encrypted' message is shown correctly in the INBOX

  @ignore
  Scenario: Read a message with an attachment
Given user is logged Givenin
When user is consulting loggedthe in
    When user is consultingINBOX
And user reads the 'read: attachment' message
Then the 'read: attachment' message is shown correctly in the INBOX

@ignore
Scenario: Read a message with two Andattachments
Given user reads the message with an attachment
    Then the correct is logged in
When user is consulting the INBOX
And user reads the 'read: attachments' message
Then the 'read: attachments' message is shown correctly in the INBOX

  @ignore
  Scenario: Read an encrypted message with an attachment
    Given user is logged in
    When user is consulting the INBOX
    And user reads the 'read: encrypted message with anattachment' attachmentmessage
Then the 'read: encrypted Thenwith theattachment' correct message is shown correctly in the INBOX