Change AfterTypeDiscoveryTest to avoid assumptions about how many tot…

[manovotn]

…al components are in test deployment.

Fixes #400

[manovotn]

@erdlet This PR should fix your problems, do you think you could checkout this branch, build it (just mvn clean install will do) and test it with GF?

[erdlet]

Thanks a lot for this fix. I'll test it until this evening against GF and provide feedback to you.

[manovotn]

I have marked the PR and the issue as challenge and accepted for I believe in this case the test makes assumptions that it shouldn't. Nonetheless, if we verify that this fixes the problem for you, we can make a quick TCK release if we chose to :)

[erdlet]

@manovotn I just ran the TCK built from your branch and ran it against GF 7 with MVC 2.1.0.RC1 and Krazo 3.0.0.RC1.

It seems this test is broken too: AfterTypeDiscoveryMassOperationsTest>Arquillian.run:138->testInitialAlternatives:77 expected [3] but found [11].
I guess It takes the same assumptions as the test you already fixed. Can you please have a look at it too? The fixed test works like a charm :)

[manovotn]

@erdlet good find!
Both tests should now be fixed as part of this PR :)

[erdlet]

@manovotn thanks for the quick fix! I'll build and run the TCK again so I should've feedback in a few minutes if everything is fine now :)

[erdlet]

@manovotn great, it works 👍🏻 Thanks a lot for your help!

Nonetheless, if we verify that this fixes the problem for you, we can make a quick TCK release if we chose to

Would it be possible to release the TCK within the next days so I can create a PR to re-integrate MVC into GF? :)

[manovotn]

@erdlet glad to hear that.
And yes, I'll do the release tomorrow and will let you know once its out.