]
Pavol Pitonak updated RFPL-3268:
--------------------------------
Fix Version/s: 5.0.0.Alpha4
(was: 5-Future)
Reimplement MatrixConfigurator in Metamer tests
-----------------------------------------------
Key: RFPL-3268
URL:
https://issues.jboss.org/browse/RFPL-3268
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: QE
Reporter: Pavol Pitonak
Assignee: Jiří Štefek
Fix For: 5.0.0.Alpha4
Metamer component enabling us to run tests in various templates and to run tests with
parameters.
Problems of current implementation:
* Implemented as a TestNG interceptor, i.e. it cannot work with JUnit (which is used by
all other RichFaces tests)
* We cannot upgrade to latest version of TestNG (not sure why, probably a bug in TestNG
interceptors, it skips tests)
Requirements for new implementation (almost identical to current implementation):
* It should work with both TestNG and JUnit (preferably implemented as an Arquillian
extension)
* I can run tests in plain template: mvn clean verify
* I can run tests in all templates: mvn clean verify -Dtemplates=*
* I can run tests in all templates using "all" (asterisk cannot be used in
Jenkins matrix): mvn clean verify -Dtemplates=all
* I can run tests in one specific template: mvn clean verify -Dtemplates=richList
* I can run tests in two or more specific templates (each separately): mvn clean verify
-Dtemplates=richList,richDataTable, i.e. each test will run twice - once in richList
template and once in richDataTable template
* I can run tests in two or more specific templates (applied all at once): mvn clean
verify -Dtemplates=richList,richDataTable, i.e. each test will run once - with both
richList and richDataTable templates activated concurently, comma cannot be used as
separator - optional feature?
* I can configure a test class/method to run with specific templates using @Templates (as
is now)
* I can configure a test class/method not to run with specific templates using @Templates
(as is now)
* I can configure a test to run with multiple parameters using @Inject, @Use (as is now)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: