Execution environment test builds

[oraNod]

Addresses #16

Opening as a draft to start a conversation and get some advice on how to proceed.

• At the moment I've been using an arg parser to pass things like the path and collection namespace and name. This has been a convenient way to test things and work through the logic. I plan to modify things and get this better integrated with the rest of the project but wanted to open a PR and work through all that collaboratively.
• Need to add docstrings and type hints.
• Need to add actual tests for ee builds. Should I port over the contents of https://github.com/ansible-collections/community.docker/tree/main/tests/ee ?

[oraNod]

@felixfontein Hey, thanks for #83 that looks like it simplifies things. I can just import with this:

from .collection import (
    build_collection,
)

Is that correct? I'm just wondering though, will that result in the collection being built for each session? On the one hand that makes sense if you're running individual test sessions (not sure if that's even possible). But if you're running all test sessions at once, does that mean the collection gets built multiple times?

[felixfontein]

Is that correct?

Yes.

I'm just wondering though, will that result in the collection being built for each session?

Yes.

On the one hand that makes sense if you're running individual test sessions (not sure if that's even possible). But if you're running all test sessions at once, does that mean the collection gets built multiple times?

That's true, but it could also happen in different contexts (i.e. with different ansible-core versions or branches). Also building is usually the fastest part of all tests involving builds, so I think it's ok. (At least for now; it can always be improved later on.)