Refactor how the values of properties in integration tests are queried

[Azurelol]

Description

Rewrites how the values of properties are queried by the integration tests by using a writer object which handles the writing of the query task and provides the functions for testing them.

The newer API simplifies the writing of these property tests:

        when:
        def query = new PropertyQueryTaskWriter("${extensionName}.${property}")
        query.write(buildFile)
        def result = runTasksSuccessfully(query.taskName)

        then:
        query.matches(result, testValue)

Changes

• UnityIntegrationTest
• *IntegrationTests
• PropertyQueryTaskWriter

[Larusso]

We have to be carefull to not getting too overboard with helper utilities in the specs as it can happen that the specs become unreadable or the maintanance hell when doing bigger shifts.

Also again. You must if you want to use traits be carefull that it won't be added multiple times as it can lead to some very funny linking issues at runtime.

[Larusso]

This PropertyUtilsImpl is a trait I hope? Because I get slight nervious ticks when seeing an Interface called Impl :)

[Azurelol]

Yes, it's a trait.

[Azurelol]

We have to be carefull to not getting too overboard with helper utilities in the specs as it can happen that the specs become unreadable or the maintanance hell when doing bigger shifts.

Also again. You must if you want to use traits be carefull that it won't be added multiple times as it can lead to some very funny linking issues at runtime.

Yes, for the utilities I am keeping in mind that they shouldn't negatively affect the readability of the tests. I went over the design of the API a few times on this newer one.

[Larusso]

I like it.
We should move this stuff as fast as possible into the shared test lib.