Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

stable

Clone or download

Read-only

Avoid assigning variables in cypress tests

Download Browse

Part of request #22559 Program management should be covered by end to end tests - Setting "now" for each test lets cypress retry succesfully, otherwise it tries to recreate a project and fails due to conflicting name. - Assigning return values to variables is an anti-pattern [0], we can use .then() to work on an element's value. How to test: - make tests_cypress should succeed [0] https://docs.cypress.io/guides/references/best-practices#Assigning-Return-Values Change-Id: I52fcea5c4a40ef6389fb80dc42cfb24367af7171

+22 −34
Joris MASSON (jmasson) 2021-08-05 09:56
Joris MASSON (jmasson) 2021-08-05 09:57
a0d209fa0cf72a2d099e66049b1d839e38e5cd63
23d95465340783120b15d9e00a13c01fb63489e4
git #tuleap/stable/a0d209fa0cf72a2d099e66049b1d839e38e5cd63

Modified Files

Side by side diff
Inline diff
Name
M plugins/program_management/tests/e2e/cypress/cypress/integration/program_management.spec.ts +22 −34 Go to diff View file