Support for nested test suites

[ekharchenko-avito]

• merged William Petit changes to support suite-in-suite embedding
• added suite Properties fulfillment from attributes (like it already was for testcase)
• added test for that

[joshdk]

Thank you for your submission @ekharchenko-avito! This is another interesting edge-case.

PR looks generally fine to me, left a few simple comments.

---

One thought I had (and I don't really have enough data to have an opinion on this) was that instead of nesting suites the way they are contained in the XML:

suite-a
 `- test-a
 `- suite-b
     `- test-b
     `- test-b

Would it make any sense to flatten the structure into something like this:

suite-atest-a
suite-a.suite-b.test-b
suite-a.suite-b.test-b

This transform would be done only to benefit users of the library, but again, I don't have any data to know if that would be the case. Thoughts?

Thanks again, cheers!

[ekharchenko-avito]

Would it make any sense to flatten the structure into something like this:

That don't make sense for my use case.
That will give /untitled/tests.SampleTest.SampleTest::testB in an example PHPUnit file which is a mess of original command line tests selector, class name, and test method name. Don't really want to parse-out those parts from the flattened name in production code.

[joshdk]

Apologies for the delay @ekharchenko-avito. Thank you so much for your contribution! 🎉