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
Is your feature request related to a problem? Please describe.
Currently, I am working with a scenario, where I need to login to my system with a specific test user. This is fine and dandy, when I specify the app specifics in the credentials.json file.
However, if I want to run my tests with various different credentials (also to be able to run the tests in isolation). I do not seem to be able to do so.
Describe the solution you'd like
The solution I can imagine, is that when using the runCommand, that I was able to provide a partial override of the this.cliConfiguration content - meaning that I can run multiple tests, with various different configurations.
Describe alternatives you've considered
one solution I found, was that I can use the dotenv package and a .env file to load in some test specific process.env properties - followed by writing custom code that picks the environment variables over the cli configuration, when present.
This kinda muddies the code more than I'd like, but it is a solution.
Additional context
We are trying to write e2e tests for our CLI, and this is why we would prefer not having to mock critical parts of the test
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, I am working with a scenario, where I need to login to my system with a specific test user. This is fine and dandy, when I specify the app specifics in the
credentials.json
file.However, if I want to run my tests with various different credentials (also to be able to run the tests in isolation). I do not seem to be able to do so.
Describe the solution you'd like
The solution I can imagine, is that when using the
runCommand
, that I was able to provide a partial override of thethis.cliConfiguration
content - meaning that I can run multiple tests, with various different configurations.Describe alternatives you've considered
one solution I found, was that I can use the
dotenv
package and a.env
file to load in some test specificprocess.env
properties - followed by writing custom code that picks the environment variables over the cli configuration, when present.This kinda muddies the code more than I'd like, but it is a solution.
Additional context
We are trying to write e2e tests for our CLI, and this is why we would prefer not having to mock critical parts of the test
The text was updated successfully, but these errors were encountered: