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
Given that we'll be creating a system to manage our data on a day-to-day basis it's critical that we have a system to reliably test whether a given state of airtigrs will work as expected. It may make sense to take on the following development workflow:
DEV
Local testing using docker-compose Airtigrs Docker-compose
Can create and teardown development environment + services on the fly for rapid testing of new features
Issues to figure out:
Providing endpoints for external services (i.e SFTP, external XNAT) when running. For tests we can mock services quite easily however when running integration tests within the development environment how do we set this up...?
Staging:
Production-mirror environment (possibly dev branch of main repository) that contains all PRs from developers. This environment should test the cumulative state of the repository using a copy of real subset of production data (i.e pick a study or two)
Production:
Production environment (main branch) that is only pushed to when Staging build runs as expected
The text was updated successfully, but these errors were encountered:
Given that we'll be creating a system to manage our data on a day-to-day basis it's critical that we have a system to reliably test whether a given state of airtigrs will work as expected. It may make sense to take on the following development workflow:
DEV
Local testing using docker-compose Airtigrs Docker-compose
Can create and teardown development environment + services on the fly for rapid testing of new features
Issues to figure out:
Providing endpoints for external services (i.e SFTP, external XNAT) when running. For tests we can mock services quite easily however when running integration tests within the development environment how do we set this up...?
Staging:
Production-mirror environment (possibly dev branch of main repository) that contains all PRs from developers. This environment should test the cumulative state of the repository using a copy of real subset of production data (i.e pick a study or two)
Production:
Production environment (main branch) that is only pushed to when Staging build runs as expected
The text was updated successfully, but these errors were encountered: