Quick Start

Familiarise with the registry

Spend time with the application to understand the different areas. Conduct exploratory testing to give yourself an idea of how the internal workflows of the system are set up. This exercise will ensure you know how the application works. Once you’ve done this will give you an idea some of the scenarios you are going to automate.

Types of tests

There are 2 types of test types that you can write:

• Automated
• Manual

Both types have a different strategy and manual test cases can be partially automated to create the preconditions.

What should be Automated?

• Repetitive tasks like testing the same common component over and over on different services
  • Error conditions
  • End to End scenarios with specific business rules.
  • Validations of Invalid config
  • Penalty fees and Fees
  • Data Preparation for manual test scenarios

Note: For more scenarios please follow Test Scenario Examples

Test Documentation

The following is an example of Test Scenario documentation

• Feature: Path to the test in the project. The feature name must be unique
• Scenario Type: Functional Testing / Automated (Happy Path/Error Condition/etc)
• Precondition – Precondition before start the test.
• Scenario:
  • The purpose of this test scenario (e.g., Check node properties as an internal user with role SEC_CREATE_USER, Create New Internal Staff Account – AGENCY type, etc.)
  • This summary will also be used as the test scenario
• Test Data Requirement: For example specific entity Name to be used
• User Role: The user role to be used. Internal User/ External User / Organisation User/ Other types of user
• REQ-REF: Requirement if exist. This is going to be useful to search and track requirements that change.
• Document Version: This is the Catalog/ BR version if exists.