You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running nx commands, the nx graph needs to be built. To do this, nx navigates the folder structure looking for project.json/package.json to inspect and determine the graph.
Currently, the cypress.config.ts module contains code to check for which credentials to use during testing. If neither UESIO_DEV or UESIO_AUTOMATION_PASSWORD is found, it throws an error. This causes nx to fail on any nx command if it detects that the graph needs to be built and therefore UESIO_DEV or UESIO_AUTOMATION_PASSWORD must always be defined to use nx reliably.
Additionally, the check for whether or not UESIO_DEV has been set returns "truthy" even if the value of process.env.UESIO_DEV is something like false.
In short, the logic required to "run" the test should not interfere unless the tests are actually being run and even then, should only impact the test running itself.
The possible solutions to this are:
Move the check (adjusting it to properly detect if UESIO_DEV is truthy) inside the default export itself
Move the check (adjusting it to properly detect if UESIO_DEV is truthy) inside the setupNodeEvents option of cypress config so that it only runs upon initial test configuration during a run
Simply use mock if UESIO_AUTOMATION_PASSWORD is not truthy
The text was updated successfully, but these errors were encountered:
When running
nx
commands, the nx graph needs to be built. To do this, nx navigates the folder structure looking for project.json/package.json to inspect and determine the graph.Currently, the cypress.config.ts module contains code to check for which credentials to use during testing. If neither
UESIO_DEV
orUESIO_AUTOMATION_PASSWORD
is found, it throws an error. This causesnx
to fail on anynx
command if it detects that the graph needs to be built and thereforeUESIO_DEV
orUESIO_AUTOMATION_PASSWORD
must always be defined to use nx reliably.Additionally, the check for whether or not UESIO_DEV has been set returns "truthy" even if the value of
process.env.UESIO_DEV
is something likefalse
.In short, the logic required to "run" the test should not interfere unless the tests are actually being run and even then, should only impact the test running itself.
The possible solutions to this are:
UESIO_AUTOMATION_PASSWORD
is not truthyThe text was updated successfully, but these errors were encountered: