Skip to main content

User Acceptance Testing (UAT)

You should use your organizations best practice when creating a Test Plan for your Content Portal implementation.

Test cases are intended to validate that each function of the solution, as described in the Solution Functional Description section of this document, works as described.

The test cases should also demonstrate the solution’s ability to handle and log errors in detail to aid in troubleshooting, and verify that the correct numbers of licenses are debited from the available license transaction pool (if applicable).

The format for test cases is up to you as the user / administrator, but the test cases should cover the primary functional components of the solution and include the following elements:

  • Solution Assumptions. These assumptions may encompass the connected system (e.g. Perceptive Content / ImageNow) components that should be defined and configured prior to certification run-through.
  • Connected system (e.g. Perceptive Content / ImageNow) API operation Errors. Test cases should ensure that any errors relating to
  • Connected system (e.g. Perceptive Content / ImageNow) APIs or connections to Message Agent/Integration Server are covered (in this example).
  • Third Party System Errors. Test cases should ensure that any errors relating to any third-party systems or infrastructures are covered (such as AssureSign or TouchNet integrated systems systems).
  • Number of connected system (e.g. Perceptive Content / ImageNow) Transactions (per test case). The number of connected system (e.g. Perceptive Content / ImageNow) API transactions should be defined for each test case. This information is used to validate that the solution utilizes the proper amount of transactions.
  • Solution Logging (per test case). Appropriate logging should be available for each test case to showcase that the solution provides thorough and understandable logging to the end user.

Example test cases

System Acceptance​

Once your Jadu Content Portal system installation has been completed, it is for you to assure the platform to your satisfaction. The implementation is deemed complete when you successfully create and publish a form (generally during foundation level training).