There are no results in report when before hook fails and next block is describe() not it()

Describe the bug The following code cause the issue

describe('one', () => {
	before(() => {
		expect(true).to.equal(false); // when before hook fails and the next block is describe
	});

	describe('second', () => {
		before(() => {
			expect(true).to.equal(true);
			cy.log('gg');
		});
		it('should log 2', () => {
			cy.log('log 2');
		});
	});
});

There is only container.json file in allure-results and no attachments

However when before hooks fails and the next block is it() it just works fine

describe('one', () => {
	before(() => {
		expect(true).to.equal(true); // pass
	});

	describe('second', () => {
		before(() => {
			expect(true).to.equal(false); // fails but there are results in report
			cy.log('gg');
		});
		it('should log 2', () => {
			cy.log('log 2');
		});
	});
});

Now allure-results folder contains result.json, container.json and attachments

Environment (please complete the following information):

• Cypress version: 8.6.0
• cypress allure plugin: 2.23.0

[romankhomitskyi]

Ok, thanks for replies and fix!!

[Shelex]

I would like to have these structure instead of splitting these describes into two specs

However that is exactly the core recommendation for designing tests - isolation 😃. Here you have admin and user functionality combined together. But it would be much easy to maintain, read and support when separated:

describe('User rent', () => {
    before(() => {
        // actions done via backend
        // create admin and user
    });

    beforeEach(() => {
        // create rent with value 100$ and share with user
        // login as user an accept rent
    });

    afterEach(() => {
        // remove rent
    });

    after(() => {
        // delete user
        // delete admin
    });

    it('should be able to display actual rent value', () => {
        expect(rent).to.be.eq(100);
    });

    it('should be able to display decreased rent value', () => {
        // via admin api decrease rent to 20
        expect(rent).to.be.eq(20);
    });

    it('should be able to display increased rent value', () => {
        // via admin api increase rent to 50
        expect(rent).to.be.eq(50);
    });
});

describe('Admin rent', () => {
    before(() => {
        // create admin
    });

    beforeEach(() => {
        // create rent with value 100
    });

    afterEach(() => {
        // remove rent
    });

    after(() => {
        // delete admin
    });

    it('should contain initial rent value', () => {
        expect(rent).to.be.eq(100);
    });

    it('should be able to decrease rent value', () => {
        // decrease rent to 20
        expect(rent).to.be.eq(20);
    });

    it('should be able to increase rent value', () => {
        // increase rent to 50
        expect(rent).to.be.eq(50);
    });
});

Moreover, it seems like functionality that should be covered with unit tests (or at least integration/component), instead of Cypress and e2e level.