Data reports/queries
Scenario 1: Validate data results from reports generated using an ODBC login connection
Specific Setup:
- Create a new user in form "User Definition" [TestUserA] and assign the user permissions to a table, for example table "SYSTEM. patient_current_demographics" is used
- Have a "Crystal Report" [ReportA] created to display data in that table using and ODBC connection configured for [TestUserA]
- Have a second user [TestUserB] who that already has access to that same table as [TestUserA]
- Have a "Crystal Report" [ReportB] created to display data in that table using and ODBC connection configured for [TestUserB]
- In form "Import Reports"
- Using the "Import Report as Form" option, have a report [ReportC] imported configured to run from a menu
- [TestUserC] has access to "Report Definition" form type report [ReportD] for testing. For example, product form "Admits By Program, Zip Code, Ethnicity" can be used
- Have three modeled forms available for testing
- [FormA] is enabled for document routing set in form "Document Routing Setup", to use a crystal report [ReportE] as a template to display the document image. (Note: The "Import Report for Document Routing" option in form "Import Reports", can be used to import the report into the system for use)
- [FormB] configured with a "Post Filing" report [ReportF] that will run at form submission
- [FormC] configured with a "Command Button" on the form that will run a report [ReportG]
- [TestUserC] has access to all forms stated in the setup and has the "Crystal Report" application on their desktop
Steps
- In application "Crystal Reports"
- Open [ReportA], that has the "ODBC" connection configured for [TestUserA]
- Click to process the report
- Validate the report display all data as expected
- Close the report
- Repeat step 1a again to regenerate the report
- Validate results are as expected
- Open [ReportB], that has the "ODBC" connection configured for [TestUserB]
- Click to process the report
- Validate the report display all data as expected
- Close the report
- Repeat step 1c again to regenerate the report
- Validate results are as expected
- Log in Avatar
- Search for and open [ReportC], the report imported to run from a menu
- Validate when selected form the menu, the report launches successfully
- Validate the report display all data as expected
- Close the report
- Repeat step 2a again to regenerate the report
- Validate results are as expected
- Close the report
- Search for and open [ReportD], the "Report Definition" report
- Populate any prompts on the form
- Click to process the report
- Validate the report display all data as expected
- Close the report
- Repeat step 2b again to regenerate the report
- Validate results are as expected
- Search for and open [FormA], the document routing enabled modeled form set to use a "Crystal Report" [ReportE] as template to display the document image
- Populate the form
- Submit the form as "Final"
- Validate the document image is displayed using the format of [ReportE] and data is displayed, as expected
- Approve/ route and submit the document
- Validate submission is successful
- Repeat step 2c again
- Validate results are as expected
- Search for and open [FormB], the form configured with a post filing report
- Populate the fields on the form
- Submit the form
- Validate the form files successfully
- Validate the post filing report [ReportF] is launched
- Validate the data is displayed as expected
- Repeat step 2e again to regenerate the report
- Validate results are as expected
- Search for and open [FormC], the form configured with the command button report
- Populate the fields on the form
- Navigate to the "Command Button" field
- Click the field to launch the report
- Validate [ReportG] is launched
- Validate data is displayed as expected
- Submit the form
- Validate the form submits successfully
- Validate the command button report [ReportF] is launched
- Validate the data is displayed as expected
- Submit the form
- Validate the form files successfully
- Repeat step 2g again to regenerate the report
- Validate results are as expected
|
Topics
• Import Reports
• Query/Reporting
• SQL Data Access
|
Sessions Widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Crystal Reports or other SQL Reporting tool (ReportA)
Scenario 1: "Avatar Sessions" Widget - validate data results
Specific Setup:
- Have user [UserA] logged in who has the "Avatar Sessions" widget on their desktop.
- Have another user [UserB] who has not logged in yet.
- Have a third user [UserC] who has a ODBC connection created to connect to the testing system, that is configured using his userID and password
- [UserC] has a report created [ReportA], to display data in a table in the testing system, using his ODBC connection
Steps
- Log in as [UserA] and note the date and time of login
- Navigate to the "Avatar Sessions" widget
- Refresh the widget and and note the current date and time
- Validate the "UserID" column of the widget includes the expected user ID associated with [UserA].
- If this is a Netsmart hosted system
- Validate the "Login Date" and "Login Time" are consistent with time a date noted in step 1
- Validate the "Last Activity" date and time are consistent with the date and time noted in step 2a
- Note the current number of connections stated in the "# of Connections" column
- Launch any form
- Refresh the the "Avatar Sessions" widget
- Validate the number of connections in the "# of Connections" column has incremented by 1
- Close the form just launched
- Validate the number of connections in the "# of Connections" column has decreased by 1
- Log in as [UserB] and note the current date and time.
- Navigate to the "Avatar Sessions" widget and refresh the widget
- Validate a row for both [UserA] and [UserB] are listed in the widget
- Validate the "UserID" column of the widget includes the expected user ID associated with [UserA]
- Validate the "UserID" column of the widget includes the expected user ID associated with [UserB]
- Repeat step 2b for [UserB]
- Validate results are as expected
- As [UserC]
- Open [ReportA]
- Click to generate the report. Note the date and time
- Validate the report launches successfully
- As [UserA]
- Click the 'Refresh' button on the "Avatar Sessions" widget
- Validate a row for both [UserA] and [UserB] are listed in the widget
- Validate in the "UserID" column of the widget includes the expected user ID associated with [UserA]
- Validate in the "UserID" column of the widget includes the expected user ID associated with [UserB]
- Validate a new row is present in the widget for [UserC]
- Validate in the "UserID" column of the widget includes the expected user ID associated with [UserC].
- Note the number of connections in the "# of Connections" column
- As [UserC], close [ReportA]
- As [UserA]
- Click the 'Refresh' button on the "Avatar Sessions" widget
- Validate the row for [UserC] is no longer present in the widget, as expected
- Validate the rows for [UserA] and [UserB] are still present
- As [UserB]
- Log out of Avatar
- As [UserA]
- Click the 'Refresh' button on the "Avatar Sessions" widget
- Validate the row for [UserB] is no longer present in the widget, as expected
- Validate the row for [UserA] is present, as expected
Data reports/queries
Scenario 1: Validate data results from reports generated using an ODBC login connection
Specific Setup:
- Create a new user in form "User Definition" [TestUserA] and assign the user permissions to a table, for example table "SYSTEM. patient_current_demographics" is used
- Have a "Crystal Report" [ReportA] created to display data in that table using and ODBC connection configured for [TestUserA]
- Have a second user [TestUserB] who that already has access to that same table as [TestUserA]
- Have a "Crystal Report" [ReportB] created to display data in that table using and ODBC connection configured for [TestUserB]
- In form "Import Reports"
- Using the "Import Report as Form" option, have a report [ReportC] imported configured to run from a menu
- [TestUserC] has access to "Report Definition" form type report [ReportD] for testing. For example, product form "Admits By Program, Zip Code, Ethnicity" can be used
- Have three modeled forms available for testing
- [FormA] is enabled for document routing set in form "Document Routing Setup", to use a crystal report [ReportE] as a template to display the document image. (Note: The "Import Report for Document Routing" option in form "Import Reports", can be used to import the report into the system for use)
- [FormB] configured with a "Post Filing" report [ReportF] that will run at form submission
- [FormC] configured with a "Command Button" on the form that will run a report [ReportG]
- [TestUserC] has access to all forms stated in the setup and has the "Crystal Report" application on their desktop
Steps
- In application "Crystal Reports"
- Open [ReportA], that has the "ODBC" connection configured for [TestUserA]
- Click to process the report
- Validate the report display all data as expected
- Close the report
- Repeat step 1a again to regenerate the report
- Validate results are as expected
- Open [ReportB], that has the "ODBC" connection configured for [TestUserB]
- Click to process the report
- Validate the report display all data as expected
- Close the report
- Repeat step 1c again to regenerate the report
- Validate results are as expected
- Log in Avatar
- Search for and open [ReportC], the report imported to run from a menu
- Validate when selected form the menu, the report launches successfully
- Validate the report display all data as expected
- Close the report
- Repeat step 2a again to regenerate the report
- Validate results are as expected
- Close the report
- Search for and open [ReportD], the "Report Definition" report
- Populate any prompts on the form
- Click to process the report
- Validate the report display all data as expected
- Close the report
- Repeat step 2b again to regenerate the report
- Validate results are as expected
- Search for and open [FormA], the document routing enabled modeled form set to use a "Crystal Report" [ReportE] as template to display the document image
- Populate the form
- Submit the form as "Final"
- Validate the document image is displayed using the format of [ReportE] and data is displayed, as expected
- Approve/ route and submit the document
- Validate submission is successful
- Repeat step 2c again
- Validate results are as expected
- Search for and open [FormB], the form configured with a post filing report
- Populate the fields on the form
- Submit the form
- Validate the form files successfully
- Validate the post filing report [ReportF] is launched
- Validate the data is displayed as expected
- Repeat step 2e again to regenerate the report
- Validate results are as expected
- Search for and open [FormC], the form configured with the command button report
- Populate the fields on the form
- Navigate to the "Command Button" field
- Click the field to launch the report
- Validate [ReportG] is launched
- Validate data is displayed as expected
- Submit the form
- Validate the form submits successfully
- Validate the command button report [ReportF] is launched
- Validate the data is displayed as expected
- Submit the form
- Validate the form files successfully
- Repeat step 2g again to regenerate the report
- Validate results are as expected
|
Topics
• Forms Designer
• Widgets
• Import Reports
• Query/Reporting
• SQL Data Access
|