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
Our current system tests include authentication, but to further enhance test coverage and reliability, we need to replicate the existing authentication infrastructure in a controlled environment. This will give us more confidence in the system’s performance and behavior before deploying to production.
Requirements:
Implement a mock authentication service that replicates the current authentication configuration (realms, clients, roles, etc.).
The mock service should be flexible to ensure it can be run both locally and in CI pipelines.
Ensure system tests authenticate against this mock service in the same way they would against production infrastructure.
Long-term, this solution should be easily integrated into our GitHub CI pipeline.
The ultimate goal is to have this authentication mock service as part of our GitHub CI pipeline, allowing us to automatically run system tests with authentication in a consistent and isolated environment during every build.
This will help streamline the development process, catch potential issues earlier, and increase confidence that the system behaves as expected across different environments.
Acceptance Criteria:
A mock authentication service is available for local development and CI.
System tests are updated to authenticate against this mock service.
All system tests pass when using the mock service.
Documentation on how to run tests with the mock authentication setup(if any ,Can be part of devcontainer?)
Should be able to run on Github CI
The text was updated successfully, but these errors were encountered:
Description:
Our current system tests include authentication, but to further enhance test coverage and reliability, we need to replicate the existing authentication infrastructure in a controlled environment. This will give us more confidence in the system’s performance and behavior before deploying to production.
Requirements:
Implement a mock authentication service that replicates the current authentication configuration (realms, clients, roles, etc.).
The mock service should be flexible to ensure it can be run both locally and in CI pipelines.
Ensure system tests authenticate against this mock service in the same way they would against production infrastructure.
Long-term, this solution should be easily integrated into our GitHub CI pipeline.
Long-Term Vision #630:
The ultimate goal is to have this authentication mock service as part of our GitHub CI pipeline, allowing us to automatically run system tests with authentication in a consistent and isolated environment during every build.
This will help streamline the development process, catch potential issues earlier, and increase confidence that the system behaves as expected across different environments.
Acceptance Criteria:
A mock authentication service is available for local development and CI.
System tests are updated to authenticate against this mock service.
All system tests pass when using the mock service.
Documentation on how to run tests with the mock authentication setup(if any ,Can be part of devcontainer?)
Should be able to run on Github CI
The text was updated successfully, but these errors were encountered: