Skip to content

Add acceptance tests and schemathesis tests poc

Paulo Oliveira requested to merge feature/acceptance-testing-schemathesis into master

Merge Request Template

Description:

Added acceptance tests folder, with a copy of integration tests from catalog_test_core v2/v3. Added bash scripts to run v2/v3 tests Added schemathesis tests for api v2/v3 that generates and executes tests based on the schema (openapi) Added bash scripts to run schemathesis tests

Type of change

  • Initial commit (a change for the initial development of a project)
  • Refactor (a non-breaking change that improves code maintainability).
  • Bugfix (a non-breaking change that solves an issue).
  • Dependencies upgrade (a version change upgrade for release management)
  • Enhancement (a change on the existing code, increasing the efficiency or effectiveness of the software without necessarily introducing new features to end user, can include approved ADR)
  • New feature (a non-breaking change that adds functionality, must include approved ADR).
  • Breaking change (a change that is not backward-compatible and/or changes current functionality, must include approved ADR).
  • Deprecation (a change for code deprecation, will need to include this in the release notes)
  • DevOps (a change for CICD related / DevOps for release management)
  • Documentation (a change of documention only)
  • Logging (a change for work related to internal audit, logging, reporting improvement)
  • FOSSA Notice (a change for FOSSA notice update)
  • Revert (a change for reverting a previous MR)
  • Testing (a changes for improving unit, integration, etc. testing)

Please provide link to gitlab issue or ADR(Architecture Decision Record) Link

Does this introduce a change in the common core logic?

  • [NO]

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Azure
  • GCP
  • IBM

Have you applied the labels accordingly?

Merge request

Label Description
MRTesting Platform Standardization A labeling strategy for defect that has been resolved after related MR(s) are merged

What is the current behavior?

What is the new/expected behavior?

Have you added/updated Unit Tests and Integration Tests?

Added acceptance tests based on existing integration tests. Added schemathesis acceptance tests for schema validation.

Any other useful information

Dev Checklist:

  • Added Unit Tests, wherever applicable.
  • Updated the Readme, if applicable.
  • Existing Tests pass
  • Verified functionality locally
  • Self Reviewed my code for formatting and complex business logic.

Merge request reports