Feature Request: Throw error if first argument to "it" or "test" is not a string

Coming from ava, you don’t need test descriptions.

The following would work.

test(() => {
    jest.mock('../config', () => () => {
      return { protocol: 'http', host: 'localhost', port: '9999', pathPrefix: '' }
    })
    const config = require('../config')()
    expect(config.api.port).toBe('9999');
}) 

However, this doesn’t do anything in jest.

Can we throw an error if there is no function as the second argument? Or if a string is not passed into the first?

[mike-robertson]

Can we throw an error if there is no function as the second argument? Or if a string is not passed into the first?

Is it possible to not do this behavior, or at the very least, put the ability to toggle it off?

Maybe my use case isn’t common, but I find myself writing out a bunch of test cases first, then I begin implementing them. Getting an error thrown in that scenario clutters up the terminal with errors about “Missing second argument. It must be a callback function”.

Thanks!

[elyobo]

Ditto what @mike-robertson said; the missing second function is (was) a deliberate feature to allow skipped tests and I use it in exactly the way that he describes, writing out test cases to be written as I think about it and filling them in later. It seems that #5558 should have checked that the first arg was a string rather than checking that two args were passed…