Currently the Cypress tests for the Portal UI utilize the live running instance of Globus and an actual account to log a user in then proceeds with the rest of the tests. After discussion we want to instead rely on a series of fake tokens that will correspond to various use-cases (e.g. public/non-logged in access, user with a single group, user with multiple groups, data admin, data admin with no group write access, etc.)
Because we consistently ping the HuBMAP commons' AuthHelper (which makes token specific calls to Globus) we will need to
Spin up a modified version of the Ingest API that Cypress will hit instead
Modify hubmap-commonsAuthHelper instantiation to accept mocked Globus URLs (default to what currently is hardcoded)
Create a Mock Globus service to respond with group and access information associated with each fake token we create
Currently the Cypress tests for the Portal UI utilize the live running instance of Globus and an actual account to log a user in then proceeds with the rest of the tests. After discussion we want to instead rely on a series of fake tokens that will correspond to various use-cases (e.g. public/non-logged in access, user with a single group, user with multiple groups, data admin, data admin with no group write access, etc.)
Because we consistently ping the HuBMAP commons'
AuthHelper(which makes token specific calls to Globus) we will need tohubmap-commonsAuthHelperinstantiation to accept mocked Globus URLs (default to what currently is hardcoded)