Unit Testing in GAS Part 5: Testing Objects and Arrays

If you’re brand new to unit testing, start with the first post in this series to get caught up.

Part 1: QUnit Setup
Part 2: Simple Tests
Part 3: Adding and Updating Functions
Part 4: Error Handling
Part 5: Testing Objects and Arrays

It’s time to dive into deeper equality situations with objects and arrays. Every test we’ve written so far has used a non-strict comparison. In other words, we’ve only been checking value but not type. This is particularly important in JavaScript because of how it handles truthy and falsy values.

For instance, if you were to write a test checking the equality of 0 and undefined, what would you expect? They’re different, right? If you want to try it yourself, you can write a quick test:

QUnit passes the first test because both 0 and undefined are falsy – the values are the same, but the type is different. Using equal as the assertion only checks against the value of the actual and expected arguments. This is where deepEqual helps. Instead of checking values only, deepEqual performs a strict check of both the value and type of the arguments.

Get the Source Code

Here’s the completed source for this post.

Objects and Arrays

We have only looked at simple values – numbers and strings. In this post, we’ll look at using deepEqual and propEqual to test objects and arrays. Rather than jumping right into testing our Calcs class, let’s start with two simpler examples. Start by adding this to your tests.gs file:

This is the first time we’ve defined a variable inside a Qunit.test instance. Each test is a function, so it can have block-scoped variables used in the test. These variables do not affect other functions in the wrapper. Eventually, we will be retrieving exisitng objects and arrays to test, but for now, we’ll define them with each test as necessary.

Because we’re defining a new wrapper, you need to go to config.gs and add objectTests() to the tests() wrapper for these new tests to run:

This is personal preference, really…there is nothing saying you cannot include these checks in the calcTests wrapper we’re using, but I find it helpful to break out tests into similar groups.

Reload the web app and you’ll see a new line passing the array deepEqual check we just wrote. Let’s do the same thing for an Object:

This test will also pass because the objects have strict equality with one another. deepEqual is recursive, meaning it will check for equality even within nested objects:

Checking Constructed Objects

Checking object constructors is complicated. You cannot just define a matching object in the function because deepEqual checks the constructor along with the value. Rather than testing the entire object, it is better to check each part of the object.

This follows with the unit testing philosophy – test the smallest possible pieces of your code. If you want to test the structure of the object, we can assign a variable to an object with the desired properties and test our Calcs object against it with propEqual.

To help with flow control, I’ve added an init() method Calcs which will return the entire object. It doesn’t matter a whole not right now, but it will in future posts.

From now on, when we need to instantiate Calcs, we’ll use Calcs.init().

To test obect properties, let’s add a variable with a known structure to use as our expected value. Then, we’ll call Calcs.init() to get the full object back to compare properties.

propEqual returns true because the properties of both are the same. Calling deepEqual will cause a failure because it checks the properties and the object constructor. Our expected value wasn’t created with a constructor like the actual and the test will fail.

Why might this type of check be important?

If your object returns the wrong type of value, propEqual will fail. For example, changing init to a string value in your expected object will fail when compared with Calcs.init() because it’s expecting a function, not a string.

Using propEqual on your classes can help prevent type errors down the line by ensuring each property matches the expected type. This kind of check, where you specify an expected structure, is called mocking and we’ll look at that in a future post.

Testing Returned Values

What about functions or methods that return structured data? We can use deepEqual to check the returned values. We’re going to add a method to Calcs which accepts an array and integer and returns an array with each value increased by the specified amount. Here’s the test we’ll run:

Our test defines three checks that need to pass:

  1. The first parameter is an array,
  2. the second parameter is a number,
  3. and the returned array is equal to the expected value.

Our method needs to accept an array and a number to add to each value in the array. We should get a new array back with the updated values.

If you reload your web app, all tests should pass. This could also be extended with throws to check for custom error messages like we did back in part 4.

Put it into practice

It’s easy to get sucked into thinking you need to check for exact data, particularly with Objects and Arrays. With unit testing, remember that you’re checking that a piece of your code does what it’s designed to do with any data. Running tests on generic structures gives you a clear idea of what any individual part of your application does. Use propEqual to test mocked objects for structure.


  • equal does a soft comparison (==) and deepEqual uses a strict check (===).
  • deepEqual also checks constructor values for Objects.
  • propEqual compares Object properties (structure) without considering the constructor.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.