Skip to main content

Your submission was sent successfully! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates from Canonical and upcoming events where you can meet our team.Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

Charm Testing reference

:information_source: Hint: Use Juju 3. (Charmed MongoDB dropped support for juju 2.9)

There are a lot of test types available and most of them are well applicable for Charmed MongoDB. Here is a list prepared by Canonical:

  • Unit tests
  • Integration tests
  • Performance tests

Unit tests:

Please check the “Contributing” guide and follow tox run -e unit examples there.

Integration tests:

The integration tests coverage is rather rich in the MongoDB charm. Please check the “Contributing” guide and follow tox run -e integration examples there.

For tests related to complex features, and HA (High Availability) - each test serves as an integration as well as a smoke test with continuous writes routines being perpetually ran in parallel of whatever operation the test is involved in. These continuous writes ensure the availability of the service under different conditions.

Those tests make use of the following fixture:

  • continuous_writes: creates a replicated collection and continuously stores data into it.

After each test completes, the collection gets deleted.

Performance test

Refer to the charmed MongoDB K8s benchmark guide for charmed Charmed MongoDB.

Last updated 7 months ago. Help improve this document in the forum.