[xwiki-devs] [proposal] A separate hudson project for escaping tests
Hi devs, The new escaping tests I recently proposed generate a quite large number of tests and take noticeable amount of time to run. There are currently 782 escaping tests, they need 8 minutes on my core duo (for comparision, there are about 1800 tests in enterprise/ in total, they need 1 hour). Caleb had an idea about adding a separate Hudson project for them, this would make it possible to see the cause of failures or, in ideal case, run functional tests in parallel with escaping tests (if the hardware is good enough). WDYT? Alex
On 08/17/2010 06:53 PM, Alex Busenius wrote:
Hi devs,
The new escaping tests I recently proposed generate a quite large number of tests and take noticeable amount of time to run.
There are currently 782 escaping tests, they need 8 minutes on my core duo (for comparision, there are about 1800 tests in enterprise/ in total, they need 1 hour).
Caleb had an idea about adding a separate Hudson project for them, this would make it possible to see the cause of failures or, in ideal case, run functional tests in parallel with escaping tests (if the hardware is good enough).
WDYT?
Well, currently all the integration tests are run during the XE build, and for consistency I think it would be better to move the tests to enterprise/trunk/distribution-tests. The fact that they take a lot of time is not reason enough to leave them out of the normal build. Alternatively, we could move all integration tests to their own project, making the XE build faster. Ideally, we should work on improving the performance, so that tests take at most half the time they require now. -- Sergiu Dumitriu http://purl.org/net/sergiu/
On Wed, Aug 18, 2010 at 09:34, Sergiu Dumitriu <[email protected]> wrote:
On 08/17/2010 06:53 PM, Alex Busenius wrote:
Hi devs,
The new escaping tests I recently proposed generate a quite large number of tests and take noticeable amount of time to run.
There are currently 782 escaping tests, they need 8 minutes on my core duo (for comparision, there are about 1800 tests in enterprise/ in total, they need 1 hour).
Caleb had an idea about adding a separate Hudson project for them, this would make it possible to see the cause of failures or, in ideal case, run functional tests in parallel with escaping tests (if the hardware is good enough).
WDYT?
Well, currently all the integration tests are run during the XE build,
Not in hudson, there is XE build (http://hudson.xwiki.org/view/Enterprise/job/xwiki-product-enterprise/) and XE-tests (http://hudson.xwiki.org/view/Enterprise/job/xwiki-product-enterprise-tests/) builds which are separated hudson jobs. So i don't see why no building escaping tests with other integration tests.
and for consistency I think it would be better to move the tests to enterprise/trunk/distribution-tests. The fact that they take a lot of time is not reason enough to leave them out of the normal build.
Alternatively, we could move all integration tests to their own project, making the XE build faster.
Ideally, we should work on improving the performance, so that tests take at most half the time they require now.
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
Sergiu Dumitriu wrote:
On 08/17/2010 06:53 PM, Alex Busenius wrote:
Hi devs,
The new escaping tests I recently proposed generate a quite large number of tests and take noticeable amount of time to run.
There are currently 782 escaping tests, they need 8 minutes on my core duo (for comparision, there are about 1800 tests in enterprise/ in total, they need 1 hour).
Caleb had an idea about adding a separate Hudson project for them, this would make it possible to see the cause of failures or, in ideal case, run functional tests in parallel with escaping tests (if the hardware is good enough).
WDYT?
Well, currently all the integration tests are run during the XE build, and for consistency I think it would be better to move the tests to enterprise/trunk/distribution-tests. The fact that they take a lot of time is not reason enough to leave them out of the normal build.
Alternatively, we could move all integration tests to their own project, making the XE build faster.
I'm pretty sure xwiki-enterprise and xwiki-enterprise-tests are already separate projects in hudson.
Ideally, we should work on improving the performance, so that tests take at most half the time they require now.
As far as I can tell, most of the tests are at near their performance limit. We could improve performance by improving page rendering time but I think we should be thinking about test time as an ever increasing number, not a static one. Caleb
Since those who answered were skeptical about a separate project, I'll move them to enterprise/trunk/distribution-tests/escaping-tests, to other tests. If nobody complains, I'll do it later today. Alex On 08/17/2010 06:53 PM, Alex Busenius wrote:
Hi devs,
The new escaping tests I recently proposed generate a quite large number of tests and take noticeable amount of time to run.
There are currently 782 escaping tests, they need 8 minutes on my core duo (for comparision, there are about 1800 tests in enterprise/ in total, they need 1 hour).
Caleb had an idea about adding a separate Hudson project for them, this would make it possible to see the cause of failures or, in ideal case, run functional tests in parallel with escaping tests (if the hardware is good enough).
WDYT?
Alex _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (4)
-
Alex Busenius -
Caleb James DeLisle -
Sergiu Dumitriu -
Thomas Mortagne