classroomtechtools/utgs

Unit Testing for Google Appscripts

utgs's Issues

Improve tests for throwing errors

Currently the api only allows to test that a function throws an error if a particular type.

Due to limitations in AppsScripts, the test can fail even though an error is actually thrown, since the isinstance test fails. An error objected created in the utgs library won't be an instance of an error object in the main project.

Also, error messages should also be exposed via the api, so a test can be do based on the message.

`assert.throwsError` not recognizing thrown error

When testing that a constructor throws an error, the test fails with the message, No error was thrown, expecting error of type 'Error'. Checking err instanceof Error returns true in the console during function execution.

class MyClass {
  constructor(url) {
    let notAllowed = "api/v1";

    if(url.includes(notAllowed)) {
      let error = new Error('You can't do that');
      console.log(error instanceof Error) // => true
      throw error;
    }
  }
}

// Throws an Error in the console
function simple_test() {
  new MyClass("https://www.example.com/api/v1")
}


// Fails the unit test with "No error was thrown, expecting error of type 'Error'"
function utgsTest() {
  const { describe, it, assert } = Utgs.module()
  describe('A unit test', function() {
    it('will fail with a bad structure', function() {
      assert.throwsError("api/v1 in the URL", function() {
        new MyClass("https://www.example.com/api/v1")
      })
    })
  })
}