According to the UiPath Document Understanding Process template, the best way to test the code in a development or testing environment is to create test data based on the use case developed, anduse it to test both the existing and the new tests. The test data should include different document types, formats, and scenarios that reflect the real-world data that the process will handle in production. The existing tests are provided by the template and cover the main functionalities and components of the Document Understanding Process, such as digitization, classification, data extraction, validation, and export. The new tests are created by the developer to test the customizations and integrations that are specific to the use case, such as custom extractors, classifiers, or data consumption methods. The test data and the test cases should be updated and maintained throughout the development lifecycle to ensure the quality and reliability of the code.
References:
Document Understanding Process: Studio Template
Document Understanding Process: User Guide