ops-scenario, the unit testing framework for ops charms
ops-scenario is a Python library that provides state-transition testing for
Ops charms. These tests are higher level than
typical unit tests, but run at similar speeds and are the recommended approach
for testing charms within requiring a full Juju installation.
Test are written in the arrange/act/assert pattern, arranging an object representing the current Juju state, acting by emulating an event from Juju, and then asserting on the (simulated) output Juju state.
Writing tests
Here's a test that verifies that a unit is active after the start event, with a very minimal initial state:
from ops import testing
# 'src/charm.py' typically contains the charm class.
from charm import MyCharm
def test_start():
ctx = testing.Context(MyCharm)
state_in = testing.State()
state_out = ctx.run(ctx.on.start(), state_in)
assert state_out.unit_status == testing.ActiveStatus()
More comprehensive tests will include relations, containers, secrets, and other components in the input state, and assertions against both the output state and the context. The 'act' stage remains a simple single call, although additional arguments may be required for the event, such as the relation or container that triggered it. For example:
import pytest
from ops import testing
from charm import MyCharm
@pytest.mark.parametrize(
'leader',
[pytest.param(True, id='leader'), pytest.param(False, id='non-leader')],
)
def test_(leader: bool):
# Arrange:
ctx = testing.Context(MyCharm)
relation = testing.Relation('db', local_app_data={'hostname': 'example.com'})
peer_relation = testing.PeerRelation('peer')
container = testing.Container('workload', can_connect=True)
relation_secret = testing.Secret({'certificate': 'xxxxxxxx'})
user_secret = testing.Secret({'username': 'admin', 'password': 'xxxxxxxx'})
config = {'port': 8443, 'admin-credentials': 'secret:1234'}
state_in = testing.State(
leader=leader,
config=config,
relations={relation, peer_relation},
containers={container},
secrets={relation_secret, user_secret},
unit_status=testing.BlockedStatus(),
workload_version='1.0.1',
)
# Act:
state_out = ctx.run(ctx.on.relation_changed(relation), state_in)
# Assert:
assert testing.JujuLogLine(level='INFO', message='Distributing secret.') in ctx.juju_log
peer_relation_out = state_out.get_relation(peer_relation.id)
assert peer_relation_out.peers_data[0] == {'secret_id': relation_secret.id}
You don't have to use pytest for your charm tests, but it's what we recommend.
pytest's assert-based approach is a straightforward way to write tests, and
its fixtures are helpful for structuring setup and teardown.
Installation
For charm tests, install the testing framework by adding the testing extra of
ops in your unit testing environment. For example, in pyproject.toml:
[dependency-groups]
test = ['ops[testing]<4.0']
Ops checks if ops-scenario is installed, and, if so, makes the classes
(such as Context, State, and Relation) available in the ops.testing
namespace. Use from ops import testing rather than importing the scenario
package.
ops-scenario supports the same platforms and Python versions as ops itself.
Documentation
- To get started, work through our 'Write your first Kubernetes charm' tutorial, following the instructions for adding unit tests at the end of each chapter.
- When you need to write a test that involves specific ops functionality, refer to our how-to guides which all conclude with examples of tests of the ops functionality.
- Use our extensive reference documentation when you need to know how each
testingobject works. These docs are also available via the standard Pythonhelp()functionality and in your IDE.
Community
ops-scenario is a member of the Charming family. It's an open source project
that warmly welcomes community contributions, suggestions, fixes and
constructive feedback.
- Read our code of conduct: As a community we adhere to the Ubuntu code of conduct.
- Get support: Discourse is the go-to forum for all Ops-related discussions, including around testing.
- Join our online chat: Meet us in the #charmhub-charmdev channel on Matrix.
- Report bugs: We want to know about the problems so we can fix them.
- Contribute docs: Get started on GitHub.
Contributing and developing
Anyone can contribute to ops and ops-scenario. It's best to start by
opening an issue with a clear
description of the problem or feature request, but you can also
open a pull request directly.
Read our guide for more details on how to work on and
contribute to ops-scenario.
Currently, releases of ops-scenario are done in lockstep with releases of ops
itself, with matching minor and bugfix release numbers. The ops documentation
outlines how to create a new release.
4 maintainers
Metadata
4 maintainers
Release files for ops-scenario 8.8.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ops_scenario-8.8.3.tar.gz | 86.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ops_scenario-8.8.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 161.9 kB
Release files / ops_scenario-8.8.3.tar.gz
| Download URL | ops_scenario-8.8.3.tar.gz |
|---|---|
| Size | 86.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eba556bd3b6266a76c0b5322e4b6ff63e991917148f2d26ba11dfc6c8dfbb6a0
|
|
BLAKE2b-256 checksum How to use checksums |
beebc67e55e1ae02cf21f1e59fe73352eab3bf0ea25750dcecdff785c4d4c78f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / ops_scenario-8.8.3-py3-none-any.whl
| Download URL | ops_scenario-8.8.3-py3-none-any.whl |
|---|---|
| Size | 74.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
83ab347c4b3c28de0d3c1e37ff71260cc621746101c2e6603b6a7fb2d3468ad2
|
|
BLAKE2b-256 checksum How to use checksums |
3eaa5c3aa073ed68c885acd6a94378b5435bfac9de05a02c848e8e05bad2813b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency log
