1
0
mirror of https://github.com/Unleash/unleash.git synced 2024-12-28 00:06:53 +01:00
unleash.unleash/frontend/cypress/integration/segments/segments.spec.ts
Thomas Heartman b5de65bb8e
chore: wait to input the name of the segment when checking for error messages (#7377)
This change adds a wait statement before entering the name of the
segment when checking for error messages that this segment name
already exists.

This is the same workaround that we did in
https://github.com/Unleash/unleash/pull/7289, which seems to have
worked.

Like in that PR, using waits is still an antipattern, but it appears
to be working.

Maybe it’s time to look more deeply at why it happens? Why isn’t the
field ready to receive input even though it’s on the page? Is it mui’s
fault or ours?
2024-06-12 14:06:44 +02:00

40 lines
1.2 KiB
TypeScript

///<reference path="../../global.d.ts" />
describe('segments', () => {
const randomId = String(Math.random()).split('.')[1];
const segmentName = `unleash-e2e-${randomId}`;
let segmentId: string;
before(() => {
cy.runBefore();
});
beforeEach(() => {
cy.login_UI();
cy.visit('/segments');
if (document.querySelector("[data-testid='CLOSE_SPLASH']")) {
cy.get("[data-testid='CLOSE_SPLASH']").click();
}
});
it('can create a segment', () => {
cy.createSegment_UI(segmentName);
cy.contains(segmentName);
});
it('gives an error if a segment exists with the same name', () => {
cy.get("[data-testid='NAVIGATE_TO_CREATE_SEGMENT']").click();
cy.wait(500);
cy.get("[data-testid='SEGMENT_NAME_ID']").type(segmentName);
cy.get("[data-testid='SEGMENT_NEXT_BTN_ID']").should('be.disabled');
cy.get("[data-testid='INPUT_ERROR_TEXT']").contains(
'Segment name already exists',
);
});
it('can delete a segment', () => {
cy.deleteSegment_UI(segmentName, segmentId);
cy.contains(segmentName).should('not.exist');
});
});