Test Case 2 - MyOSCAR to OSCAR message
Edited by:
DRAFT
Description:
Send message from MyOSCAR -> OSCAR
Action | Origin | Class | Calling Method | Further Details |
---|---|---|---|---|
Search Allergy | OSCAR | PHRMessageAction | sendPatient | Possible exceptions thrown 1) java.net.SocketTimeoutException: SocketTimeoutException invoking https://localhost:8091/myoscar_server/ws/MessageService: Read timed out |
Â
Actors/Related actors:
- Care Provider
- Demographic
- Help Desk
Pre-action requirements/state:
- Care Provider is active in OSCAR
- Demographic is active in OSCAR and registered for MyOSCAR
- There is an established relationship* (access and sharing) between the Demographic and Care Provider
- A Care Provider must REPLY to messages, where Demographic users can reply and create new messages (pending accessing and sharing confirmation)
Post-action state:
- OSCAR and MyOSCAR are running as expected.
Steps to perform the test case:
- Login to MyOSCAR as Demographic user
- Go to the messages area
- Click on new message
- Select the Care Provider from the list of options
- Enter in the message details
- Click send
Failure Steps:
- Not able to send the messages
Success Steps:
- Messages are sent/read and the appropriate folders (inbox, sent, read, new...etc) reflect folders updated state (new, read, sent...etc)
Alternate Flows:
- Please see each specific use case/test case for more details.
Special Requirements/Notes:
N/A
Links:
N/A