This is the code repository for snapd-testing-tools, the set of tools used by snapd for testing porpuses.

The tools in this project are designed and tested independently, making them easy to be imported and used by any project.

This is an open source project and we warmly welcome community contributions, suggestions, and constructive feedback. If you're interested in contributing, please take a look at our Code of Conduct first.

• to report an issue, please file a bug report on our Launchpad issue tracker
• for suggestions and constructive feedback, create a post on the Snapcraft forum

We're friendly! We have a community forum at https://forum.snapcraft.io where we discuss feature plans, development news, issues, updates and troubleshooting. You can chat in realtime with the snapd team and our wider community on the #snappy IRC channel on libera chat.

For news and updates, follow us on Twitter and on Facebook.

The tools included in this project are intended to be reused by other projects.

Tools are supported in all the systems included in spread.yaml file.

Read the following considerations before adding new tools:

• Each tool needs to be accompanied by at least 1 spread test in tests/<tool-name>/
• At least 1 spread test needs to be included in the tests directory for each tool
• If the tool is a shell script, it needs to first pass a ShellCheck assessment
• All tools need to be as generic as possible
• Each tool must also provide a command line interface (CLI), including help output

The utils included in this project are intended to be reused by other projects.

Utils are used as a complement for spread tests executions. Those are not intended to be used by spread tests. For example utils are used on github action workflows to analyze tests code and outputs.

Utils are supported in ubuntu-18.04 and higher.

Read the following considerations before adding new utils:

• Each util needs to be accompanied by at least 1 spread test in tests/<util-name>/
• At least 1 spread test needs to be included in the tests directory for each util
• If the util is a shell script, it needs to first pass a ShellCheck assessment
• All utils need to be as generic as possible
• Each util must also provide a command line interface (CLI), including help output

Service	Status
Github Actions