JUnit VS Juju

Because I only wanna use the cmd java test, so I chose Junit4 which supports Plain-old JAR. I did test according to the Getting started document. But when I ran the javac -cp .:junit-4.XX.jar:hamcrest-core-1.3.jar CalculatorTest.java I got the error message CalculatorTest.java:4: error: package main does not exits. I tried to reorganize the folder and set Path according to others' experience 1, 2, but it still did not work.

Oops, another error. This is why we should read the manual 😅.

JUnit4

Delete those imports and remove the junit-jupiter-api dependency. Follow the instructions for JUnit 4.

Quite a lot of Java dependencies bring Junit 4 or Junit vintage engine as a transitive dependency.

The AHTest039.json file is the actual test. My testRunner() method (no relation to JUnit test runners) reads that JSON file, processes it, and asserts that the test passed. So my test class consists of a few Java methods, and what is essentially a list of JSON files to process.

Basically juju is used to deploy microservices, and other stuff too: https://juju.is/

Juju https://juju.is/

https://juju.is/

Each app is packaged in a charm which seems to be a yaml declaring inputs, dependencies and other meta data and optional python code that can respond to certain lifecycle hooks

https://discourse.charmhub.io/t/implementing-relations/1051

   name: my-node-app

I am currently working myself through setting up our new Research GPU-Cluster where we have "sort of" managed to deploy MAAS to manage all the servers more efficiently, and on top of MAAS then use Juju to deploy the further components of the cluster. The components here are

Kubernetes Custom Resources were created to allow the Kubernetes API to be extended for domain-specific logic, by defining new resource types and controllers. OSS frameworks like operator-sdk, kubebuilder and juju were created to simplify the creation of custom resources and their controllers. Tools built with these frameworks came to be known as Operators.

Depending on what you're trying to accomplish, Juju and MAAS, if not just automate with preseed for custom desktops.

At Canonical I work on two open-source projects written in Go: Juju, a large cloud-based application deployment tool, and Pebble, a small Linux service manager. Both include CLI clients and API-based server daemons. Juju in particular is a large distributed system.

The new Portainer charm allows users of Canonical’s Charmed Kubernetes distribution to automatically install and integrate Portainer Business as part of the Kubernetes cluster deployment process, using Juju, the Charmed Operator framework.