open-component-model / ocm-project

OCM Project Backlog
Apache License 2.0
0 stars 0 forks source link

Automated Testing for OCM CLI #103

Open robertwol opened 1 year ago

robertwol commented 1 year ago

User Story:

As a developer or contributor to the OCM project, I want to have automated testing in place to ensure the reliability and functionality of the OCM CLI and related components. This will help identify and fix issues early, improve code quality, and provide a robust user experience.

Epic link:

List of Potential Tasks

  1. Create end-to-end (E2E) tests for OCM commands and their common variants to cover different use cases.
  2. Develop a simple OCM GitHub action that verifies the basic functionality of the CLI without requiring sources, resources, or components.yaml.
  3. Implement test scenarios and scripts to cover 80% of the common use cases of OCM.
  4. Set up a testing framework (e.g., using a testing library or framework) for automated testing of OCM.
  5. Create test data and fixtures to simulate various scenarios and edge cases.
  6. Write unit tests for critical functions, modules, or libraries used in the OCM project.
  7. Integrate the automated tests into the project's continuous integration (CI) pipeline.
  8. Define a code coverage threshold and ensure that the tests meet or exceed the defined coverage percentage.
  9. Establish a process for regularly updating and maintaining the automated tests as new features and changes are introduced.

Definition of Done

Related issues:

Skarlso commented 2 months ago

What remains to be done here? The integration test thingy is running and working, isn't it?