Testing asynchronous features

If you have made the tests pass, you are probably thinking that you are done. But actually, you are not. The problem is that we have designed a synchronous API. This is not feasible in a JS application, because JS is single-threaded. Any I/O will cause our system to block, and we need to process the requests one at a time. This is not acceptable in a server or in a UI application. So, we need to change our design to use an asynchronous API, but how do we test an asynchronous API?

Testing a callback-based API

Instead of returning the value directly, we can change our API to use callbacks. The same thing applies to our DAO. After all, the DAO will perform IO, so it needs to be asynchronous. So, let's change our test. For this, we first need to change the setup and action:

context('Given that the order is empty', function () {
    var result;
    beforeEach(function (done) {
      this.orderId = 'some empty order id';
      this.orderDAO...

Tech Concepts

Programming languages

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Learning Behavior-driven development with Javascript

By : Enrique Javier A Rubio

Learning Behavior-driven development with Javascript

By: Enrique Javier A Rubio

Overview of this book

Testing asynchronous features

Testing a callback-based API

Learning Behavior-driven development with Javascript

By : Enrique Javier A Rubio

Learning Behavior-driven development with Javascript

By: Enrique Javier A Rubio

Overview of this book

Testing asynchronous features

Testing a callback-based API

Confirmation

Buy this book with your credits?

Submit Your Feedback

Create a Free Account To Continue Reading

Sign in to activate your 7-day free access