No, we didn't assign it to anyone. Sent from my iPhone On Sep 19, 2011, at 16:19, Shane Bryzak <sbryzak(a)redhat.com&gt; wrote: > Was it decided who would take care of the testsuite restructure? I must > admit I wasn't paying much attention during this discussion ;) > > On 19/09/11 23:39, Jozef Hartinger wrote: >> INTEGRATION TESTS >> >> Structure: >> >> - api >> - impl >> - testsuite / src / test / java >> >> Container-specific issues >> - there will be a BaseDeploymentFactory that creates base deployment >> based on a system property (arquillian container name) >> - there will be no common package scheme for now >> >> Default profile >> - weld embedded >> - skipped tests if weld embedded does not make sense in the context of >> the module >> >> >> FUNCTIONAL TESTS >> - m4 will be used to generate pom files from our templates (stored in >> Seam QA github) >> > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

Marek is working on integration tests while me and Tomas are working on functional tests. On 09/20/2011 12:24 AM, Jason Porter wrote: > No, we didn't assign it to anyone. > > Sent from my iPhone > > On Sep 19, 2011, at 16:19, Shane Bryzak&lt;sbryzak(a)redhat.com&gt; wrote: > >> Was it decided who would take care of the testsuite restructure? I >> must >> admit I wasn't paying much attention during this discussion ;) >> >> On 19/09/11 23:39, Jozef Hartinger wrote: >>> INTEGRATION TESTS >>> >>> Structure: >>> >>> - api >>> - impl >>> - testsuite / src / test / java >>> >>> Container-specific issues >>> - there will be a BaseDeploymentFactory that creates base deployment >>> based on a system property (arquillian container name) >>> - there will be no common package scheme for now >>> >>> Default profile >>> - weld embedded >>> - skipped tests if weld embedded does not make sense in the context of >>> the module >>> >>> >>> FUNCTIONAL TESTS >>> - m4 will be used to generate pom files from our templates (stored in >>> Seam QA github) >>> >> _______________________________________________ >> seam-dev mailing list >> seam-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/seam-dev

On Tue, 20 Sep 2011 10:51:47 +0200, Shane Bryzak <sbryzak(a)redhat.com&gt; wrote: > Can we please make it a priority to get the Solder testsuite updated to > the new structure and all the tests passing? Once this is done, the > rest of the team can help out by updating the other modules to follow > the same configuration. Sure. Marek, can you please focus on this?

Thanks, Ondra

Thanks Marek. Just a heads up - the Catch, Config and Servlet modules are going to be merged with Solder as sub-modules shortly. Would you like me to wait until the testsuite is stable before I move the tests over for these?

Shane On 21/09/11 04:29, Marek Schmidt wrote: > On 09/20/2011 03:47 PM, Ondřej Skutka wrote: >> On Tue, 20 Sep 2011 10:51:47 +0200, Shane Bryzak <sbryzak(a)redhat.com&gt; >> wrote: >> >>> Can we please make it a priority to get the Solder testsuite updated to >>> the new structure and all the tests passing? Once this is done, the >>> rest of the team can help out by updating the other modules to follow >>> the same configuration. >> >> Sure. Marek, can you please focus on this? > > Sure, I am on it. > > Current progress in > > https://github.com/maschmid/solder/tree/testsuite-update-2 > >> >> Thanks, >> Ondra >> >