Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

*For Zapier CLI

I am currently working on writing unit tests for my zapier App. The documentation doesn’t really give me a good example of this, but is it possible to write unit tests to cover your input fields that contain altersDynamicFields?

The reason why I would like to test this is because the input fields actually makes a call to my API that influences certain fields to appear because the input field has the altersDynamicFields property.

Anybody know a good route for this?

Did you manage to find an answer to this?

Hey @Ryan Learner , 

Excellent question, and apologies this isn’t covered in the docs. I definitely see how helpful that would be. 

Yes, I think this should be doable. 

My main suggestion would be the following:

When invoking appTester in the test, instead of passing the perform, like this (from the example in the docs)...

    const results = await appTester(
      App.triggers.recipe.operation.perform,
      bundle
    );

...pass inputFields, like this:

    const results = await appTester(
      App.triggers.recipe.operation.inputFields,
      bundle
    );

results should then be an array of field definitions. This way, you can run tests with different bundle.inputData mock values and test what fields are/aren’t created.

Does this give you a rough idea of where to start?

Thanks @connorz. That works!

 

Just as a side note, the typescript interface for `appTester` doesn’t like passing `App.triggers.recipe.operation.inputFields` as it doesn’t take `bundle` so needs to be cast.

Reply


Terms & Conditions