[
https://issues.jboss.org/browse/RFPL-3367?page=com.atlassian.jira.plugin....
]
Pavol Pitonak commented on RFPL-3367:
-------------------------------------
Works perfectly for 6 components as in the job you linked. However, I think that it
wouldn't work for all 83 components - the table would be too big.
Can we create about 20 groups somehow (not using 20 almost identical testng.xml
descriptors)?
Split suites to decrease job run times and to acquire better
feedback
---------------------------------------------------------------------
Key: RFPL-3367
URL:
https://issues.jboss.org/browse/RFPL-3367
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: QE
Reporter: Jiří Štefek
The suite for tables is now too big and it cannot run on Jenkins under {color:red}900
mins{color}, we need to split it somehow. But, imho, it is not just problem of this suite,
we should divide all suites somehow to gain at least a better feedback.
Any ideas how to divide the suites?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)