Re: [wildfly-dev] Chained transformers and 7.1.x tests

https://github.com/wildfly/wildfly-core/pull/10 enables this and also gets rid of all the .dmr files used by the subsystem tests. The tests will now simply generate these on demand. All tests in core pass with this (also for 7.1.x when enabled). In wildfly everything passes when running the tests, although there are some issues in the following subsystems when running against 7.1.x * jgroups - needs a touched up .dmr file for 7.1.x, I have s commit

* infinispan - something goes wrong in the

* messaging - although not a 7.1.x issue, the PR enables testing against WF 8 as well. However, the messaging extension uses some methods which are no longer available in WF 9. This could be fixed by adding a test-controller-8_0_0. These problems are probably not too important to spend a lot of time on at this stage, since they do not occur when running against the versions enabled by default. The point of allowing the 7.1.x testing again is to get better coverage while converting the chained transformer stuff so that I can work through problems while I remember how this works, rather than in many month’s time. On 5 Jul 2014, at 10:57, Kabir Khan <kabir.khan(a)jboss.com&gt; wrote: > I’ve got the chained transformers mostly working in its own tests, but have some issues to iron out when using them for real, which is not picked up by the tests I wrote. Currently I am trying to convert the jmx subsystem, and think I will also do the other ones in wildfly-core (remoting and logging). > > Since we have disabled transformer testing against WildFly 8, and AS 7.1.x, there isn’t actually much of a chain to test at the moment. To get better coverage of what I have done in real subsystem scenarios, I would like to temporarily reinstate the test controller for 7.1.x, and to use a system property to enable running of tests against 7.1.x and WildFly 8 unless someone has some strong objections. If people start converting to use chained transformers, since the 7.1.x tests already exist, I think this will be valuable validation of what they are doing. > > > > > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev