Jasmine Cookbook

Very often, we reuse pieces of code across different scenarios. This is due to functionality dependencies among scenarios, preconditions, or some other requirements such as initialization/declaration of application/system variables or objects. This improves code redundancy and maintainability.

Generally, to avoid code duplication (across scenarios/Jasmine specs) and increase code reusability and readability, we use setup and teardown functions. Jasmine provides two global functions (that is, beforeEach and afterEach) corresponding to setup and teardown functions. We can initialize variables and write common code and preconditions under the beforeEach function. Similarly, the afterEach function can be used to reinitialize variables or reset preconditions. The beforeEach function is called once before each spec is run in the describe block, and the afterEach function is called once after each spec is run. Both the functions are very useful for refactoring and optimizing the common code.

Getting ready

You will learn this recipe with the help of the second recipe in this chapter. For more information, refer to the Adding specs to your Jasmine test recipe. In this recipe, we implemented three scenarios for a sales and inventory control system and created a spec file (InventoryStock_spec.js) with the test code.

How to do it…

To apply Setup and Teardown to the Jasmine test, you need to perform the following steps:

First, you need to create a spec file (InventoryStockOptimizeCode_spec.js) under the /spec folder and get the following code from the spec file (InventoryStock_spec.js) created in the second recipe of this chapter, Adding specs to your Jasmine test:

describe("Inventory Stock", function() {
  //Scenario - 1
  it("Inventory Stock should be updated on sale of item", function() {
        var stockinhand_item1=11;
        var item1 = 1;
      var transaction = "SALE";
      expect(stockinhand_item1-item1).toEqual(10);
    });
    it("Inventory Stock should be updated on issue of an item within organization", function() {
        var stockinhand_item1=11;
        var item1 = 1;
      var transaction = "ISSUE";
      expect(stockinhand_item1-item1).toEqual(10);
    });

    //Scenario - 2
    it("Inventory Stock should be updated on return of any item", function() {
        var stockinhand_item1=11;
        var item1 = 1;
      var transaction = "SALE RETURN";
      expect(stockinhand_item1+item1).toEqual(12);
    });

    //Scenario - 3
    it("Inventory Stock should be updated on receiving or procuring new item", function() {
        var stockinhand_item1=11;
        var item1 = 1;
      var transaction = "PROCUREMENT";
      expect(stockinhand_item1+item1).toEqual(12);
    });
});

In the preceding code snapshot, notice the code redundancy across the specs. Here, we declared and assigned value to variables in each spec separately.

Next, refactor the code by applying the beforeEach and afterEach function by using the following code:

describe("Inventory Stock", function() {
  var stockinhand_item1, item1;
  beforeEach(function() {
      stockinhand_item1=11, item1 = 1;
    console.log("beforeEach: Stock in hand for item1 before spec execution = " + stockinhand_item1);
    });
  afterEach(function() {
      stockinhand_item1=0, item1 = 0;
    console.log("afterEach: Stock in hand for item1 once spec executed = " + stockinhand_item1);
    });

  //Scenario - 1
  it("Inventory Stock should be updated on sale of an item", function() {    
      expect(stockinhand_item1-item1).toEqual(10);
    });
    it("Inventory Stock should be updated on issue of an item within organization", function() {
        expect(stockinhand_item1-item1).toEqual(10);
    });

    //Scenario - 2
    it("Inventory Stock should be updated on return of an item", function() {
        expect(stockinhand_item1+item1).toEqual(12);
    });

    //Scenario - 3
    it("Inventory Stock should be updated on receiving or procuring new item", function() {
        expect(stockinhand_item1+item1).toEqual(12);
    });
});

In the preceding code snapshot, notice that we declared the common variables and assigned the corresponding values in the beforeEach function. Here, we have written the code just for illustrative purpose and to understand the working of beforeEach and afterEach function.

Finally, run the spec file (InventoryStockOptimizeCode_spec.js) using the Jasmine runner (that is, SpecRunner.html). You will see test execution results, as shown in the following screenshot, which indicates that all four specs are passing:
In your browser, if you go to the console window, you will see that the message defined with the console.log() method is printed four times, corresponding to each spec.

How it works...

In steps 1 to 3, we looked at how setup/teardown functions are applied to Jasmine tests using the beforeEach and afterEach functions. In step 2, we declared both the variables (stockinhand_item1 and item1) at the top-level scope, that is, the describe block. Here, we refactored the test code by moving the initialization code into a beforeEach function. Also, we reinitialized the value of variables using the afterEach function.

Jasmine Cookbook

By : Munish Kumar

Jasmine Cookbook

By: Munish Kumar

Overview of this book

Related Content you might be interested in

Current Title:

Jasmine Cookbook

Applying setup and teardown functions to the Jasmine test

Getting ready

How to do it…

How it works...