Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Connector Toolkit
  3. Before you begin
  4. Develop a connector for Cloud Data Integration
  5. Import a connector
  6. Debug the connector code
  7. Connection attributes
  8. Type system
  9. Connector metadata
  10. Partitioning capability
  11. Manual changes to Informatica Connector Toolkit source code
  12. Runtime behavior
  13. Connector example: MySQL_Cloud
  14. Version control integration
  15. Appendix A: Metadata models
  16. Appendix B: ASO model
  17. Appendix C: Connector project migration
  18. Appendix D: Frequently used generic APIs in Informatica Connector Toolkit
  19. Appendix E: Frequently asked questions

Cloud Data Integration Connector Toolkit Developer Guide

Cloud Data Integration Connector Toolkit Developer Guide

Phase 5: Generate and run the test scenarios

Phase 5: Generate and run the test scenarios

After you create and export a new connector, you can test the connector using the automation framework. The framework generates and runs the test cases.
After you export a connector, perform the following tests:
  • Code Acceptance Test (CAT) or Unit Test.
    Units tests are standalone tests. You can generate the test case after you upload data in the project explorer. After the test run, a status report is generated without any external dependency.
    It is mandatory to run unit test scenarios. If you do not run unit test scenarios, the package validation for the connector fails during sandbox deployment in INFAConnect.
  • Product Acceptance Test (PAT) or Integration Test.
    Integration tests require the configuration details to generate and execute the test cases. It requires user intervention for manual upload of data to the pod.
When the automation framework runs, it performs the following tasks:
  1. Analyzes the connector package and generates the test suite. You can use the test suite to test the functionalities in a connector. For example, you can test the connection, verify the record and field details, search records, and test the read, write, filter operations.
  2. Runs the test cases to validate the unit and integration tests. You can run the test cases separately.
  3. Populates a single unified test report for both the unit and integration tests. You can see the PASS and FAIL status in the report.

0 COMMENTS

We’d like to hear from you!