Proposal: Wrap all tests in a meaningful describe()

[Reinmar]

I've noticed that sometimes we wrap the whole test file with a meaningful describe() and sometimes we only call describe() for methods and properties. Wrapping has one major advantage – when running tests in Node.js it's clear what failed. When the test file isn't wrapped, you get some meaningless method/properties names and no context.

So, let's wrap all files. It does not need to be one describe(), because a test file may test multiple subjects, but the most outer describe() calls should always define the subject in a way that it's understandable within the project.

describe( 'Editor', () => {
    describe( 'constructor', () => {
    } );

    ...
} );

[scofalik]

+1

I've noticed the same in Tree Model when I started to work on it and I have changed multiple tests, but probably some of them are still unwrapped.

[szymonkups]

+1

[pjasiun]

:+1:

[Reinmar]

Documented: https://github.com/ckeditor/ckeditor5-design/wiki/Code-Style#tests