Is this a BUG REPORT or FEATURE REQUEST?:
feature

What happened:
Currently, our E2E tests don't cover every part of the project and we need to have tests for more complex scenarios to be aware of the edge cases.

What you expected to happen:
Discuss how we're going to implement these tests and how the structure is supposed to be.

I think it would be good to have an isolated and fresh environment for each test case and keep all the records related to a test case inside its own zone file.
We can separate the test cases by keeping them in their own directories and have a manager script at the root that runs each test cases' script.
The structure would look like this:

├─e2e_tests
├── dockerv2
│   ├── pull
│   │   ├── zonefile
│   │   └── test.sh
│   └── push
│       ├── zonefile
│       └── test.sh
└── manager.sh

Not sure how we should handle the containers for each test case. We can use solutions like compose or have our own script for creating and managing the test containers.
I personally prefer the custom script and a downside would be requiring more time to implement a stable solution.
We can also add the container-related stuff to each test's script but think it would be better to keep the test script as clear and simple as possible and only keep the tests inside it.

Would love to hear other thoughts and approaches.

How to reproduce it (as minimally and precisely as possible):
Feature Request

Anything else we need to know?:
Questions:

• A better structure for managing the files?
• Alternatives for compose and custom script?
• Other solutions for managing the test cases instead of a manager bash script?