Implement BDD interface and nested fixtures

describe('Utils', () => {
  describe('compose', () => {
    it('composes from right to left', () => {
         ...
    });
  });
});

[gilmeir-curv]

Adding to what @inikulin reported, take for example jest, which lets you nest multiple describe sections, including each section’s hooks. See my comment here.

[chikunov]

Sure,

lets say that i have a page with a form that could be in 2 different modes: read-only and editing. As name suggests, you should switch to the edit mode before you can change any values in the form. Rendering for those is different too. I would like to have something like the following:

fixture `MyPage`
    .page `http://mypage.com`;

section
    .before(async t => {
        await t.scrollTo(form);
    })
    ('Form', async t => {
        section
            .before(() => {
                await form.switchToReadOnlyMode();
            })
            ('Read-only mode', () => {
                test();
                test();
            });

        section
            .before(() => {
                await form.switchToEditMode();
            })
            ('Edit mode', () => {
                test();
                test();
            });
    });

section("Something unrelated to form on the same page", () => {})

This allows to group tests together and have a single setup point for a group. Furthermore, it allows to apply some metadata to sections and use it in reporting afterwards

section('Some page area', () => {
  section.metadata('browser', 'chrome')("chrome tests", t => {
     test(); 
  });

  section.metadata('browser', 'firefox')("firefox tests", t => {
     test(); 
  });
})

It is possible to replicate similar behavior by moving those preparations into a separate function and calling them in every test, setting up metadata on every test etc. But this leads to a lot of duplication in code.