is anyone build the Automated test frameworks for service graph connectors ?

[M Iftikhar]

Hi @btejaswini,

Yes, automated test frameworks for Service Graph Connectors can be built! Could you please clarify:

•  What type of testing are you looking for?
• Unit Testing for connector development?
• Integration Testing for connector workflows?
• Regression Testing for connector configurations?
• Performance Testing for connector operations?

Common approaches include:

• ServiceNow ATF (Automated Test Framework) for workflow testing
• Custom scripts with REST API testing
• Selenium for UI-based connector testing
• CI/CD pipelines with Jenkins/GitLab for automated deployment testing

Typically, teams test:

• Data transformation rules
• Connection establishment
• Discovery patterns
• CI record creation
• Error handling scenarios

Share more details about your specific use case, and I can provide a tailored solution!

Hope this helps! 

If my response helped, please mark it as the accepted solution so others can benefit as well.

[btejaswini]

Hi lftikhar,
My scenario is build atf for meraki and incident management

I followed these steps to test the Meraki data import: Created a record in the sys_import_set table using the Meraki data source. Verified that the record was created in the Meraki Devices staging table.
third step run transformation, but it failing The import set remains in a null state instead of processed. I tried increasing the timeout duration, but the system only allows up to 99 seconds. It doesn’t accept 3-digit or 4-digit values. After resolving this, I also need to validate whether incidents are being created when alerts are triggered from Meraki.

[btejaswini]

my scenario is test the Meraki service graph connector mainly to capture the incident management
data import: Created a record in the sys_import_set table using the Meraki data source. Verified that the record was created in the Meraki Devices staging table.
third step run transformation, but it failing The import set remains in a null state instead of processed. I tried increasing the timeout duration, but the system only allows up to 99 seconds. It doesn’t accept 3-digit or 4-digit values. After resolving this, I also need to validate whether incidents are being created when alerts are triggered from Meraki.