mirror of
https://github.com/Unleash/unleash.git
synced 2024-10-28 19:06:12 +01:00
b5de65bb8e
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? |
||
---|---|---|
.. | ||
fixtures | ||
integration | ||
oss/feature | ||
support | ||
global.d.ts | ||
README.md | ||
tsconfig.json |
Unleash Behavioural tests
Add common commands to Cypress
global.d.ts
is where we extend Cypress typesAPI.ts
contains api requests for common actions (great place for cleanup actions)UI.ts
contains common functions for UI operationscommands.ts
is the place to map the functions to a cypress command
Test Format
Ideally each test should manage its own data.
Avoid using after
and afterEach
hooks for cleaning up. According to Cypress docs, there is no guarantee that the functions will run
Suggested Format:
prepare
when
then
clean
Passing (returned) parameters around
it('can add, update and delete a gradual rollout strategy to the development environment', async () => {
cy.addFlexibleRolloutStrategyToFeature_UI({
featureToggleName,
}).then(value => {
strategyId = value;
cy.updateFlexibleRolloutStrategy_UI(featureToggleName, strategyId).then(
() => cy.deleteFeatureStrategy_UI(featureToggleName, strategyId)
);
});
});