In order to ensure the best experience for our mutual customers, we require validation and sign-off for four different aspects of the integration.
- Your team will first validate that the integration works end-to-end.
- The Databricks engineering team will validate the Partner Connect integration functionally works in all use cases.
- The Databricks partner solution architect team will validate the "core integration" works using Partner Connect's permissions setup.
- The Databricks product team will validate the usability of the integration for a new user who is unfamiliar with your product.
We require partners to validate their API implementation using the test suites provided in this project.
We require partners to validate their end-to-end experience for all the applicable test cases.
Prior to artifact submission, testing can be done using the Self-Testing Partner CLI. This CLI will create a testing tile visible only within your workspace which will allow you to test your integration but lacks some configuration options (e.g. icons, descriptions).
Once artifacts have been submitted, we can enable a full version of your tile in any workspace.
We will schedule a one-hour video call to manually execute the test cases with you. Your team should come prepared with the ability to reset our test accounts and connections.
A partner solution architect will validate the "core integration" works when used through Partner Connect. This step does not require a meeting.
The Databricks product team will validate the usability of the integration from a new user's perspective. In particular, the product team will validate:
- A user does not have to select Databricks as the connector.
- A user does not have to manually enter the configuration that was passed via the Connect API.
- It is seamless for a user to find the Databricks connection when they land in the partner product. The user will not get lost trying to find or use the connection to Databricks.