Skip to content

chore: migrate integration tests to jubilant#194

Draft
seb4stien wants to merge 2 commits intomainfrom
chore/migrate-integration-tests-to-jubilant
Draft

chore: migrate integration tests to jubilant#194
seb4stien wants to merge 2 commits intomainfrom
chore/migrate-integration-tests-to-jubilant

Conversation

@seb4stien
Copy link
Contributor

Overview

This PR migrates the integration tests from pytest-operator to jubilant~=1.7, following the latest integration test standards.

Changes

  • Replace pytest-operator with jubilant~=1.7 in integration tests
  • Update fixtures to use jubilant's Juju interface instead of OpsTest
  • Migrate all async test functions to sync functions
  • Add renovate configuration for charmhub revisions tracking
  • Update tox.ini to use jubilant for integration tests
  • Add pytest options for model reuse (--model, --use-existing, --keep-models)

Testing

Linting passes successfully. Integration tests will be run by CI.

- Replace pytest-operator with jubilant~=1.7 in integration tests
- Update fixtures to use jubilant's Juju interface instead of OpsTest
- Migrate all async test functions to sync functions
- Add renovate configuration for charmhub revisions tracking
- Update tox.ini to use jubilant for integration tests
- Add pytest options for model reuse (--model, --use-existing, --keep-models)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The @pytest.mark.abort_on_fail marker was specific to pytest-operator
and is not supported in standard pytest or jubilant.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@seb4stien
Copy link
Contributor Author

Fixed Issue

Removed the @pytest.mark.abort_on_fail marker which was causing a warning. This marker was specific to pytest-operator and is not supported in standard pytest or jubilant.

The tests should now run without warnings in CI.

@github-actions
Copy link
Contributor

Unused entries in .trivyignore

Image: ghcr.io/canonical/hockeypuck:3c3175ed54ebf929a6e623ead51f15cc912bea4c-_0.2_amd64

The following CVEs are in .trivyignore but not ignored by Trivy anymore:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant