About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

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

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

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.

Question

Test harness for Code steps (Unit and Integration Testing) - prevent repeated errors turning off Zap

  • 4 September 2021
  • 3 replies
  • 81 views
M
Userlevel 2
Badge

If a code block fails repeatedly, Zap Manager will disable the Zap.

Good programming practices would exercise a code block in a unit test, essentially putting the code through scenarios known to have caused problems before (regression testing) and boundary conditions that can have dubious scenarios.

These can avoid failures, exceptions and unwanted results.

Question - what do you recommend for unit testing?

 

P.S. yes, I understand I can upload code blocks as AWS Lambdas and test them there. I’m looking for something simpler.

 

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

SamB
Rank
Userlevel 7
Badge +11

Hey @mrjcleaver!

It looks like a similar question was asked on how to catch errors in a Code step to prevent it from erroring over here:


Hopefully the suggestion in that related thread will be helpful to you in preventing your Zap from being switched off automatically. :)​​​

M
Userlevel 2
Badge

Hi @SamB - it's marginally related. Thanks for looking.

It's one thing is how to address a particular code block (check for each key, and value, and wrap the whole thing in a try/catch).

 

What I'm asking about is how to make sure the team has done that for every code block. i.e. there is professionalism throughout in every zap.

 

Whereas no-code environments like Zapier is targeted as being easy for non-coders, Zapier should still provide dependable results.

 

Test harnesses exercise pieces of functionality to achieve this.

SamB
Rank
Userlevel 7
Badge +11

Ah, I see! Sorry for my misunderstanding here previously, @mrjcleaver. 

I don’t believe we have a recommended unit testing process documented for Code by Zapier steps, but with our developer platform we do recommend using the Jest framework for unit testing. You can find out more about that here: Writing Unit Tests  

Hope that helps! 

Terms & Conditions