Bud and Bloom can now run on Cloudron. If you already use Cloudron to host your tools, you can give test management and product traceability a place on the same server, with your own accounts, projects, and data.
The useful part of an evaluation begins when you bring in work you recognise: a requirement from your project, a test that checks it, and a result from your own test bench. This release makes it easier to get the applications running so you can try that workflow.
Two applications, two starting points
Bud TMP by EmbedLabs brings automated test runs, results, logs, and artifacts together. A test failure becomes easier to investigate when the evidence stays attached to the run and you can identify the Test Station that produced it. You can start with Bud if your immediate problem is keeping track of tests across developers, CI jobs, or hardware benches.
Bloom PLM by EmbedLabs manages requirements, controlled documents, verification, risks, changes, and defects. Trace links connect these records so you can follow a requirement through its related test cases. Start with Bloom if you want to understand what is covered, what still needs verification, and how a change relates to the rest of a project.
You can use either application independently. Connecting them lets Bud send execution outcomes to Bloom for identified test cases, bringing test evidence into the requirements workflow.
What changes with Cloudron
The Cloudron installation uses the same product images as other self-hosted installations. Cloudron supplies the database configuration and persistent storage; the application applies its database migrations at startup. After installation, open the app in your browser and create its first administrator account.
Tests still run on the machine or hardware bench where your test environment lives. Hosting Bud on Cloudron gives those runs somewhere to send their results. Installing the application does not run a test suite or populate a test history.
Try one complete verification workflow
Choose a small example from an existing project. In Bloom, create a requirement and a test case that verifies it, then link the two. Keep the scope small enough that you can inspect every relationship yourself.
In Bud, create an enrolment key for a Test Station and configure your runner using the setup instructions. Run your own tests and upload their results. Open the resulting run in Bud and inspect the outcome, logs, and any attached artifacts. This is the point to check whether the evidence you need for investigating a failure is actually present.
To connect the two apps, configure Bloom PLM Integration in Bud with a scoped integration credential and associate the uploaded test results with the corresponding Bloom test-case IDs. Run the example again and check its execution outcome in Bloom. That gives you a concrete path to evaluate: requirement, test case, execution, and result.
Install Bud and Bloom
The repository instructions cover the Cloudron manifest, product image, installation command, and first administrator setup. Follow the instructions for the application you want to try:
Install Bud on Cloudron · Install Bloom on Cloudron
Installation currently uses the repository instructions. Listings in the official Cloudron App Store and the Community Apps directory are not yet available.