Rules proposal: one describe per file

[alecxe]

The rationale and the use case we have is described here Enforce one describe per file.

To summarize - the rule should produce a warning if there is more than one top-level describe per file.

Probably, we have too narrow of a use case - feel free to close if you feel there is no need for this kind of rule. Or, may be we can just turn it off by default.

Thanks!

[lo1tuma]

Hi @alecxe, thanks for the suggestion. I like the idea and would probably use such a rule as I’m already restrict my test files to only have one top-level describe 😉 .

Just for completeness: there are of course some limitations to static analysis in JavaScript where not all top-level describes can be detected. For example when someone creates test suites dynamically:

function createTestCases(name) {
    describe(name, function () {
        // tests ...
    });
}

createTestCases('foo');
createTestCases('bar');

[jfmengels]

FYI, this is kind of similar to #83.

[lo1tuma]

@jfmengels Good hint. I guess this rule together with a no-nested-describes rule would give you the behavior that you can only use one describe per file.

[jfmengels]

Ah, good point. Fine by me then 👍