Follow up to #36538 (comment)
There are many tests that create objects (containers, networks, volumes, services) with a name. We should avoid using names (where possible), to prevent tests possibly influencing other tests due to resources not (yet) being cleaned up, or possibly if tests are run in parallel
- Remove names from tests, and use object ID's (where possible)
- For those tests that do need a name, make sure that a unique name is used. (For example, use
t.Name() to name an object after the name of the test, or use a randomly generated name)
This may be a lot of work to go through all the tests, but perhaps there are contributors that want to work on some of these
If you're interested to work in this, leave a comment below, and mention what tests you'll be working on (so that it doesn't conflict with other people working on the same tests 😅)
Follow up to #36538 (comment)
There are many tests that create objects (containers, networks, volumes, services) with a name. We should avoid using names (where possible), to prevent tests possibly influencing other tests due to resources not (yet) being cleaned up, or possibly if tests are run in parallel
t.Name()to name an object after the name of the test, or use a randomly generated name)This may be a lot of work to go through all the tests, but perhaps there are contributors that want to work on some of these
If you're interested to work in this, leave a comment below, and mention what tests you'll be working on (so that it doesn't conflict with other people working on the same tests 😅)