Description

Performing unit tests of your code is very important. At the same time, creating unit test scripts is quite tedious and there is usually not enough time for it.

This test script generator allows you to automatically generate files containing unit test scripts using minimal effort.

You can insert the generator configuration at the place of the actual function calls you want to test. The generator will use the real values as test parameters and match the unit tests to their type.

You can also use this generator to mock unit tests.

Currently, only the "jest" and "mocha" (with "chai") frameworks are supported.

Important!!! As of version 1.1.0, this project is compatible with ES6. If you have a problem with the configuration of your 'jest' test framework read the Problems section.

Prerequisites

This library generates unit test scripts. These scripts will be used when running unit tests in your project. Remember to install and configure your favorite testing framework ("jest" or "mocha & chai") in your enviroment.

Installation

npm i unit-test-script-generator

Usage

Create a new generator file (similar to the demo.js file presented in the following section), and then edit this file according to the list below.

1. Import the library: import testGenerator from 'unit-test-script-generator'

2. Initialize the generator: const tg = new testGenerator.TestScriptGenerator(true, 'libToTest');

   parameters: generateFiles - false if the result file should not be generated. Sometimes you may not want to generate test scripts for certain libraries. Instead of removing them from the generator file, maybe set this parameter to false. moduleName - module where are located tested functions config - You can specify an optional configuration as the third parameter of the call: testScriptPath - path to the folder where the test scripts will be saved modulePath - path to the location where the module whose functions you will test is located testFramework - framework that supports unit tests (currently 'jest' and 'mocha', for 'mocha' you should also have chai installed). Optional configuration example: const tg = new testGenerator.TestScriptGenerator(true, 'libToTest', {testFramework: 'mocha', testScriptPath: './test/', modulePath: '../core/'}); You can simultaneously initialize multiple generators for different libraries, for example:

   const tg = new testGenerator.TestScriptGenerator(true, 'libToTest');
   const tg2 = new testGenerator.TestScriptGenerator(true, 'libToTest2');
   const tg3 = new testGenerator.TestScriptGenerator(true, 'libToTest3');
   
   tg.generateTestForFunc(libToTest.sumFunc, 1, 3);
   tg2.generateTestForFunc(libToTest.multiplyFunc, 1, 3);
   tg3.generateTestForFunc(libToTest.eqFunc, 2, 3);

   The above code will create 3 unit test files (as long as you have libraries: libToTest, libToTest2, libToTest3).

3. Call the function for which you want to generate a unit test: example typical function call libToTest.sumFunc(1, 3) replace with tg.generateTestForFunc(libToTest.sumFunc, 1, 3);

   Functions for asynchronous calls have also been prepared: generateTestForFuncAsyncResolve - for calls that terminate without error generateTestForFuncAsyncReject - for calls that end with an error

   example call: await tg.generateTestForFuncAsyncResolve(libToTest.sumFunc, 1, 3);

   Important: The functions that generate scripts (generateTestForFunc + Async) always return values like the original (tested) functions. This allows you to permanently define script generation, and if you don't need to generate scripts then set the 'generateFiles' parameter to false

4. Run js file with test generator node demo.cjs

   After running, you will get a new ....test.js file in the testScriptPath directory

Example

The demo.js file contains a sample call to the script generator that runs on the libToTest.js test library.

After running demo.js, a ./testScripts/libtotest..test.js file will be generated

Now you can run unit tests with the "jest" command.

demo.cjs

(async function () {
    const testGenerator = await import('unit-test-script-generator');//import('unit-test-script-generator');// or import('./index.js') for development
    const libToTest = await import('./libtoTest.js');

    console.log('START DEMO');
    const tg = new testGenerator.TestScriptGenerator(true, 'libToTest', { testFramework: 'mocha', testScriptsPath: './test/' });
    // const tg = new testGenerator.TestScriptGenerator(true, 'libToTest');
    tg.generateTestForFunc(libToTest.sumFunc, 1, 3);
    tg.generateTestForFunc(libToTest.multiplyFunc, 1, 3);
    tg.generateTestForFunc(libToTest.eqFunc, 2, 3);
    tg.generateTestForFunc(libToTest.eqFunc, 3, 3);
    tg.generateTestForFunc(libToTest.eqFunc, "string1", "string1");
    tg.generateTestForFunc(libToTest.eqFunc, { id: 1, name: "ala" }, { id: 1, name: "ala" });
    tg.generateTestForFunc(libToTest.eqFuncObj, { id: 1, name: "ala" }, { id: 2, name: "ela" });
    tg.generateTestForFuncAsyncResolve(libToTest.promiseResolveFunc, { id: 1, name: "ala" }, { id: 2, name: "ela" });
    tg.generateTestForFuncAsyncReject(libToTest.promiseRejectFunc, { id: 1, name: "ala" }, { id: 2, name: "ela" });
    console.log('FINISH DEMO');
})()

libToTest.js

const sumFunc = (a, b) => {
    return a + b;
}

const multiplyFunc = (a, b) => {
    return a * b;
}

const eqFunc = (a, b) => {
    return a === b;
}

const eqFuncObj = (a, b) => {
    return { result: a === b, name: 'eqFuncObj' };
}

const promiseResolveFunc = (a, b) => {
    return new Promise((resolve, reject) => {
        resolve('promiseResolveFunc')
    })
}

const promiseRejectFunc = (a, b) => {
    return new Promise((resolve, reject) => {
        reject('promiseRejectFunc')
    })
}

export default {
    sumFunc,
    multiplyFunc,
    eqFunc,
    eqFuncObj,
    promiseResolveFunc,
    promiseRejectFunc
}

export {
    sumFunc,
    multiplyFunc,
    eqFunc,
    eqFuncObj,
    promiseResolveFunc,
    promiseRejectFunc
}

Result (generated script) for JEST framework

/*
   Script generated automatically from the NPM unit-test-script-generator package.

   Package version: 1.1.0
   Test framework: jest
   Tested module: libToTest
   ES6: True
   Date of file generation: 11/15/2022, 12:06:49 PM
*/

// import "regenerator-runtime/runtime";
import libToTest from "../libToTest.js";

// describeID: r5g245np7
describe("Tests for module: libToTest", () => {
  test("test function sumFunc", () => {
    expect(libToTest.sumFunc(1, 3)).toBe(4);
  });

  test("test function multiplyFunc", () => {
    expect(libToTest.multiplyFunc(1, 3)).toBe(3);
  });

  test("test function eqFunc", () => {
    expect(libToTest.eqFunc(2, 3)).toBe(false);
  });

  test("test function eqFunc", () => {
    expect(libToTest.eqFunc(3, 3)).toBe(true);
  });

  test("test function eqFunc", () => {
    expect(libToTest.eqFunc("string1", "string1")).toBe(true);
  });

  const obj_0fwr05acy = {"id":1,"name":"ala"};
  const obj_o5br3gd8y = {"id":1,"name":"ala"};
  test("test function eqFunc", () => {
    expect(libToTest.eqFunc(obj_0fwr05acy, obj_o5br3gd8y)).toBe(false);
  });

  const obj_acf69da31 = {"id":1,"name":"ala"};
  const obj_y1oyjcttf = {"id":2,"name":"ela"};
  const resObject_b1tjhcg46 = {"result":false,"name":"eqFuncObj"};
  test("test function eqFuncObj", () => {
    expect(libToTest.eqFuncObj(obj_acf69da31, obj_y1oyjcttf)).toEqual(resObject_b1tjhcg46);
  });

  const obj_i5aercmgx = {"id":1,"name":"ala"};
  const obj_wkzdscv1x = {"id":2,"name":"ela"};
  const obj_7o9vye2u3 = {"id":1,"name":"ala"};
  const obj_2ish6ciq4 = {"id":2,"name":"ela"};
  test("async test function resolve promiseResolveFunc", async () => {
     await expect(libToTest.promiseResolveFunc(obj_i5aercmgx, obj_wkzdscv1x))
    .resolves.toBe("promiseResolveFunc");
  });

  test("async test function reject promiseRejectFunc", async () => {
    expect.assertions(1);
    return libToTest.promiseRejectFunc(obj_7o9vye2u3, obj_2ish6ciq4)
    .catch(e => expect(JSON.parse(JSON.stringify(e))).toBe("promiseRejectFunc"));
  });

});// describeID[r5g245np7]

Problems

This is the early version of the project and although it has been tested you are likely to encounter problems. Let me know if you encounter any problems other than those described below or have ideas for changes to the module (testscriptgenerator@).

Some of them are described here:

1. To force the 'jest' framework to operate under ES6 check out the documentation for the 'jest' framework or read this article: https://how-to.dev/how-to-set-up-jest-for-es-module
2. Sometimes you need to bind a function to a module e.g:

   const funcToCall = libToTest.sumFunc;
   const funcBinded = funcToCall.bind(libToTest);
   await tg.generateTestForFunc(funcBinded, 1, 3);

3. Sometimes you will have to make changes to your test scripts and supplement them with initialization of the libraries you use, for example. For example, if the library "yourLib" requires the init function to be called before running other functions, you will need to take care of this in your test scripts (check how to perform this correctly in your favorite testing framework). yourLib.init();

   and now test scripts test("test function sumFunc", () => { expect(yourLib.sumFunc(1, 3)).toBe(4); });

4. In functions that generate test cases (e.g. generateTestForFunc) do not pass cyclic object values in the parameters. The objects must be serializable by JSON.stringify

5. In case of problems, you can always manually modify the generated test scenarios. You can use them just as a template.

6. Make sure that the framework 'jest' looking for test scripts in the ./testScripts folder (or any other folder you set in the configuration)