ginkgo Proposal: Finer-Grained Shared Resources and Parallelism

I'd like to propose some new behavior for Ginkgo and am looking for feedback. The intent here is to solve long-standing problems that keep recurring, particularly for users who build large complex integration suites (e.g. k8s e2e suites).

Please take a look at the proposal up on hackmd.io:

https://hackmd.io/@onsi/By32R9AfT

and either comment on the doc at the link or in the comments below.

Oct 31 '23 15:10 onsi

I did a quick read of the proposal and at face everything outlined seems like a great addition! I'll have more time to pick through it over the weekend to really think through the Subsuites side of things. But the new Exclusive functionality is a fantastic improvement - no notes there!

👏🏽

Nov 03 '23 06:11 XenoPhex

Thanks for taking a look @XenoPhex !

Nov 03 '23 14:11 onsi

I went through the proposal. Lot's of useful stuff, thanks for considering this change. I left one comment (just for clarification), the proposal itself looks good to me.

Nov 13 '23 12:11 pohly

Thanks @pohly !

Nov 13 '23 12:11 onsi

Hi @onsi! The proposal looks very interesting. For me it would mean no more shuffling and ordering test suites, so that the actual tests are run after a test server is build and available for use and faster test runs because I don't have to serialize everything :) This will also bring more clarity and readability when writing tests.

Nov 16 '23 13:11 chombium

thanks @chombium - that’s exactly what i’m hoping this enables :) glad to hear you’re seeing it too :)

Nov 16 '23 14:11 onsi

Hi @onsi I like this! As a member of team that leverages Ginkgo heavily for integration/system/e2e type tests that rely on the ordered function quite a bit this opens up some new possibilities!

Nov 16 '23 15:11 Dannyb48

thanks for taking a look @Dannyb48 ! now i just need to implement it all, lol!

Nov 16 '23 17:11 onsi