We are currently working with a public repository in order to allow the code base to be easily setup in the docker container via bootstrap.py.
Due to the public nature of the repository, and following best practices in general, none of the credentials for accessing an environment can be stored in the tests themselves. We need to determine the appropriate handling of these credentials, given that they may be different for whichever server_url is passed into the process execution. We may ultimately need a way to support multiple credentials of users with differing permission levels as well.
Currently we have an individual username/password combination that can be passed via Form to the process, but this has its limitations. We need to determine what is the appropriate long term solution for credentials, and what limitations we may need to enforce on the tests.
We are currently working with a public repository in order to allow the code base to be easily setup in the docker container via bootstrap.py.
Due to the public nature of the repository, and following best practices in general, none of the credentials for accessing an environment can be stored in the tests themselves. We need to determine the appropriate handling of these credentials, given that they may be different for whichever server_url is passed into the process execution. We may ultimately need a way to support multiple credentials of users with differing permission levels as well.
Currently we have an individual username/password combination that can be passed via Form to the process, but this has its limitations. We need to determine what is the appropriate long term solution for credentials, and what limitations we may need to enforce on the tests.