Introduction to Testing

Testing is an optional but recommended part of Data Collection Studio. By defining test cases from real UI data, Technical Analysts can ensure that there are no overlapping rules and that all expected data is collected accurately. This process helps maintain data integrity and confirms that data collection behaves as intended under various conditions.

Commen Reasons for Errors in Test Cases

In this section, we will cover the common reasons for errors encountered during test case execution and provide guidelines to ensure effective and accurate testing. Properly setting up and managing test cases is crucial for validating data collection rules.

• Test Only Recognized Applications:

  • Ensure that tests at the application level are only for cases where the application is recognized by the window, but no specific window rule matches.

  • Use unique paths for application-level test URLs to differentiate them clearly from the window-level tests (e.g., you can make up URLs that are not real like this: springbeta2024-training.processmaker.net/some-path).

• Naming Conflicts:

  • Test failures can occur due to naming conflicts between windows and rules. Ensure each window and rule have unique names to avoid overlapping.

• Overlapping Rules:

  • Ensure that test cases do not have overlapping rules for the same process ID or dimension ID. Split tests into separate parts if multiple identifiers (e.g., process ID and dimension ID) are found from a single event.

  • For example, Adding Teams and Excel through the Application Catalog will create an error because Excel files viewed in Teams get both Teams and Excel application tags. You can choose which app to use in this scenario.

• Differentiate URLs for Test Cases:

  • Always use distinct URLs for different test cases to prevent conflicts and ensure clarity in test results.

• Handling Multiple Identifiers:

  • When a process has multiple identifiers, such as process ID and dimension ID, avoid conflicts by testing each identifier separately. For example:

    • Use a URL containing process_id but not client_id to test the process ID.

    • Use a URL containing client_id but not process_id to test the dimension value.