mawrkus / js-unit-testing-guide Goto Github PK

Now that the "📙 Resources" section has been splitted into different topics, it would be nice to populate it with more content. Blog posts, tutorials, videos, books, ... The idea is not to have an encyclopedia but to have a few (5 max. per topic?) high quality resources. Help, anyone?

Thanks for the excellent guide.

It is unclear to me whether the examples are using mocha or jasmine, as both of them use describe(). But I wanted to point out that mocha specifically discourages the use of arrow functions. https://mochajs.org/#arrow-functions

I think it would be helpful to make clear which framework/tooling the examples are using, and if they are indeed using mocha, they should perhaps use function() instead. Thanks.

If you take a look at this test case:

describe('A set of functionalities', () => {
  it('should do something nice', () => {
   expect(myVar).toBe(true);
  });
});

if this test fails, then your report will say something along the lines of:

expected undefined to be true

which doesn't mean anything.

Would be much nicer to use Jasmine Custom Messages. Where your tests would start to look like this:

describe('A set of functionalities', () => {
  it('should do something nice', () => {
   since('i have a boolean variable named myVar with a value of true')
      .expect(myVar).toBe(true);
  });
});

And your typical report would read on a failure:

A set of functionalities should do something nice I have a boolean I have a boolean variable named myVar with a value of true FAILED

Basically creating much more approachable error reports that mean something later in the future. And motivating the notion of creating meaningful tests.

What are your thoughts?

It would be nice to have the guide translated in the following languages:

• Chinese (a version from 2020 already exists)
• Spanish
• French
• Portuguese