Rule proposal: no same level suites and tests

[fleg]

Bad

describe('root', function() {
    it('a', function() {});
    it('b', function() {});
    describe('bar', function() {
        it('x', function() {});
        it('y', function() {});
    });
});

Good

describe('root', function() {
    describe('foo', function() {
        it('a', function() {});
        it('b', function() {});
    });

    describe('bar', function() {
        it('x', function() {});
        it('y', function() {});
    });
});

[lo1tuma]

@fleg What would be the rationale for such a rule? Is it purely stylistic or are there any problems with having suites and tests at the same level?

[fleg]

stylistic I guess

[fleg]

actually mocha do not preserve order for same level suites and tests

describe('root', function() {
    it('a', function() {});
    it('b', function() {});
    describe('bar', function() {
        it('x', function() {});
        it('y', function() {});
    });
    it('q', function() {});
    it('w', function() {});
});

  root
    ✓ a
    ✓ b
    ✓ q
    ✓ w
    bar
      ✓ x
      ✓ y


  6 passing (16ms)

[lo1tuma]

Regarding the order of the output of mochas spec reporter, there is already #35 which is a proposal to enforce the same order in the test code.

Anyway I would be ok with I rule that forbids to have tests at the same level as suite. The only thing I wonder if this should be a separate rule than the one suggested in #35 or if they have enough things in common that it could be one generic rule?

[fleg]

I think it could be one rule with option to forbid same level tests/suites