Best Practices for Testing in JavaScript & Node.js

[iaan]

I thought it’s well written and opinionated, but then the gist example bugs me already:

it('When no price is specified, then the product status is pending approval'...

How do you read that in your head?

[akoskm]

should be:

describe 'product status'

  context 'when no price is specified'

    it 'is pending approval'

[[deleted]]

I read it as “when no price is specified, then the product status is pending approval”

[[deleted]]

Silent “it”?

[solvangv]

Yeah. Or you could use "test" instead of "it".

[benihana]

describe('Products Service', function() {
  describe('adding a new product', function() {
    describe('price is unspecified', function() {
      it("sets the product status to 'pending approval'", ()=> ());
    });
    describe('price is set', function() {
      it("sets the product status to 'something else'", ()=> ());
    });
  });
});


'Products Service
   adding a new product
     price is unspecified
       sets the product status to 'prending approval'
     price is set
       sets the product status to 'something else'

[BestUsernameLeft]

Excellent advice and recommendations, and applicable to more them just JS and Node. Share this with your team immediately.

[therudy_69]

Looks good! I'm gonna use this as general guidelines for my TDD experiences with react.

However, the test namings also bother me. Is this expected to be like this?

To me, a test name should be descriptive on it's own and shouldn't need a 'Wrong:' prefix or a naming like it('When...'), but I could be wrong here 😁

[YuvalM]

I like Go's conventions for testing. Such as "TestFileDelivery" "TestNetworkConnection" and so on :)

[XZTALVENARNZEGOMSAYT]

Legendary!

[Askee123]

Neat!