Test roots cloning use cases

Problem to solve

We currently spend a considerable amount of time writing unit and funcional tests for our application.

A critical component that disrupts our service when it fails does not have any type of tests. That is roots cloning.

This:

1. Makes development speed considerably slower as there is no comfortable way to test if things work
2. Increases the chances of disrupting the service by breaking it
3. Makes developers afraid of touching it, which also creates the perfect environment for bad architectures due to low maintenance

Let's look for ways of comfortably testing this.

Intended users

Developers

Permissions and Security

N/A

Proposal

Look for ways of testing both cluster and batch roots cloning.

Test plan

N/A

Steps

• Make sure that the code contributions checklist has been followed.

What does success look like, and how can we measure that?

• Batch cloning can be tested in local and pipeline time
• Cluster cloning can be tested in local and pipeline time

Links / references