-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[registry-operator]: end-to-end testing framework #6
Comments
I've done some initial investigation and I really enjoy Also, dependency management with Poetry is frictionless. It also easily integrates with linting tools, providing single file for configuration management for many, e.g. mypy, black, isort.
|
I'd like to use |
+1 for |
# Proposed Architectural Decision Record (mADR) ## Checklist - [x] The context and problem statement are clearly articulated. - [x] The considered options are listed with relevant links or references. - [x] The chosen option is clearly stated along with the rationale. - [x] The mADR template is filled out accurately. - [x] Any additional information or references are included. <!-- Link to the discussion --> Closes #6 Signed-off-by: Mateusz Urbanek <mateusz.urbanek.98@gmail.com>
Reopening. One more option worth considering:
|
Context and Problem Statement
Ensuring the reliability and functionality of the registry-operator is essential to maintain a seamless experience for developers and DevOps teams utilizing CNCF Distribution Registry instances. End-to-end testing plays a critical role in validating the deployment, scaling, and management capabilities of the registry-operator across various scenarios.
The selection of an appropriate end-to-end testing framework is paramount to establish robust testing standards and practices. Factors such as adherence to language idioms, support for testing complex workflows, community adoption, and extensibility are crucial considerations in this decision-making process.
Considered Options
Radish (Python)
pytest-bdd (Python)
behave (Python)
Ginkgo and Gomega (Go)
testing (Go)
The text was updated successfully, but these errors were encountered: