To Do Button - To Do's
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- HomeView - My To Do's widget
Scenario 1: Adding "To Do Button" functionality to Modeled Form
Specific Setup:
- Have a modeled form with prompt "Enable To-Do Creation From Form" set to "Yes"
- Have a user who is a staff member
- Have the "My To Do's" widget on their home view
Steps
- Open the modeled form
- Populate the desired fields on the form
- Click the [Create To Do] button displayed under the "Submit" button
- On the "Create To Do" dialog window, add a staff member using the "Select Staff" prompt
- Populate the "Note" field with any desired text
- Click [Save]
- Click "X" to close the form without submitting
- Validate a message stating "The defined to-do message cannot be sent because the form was not submitted" is displayed
- Click [OK]
- Return to the form
- Repeat steps 2 thru 6
- This time click [Submit]
- Validate a To do is present in the "My To Do's" widget
- Click "Review To Do Item"
- Click "Reviewed"
- Click [Submit]
- Validate the To Do has been successfully reviewed and removed from the To Do list
- Open the modeled form
- Select the same row used in the previous steps for edit
- Make any changes to the form
- Repeat steps 4 thru 7
- Validate a message is displayed "A to-do message has been defined. Would you like to send the to-do?"
- Click [No]
- Validate the "My To Do's" widget does not contain a To Do
- Repeat steps 19 thru 21
- Validate a message is displayed "A to-do message has been defined. Would you like to send the to-do?"
- This time click [Yes]
- Validate a To Do is present in the "My To Do's" widget
- Click "Review To Do Item"
- Click "Reviewed"
- Click [Submit]
- Validate the To Do has been successfully reviewed and removed from the To Do list
|
Topics
• Forms
• Modeling
• To-Do's
|
Episode drop down fields
Scenario 1: Validate results displayed in "Episode" drop down fields
Specific Setup:
- Have a client admitted in one or more episodes
- Have access to a form that contains an "Episode" drop down list within the form. For example, the "Progress Note (Group and Individual)"
Steps
- Access the 'Progress Notes (Group and Individual)' form.
- Select the client in the "Select Client" field
- Click the "Select Episode" drop down list
- Validate a row is displayed for each of the clients existing episodes
- Validate that the format of each episode row displayed is: "Episode # (value) Admit:(date value) Discharge: (Date Value) Program: (Program Value) "
- Validate there are no unexpected characters inserted between words or values in the episode rows that are displayed. For example "@" or "&" characters
- In the "Search Clients" field on the home view, select the client
- Click the "Episodes" drop down list in the upper corner of the home view
- Click "All"
- Validate the "Episodes" selection box displays a row for each of the clients existing episodes
- Validate that the format of each episode row displayed is: "Episode # (value) Admit:(date value) Discharge: (Date Value) Program: (Program Value) "
- Validate there are no unexpected characters inserted between words or values in the episode rows that are displayed. For example "@" or "&" characters
|
Topics
• Forms
|
Open Forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Event Log Report
- Master Client Inquiry
Scenario 1: Validate a form left open from a prior day can be executed or exited successfully
Specific Setup:
- Have two "Entity" based forms, [FormA] and [FormB], that had been left open from a prior day. For example "Update Client Data" and "User Definition"
- Have two non "Entity" based forms, [FormC] and [FormD], that were left open from a prior day. For example form "Event Log Report" and form "Master Client Inquiry"
Steps
- Navigate to [FormA]
- Populate the desired fields on the form
- Submit the form
- Validate the form files successfully
- Return to the [FormA]
- Validate all fields are populated as expected
- Navigate to [FormB]
- Populate the desired fields on the form
- Exit the form
- Validate the form closes successfully
- Navigate to [FormC]
- Populate the desired fields on the form
- Submit the form
- Validate the form files successfully
- Return to the [FormC]
- Validate all fields are populated as expected
- Navigate to [FormD]
- Populate the desired fields on the form
- Exit the form
- Validate the form closes successfully
- Open form "Current Database Locks"
- Validate there are no current database locks listed for the forms submitted or closed in the prior steps
|
Topics
• Forms
|
Copy and Paste
Scenario 1: Validate copy and paste of text from MS-Word documents into Avatar text fields
Specific Setup:
- Have a form that contains a "Scrolling Text" field and a "Non-Scrolling" text field [FormA]. For example, a modeled form
- Have an MS-Word document that contains a mix of standard and special characters as well as special formatting that includes "Bullets" and "Numbering"
Steps
- Open the [FormA]
- Navigate to the "Non-Scrolling Text" field
- Copy the text in the MS-Word containing special characters
- Paste the text into the "Non-Scrolling Text" field
- Validate the text is populated successfully
- Navigate to the "Scrolling Text" field
- Copy the text in the MS-Word containing special characters
- Paste the text into the "Scrolling Text" field
- Validate the text is populated successfully
- Navigate back to the "Non-Scrolling Text" field
- Copy the text in the text field
- Navigate to the "Scrolling Text" field
- Paste the text copied from the "Non-Scrolling Text" into the "Scrolling Text" field
- Validate the text is populated successfully
- Now copy the text in the "Scrolling Text" field
- Navigate to the "Non-Scrolling Text" field
- Paste the text copied from the "Scrolling Text" into the "Non-Scrolling Text" field
- Validate the text is populated successfully
- Submit the form
- Return to the form and edit the row just filed
- Validate the "Scrolling Text" and "Non-Scrolling Text" fields are populated, as expected
|
Topics
• Forms
|