March 2014 - richfaces-planning-issues

[JBoss JIRA] (RFPL-3268) Reimplement MatrixConfigurator in Metamer tests

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RFPL-3268?page=com.atlassian.jira.plugin.... ] Jiří Štefek edited comment on RFPL-3268 at 3/11/14 6:00 AM: ------------------------------------------------------------ Because the Arquillian extension was not easily implementable as a testing framework independent solution, the MatrixConfigurator was replaced by using of a TestNG's @DataProvider. The TestNG was updated to latest version. The features: * The tested/supported templates are specified in value of {{@Templates}} annotation of first found field in hierarchy of test (from offspring to parent) ( == maybe as before). * The plain template is activated by default as before. * To run tests in all templates one can now use either {{*}} or {{all}}. * To run tests in specific template one can still use everything as before plus I've added some aliases for each template. One can now use e.g. {{-Dtemplates=edt}} for running tests in richExtendedDataTable. The aliases are in [Template|https://github.com/richfaces/richfaces-qa/blob/master/metamer/ap...] class of Metamer Application. The aliases are case insensitive. * The templates can now be run separately, e.g.: {{-Dtemplates=plain,edt,cp}} (plain, extendedDataTable, collapsiblePanel) ** all tests will run in each specified template, templates separator is {{comma}} ** one can even use {{-Dtemplates=plain,*}} which will run all tests in plain template and in all supported templates (there will be 2 tests for plain template). * The templates can now be run concurrently, e.g.: {{-Dtemplates=acc>edt,cp}} (1st configuration: EDT inside accordion, 2nd configuration: collapsible panel) * One can configure a test class/method to run or to not run with specific templates using @Templates (as before) * The {{@Use}} parameter was separated to {{@UseForAllTests}} and {{@UseWithField}}. ** {{@Inject}} was deleted ** {{@UseForAllTests}} for marking field, that will be used for configuration in all tests ** {{@UseWithField}} for marking method to use a field for configuration ** {{@Uses}} can now only accept {{@UseWithField}} annotations ** {{@UseForAllTests}} and {{@UseWithField}} can be used concurrently ** the supported types for fields are Strings, Enums, and everything not primitive (can be fixed) from field was (Author: jstefek): Because the Arquillian extension was not easily implementable as a testing framework independent solution, the MatrixConfigurator was replaced by using of a TestNG's @DataProvider. The TestNG was updated to latest version. The templates features: * The tested/supported templates are specified in value of {{@Templates}} annotation of first found field in hierarchy of test (from offspring to parent) ( == maybe as before). * The plain template is activated by default as before. * To run tests in all templates one can now use either {{*}} or {{all}}. * To run tests in specific template one can still use everything as before plus I've added some aliases for each template. One can now use e.g. {{-Dtemplates=edt}} for running tests in richExtendedDataTable. The aliases are in [Template|https://github.com/richfaces/richfaces-qa/blob/master/metamer/ap...] class of Metamer Application. The aliases are case insensitive. * The templates can now be run separately, e.g.: {{-Dtemplates=plain,edt,cp}} (plain, extendedDataTable, collapsiblePanel) ** all tests will run in each specified template, templates separator is {{comma}} ** one can even use {{-Dtemplates=plain,*}} which will run all tests in plain template and in all supported templates (there will be 2 tests for plain template). * The templates can now be run concurrently, e.g.: {{-Dtemplates=acc>edt,cp}} (1st configuration: EDT inside accordion, 2nd configuration: collapsible panel) * One can configure a test class/method to run or to not run with specific templates using @Templates (as before) * The {{@Use}} parameter was separated to {{@UseForAllTests}} and {{@UseWithField}}. ** {{@Inject}} was deleted ** {{@UseForAllTests}} for marking field, that will be used for configuration in all tests ** {{@UseWithField}} for marking method to use a field for configuration ** {{@Uses}} can now only accept {{@UseWithField}} annotations ** {{@UseForAllTests}} and {{@UseWithField}} can be used concurrently ** the supported types for fields are Strings, Enums, and everything not primitive (can be fixed) from field > 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: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RFPL-3268) Reimplement MatrixConfigurator in Metamer tests

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RFPL-3268?page=com.atlassian.jira.plugin.... ] Jiří Štefek resolved RFPL-3268. ------------------------------- Resolution: Done Because the Arquillian extension was not easily implementable as a testing framework independent solution, the MatrixConfigurator was replaced by using of a TestNG's @DataProvider. The TestNG was updated to latest version. The templates features: * The tested/supported templates are specified in value of {{@Templates}} annotation of first found field in hierarchy of test (from offspring to parent) ( == maybe as before). * The plain template is activated by default as before. * To run tests in all templates one can now use either {{*}} or {{all}}. * To run tests in specific template one can still use everything as before plus I've added some aliases for each template. One can now use e.g. {{-Dtemplates=edt}} for running tests in richExtendedDataTable. The aliases are in [Template|https://github.com/richfaces/richfaces-qa/blob/master/metamer/ap...] class of Metamer Application. The aliases are case insensitive. * The templates can now be run separately, e.g.: {{-Dtemplates=plain,edt,cp}} (plain, extendedDataTable, collapsiblePanel) ** all tests will run in each specified template, templates separator is {{comma}} ** one can even use {{-Dtemplates=plain,*}} which will run all tests in plain template and in all supported templates (there will be 2 tests for plain template). * The templates can now be run concurrently, e.g.: {{-Dtemplates=acc>edt,cp}} (1st configuration: EDT inside accordion, 2nd configuration: collapsible panel) * One can configure a test class/method to run or to not run with specific templates using @Templates (as before) * The {{@Use}} parameter was separated to {{@UseForAllTests}} and {{@UseWithField}}. ** {{@Inject}} was deleted ** {{@UseForAllTests}} for marking field, that will be used for configuration in all tests ** {{@UseWithField}} for marking method to use a field for configuration ** {{@Uses}} can now only accept {{@UseWithField}} annotations ** {{@UseForAllTests}} and {{@UseWithField}} can be used concurrently ** the supported types for fields are Strings, Enums, and everything not primitive (can be fixed) from field > 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: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RFPL-3279) TestEditor#testReadonly wrong implementation

by Matej Novotny (JIRA)

Matej Novotny created RFPL-3279: ----------------------------------- Summary: TestEditor#testReadonly wrong implementation Key: RFPL-3279 URL: https://issues.jboss.org/browse/RFPL-3279 Project: RichFaces Planning Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Matej Novotny Assignee: Matej Novotny Fix For: 5.0.0.Alpha4 The test is passing even though it should fail due to RF-13574. Reimplement it to detect failure correctly. For RF 4 test is working so only push this to RF 5 -- 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: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RFPL-3278) Stablilize framework tests for RF5 on WildFly

by Pavol Pitonak (JIRA)

Pavol Pitonak created RFPL-3278: ----------------------------------- Summary: Stablilize framework tests for RF5 on WildFly Key: RFPL-3278 URL: https://issues.jboss.org/browse/RFPL-3278 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: QE Affects Versions: 5.0.0.Alpha3 Reporter: Pavol Pitonak Assignee: Jiří Štefek Fix For: 5.0.0.Alpha4 -- 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: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3276) metamer: increase height of contextmenu and menugroup sample in accordion template

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RFPL-3276?page=com.atlassian.jira.plugin.... ] Jiří Štefek updated RFPL-3276: ------------------------------ Summary: metamer: increase height of contextmenu and menugroup sample in accordion template (was: metamer: increase height of contextmenu sample) > metamer: increase height of contextmenu and menugroup sample in accordion template > ---------------------------------------------------------------------------------- > > Key: RFPL-3276 > URL: https://issues.jboss.org/browse/RFPL-3276 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Jiří Štefek > Assignee: Jiří Štefek > > When one opens the context menu in the accordion template, then some of the choices are hidden behind the template. The automated tests are failing due to this. -- 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: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3276) metamer: increase height of contextmenu sample

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RFPL-3276?page=com.atlassian.jira.plugin.... ] Jiří Štefek updated RFPL-3276: ------------------------------ Component/s: QE > metamer: increase height of contextmenu sample > ---------------------------------------------- > > Key: RFPL-3276 > URL: https://issues.jboss.org/browse/RFPL-3276 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Jiří Štefek > Assignee: Jiří Štefek > > When one opens the context menu in the accordion template, then some of the choices are hidden behind the template. The automated tests are failing due to this. -- 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: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3277) metamer: reimplement hotkey test: testPreventDefaultFalse

by Jiří Štefek (JIRA)

Jiří Štefek created RFPL-3277: --------------------------------- Summary: metamer: reimplement hotkey test: testPreventDefaultFalse Key: RFPL-3277 URL: https://issues.jboss.org/browse/RFPL-3277 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: QE Reporter: Jiří Štefek The test is failing on Jenkins with newer versions of Firefox. -- 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: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3276) metamer: increase height of contextmenu sample

by Jiří Štefek (JIRA)

Jiří Štefek created RFPL-3276: --------------------------------- Summary: metamer: increase height of contextmenu sample Key: RFPL-3276 URL: https://issues.jboss.org/browse/RFPL-3276 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jiří Štefek Assignee: Jiří Štefek When one opens the context menu in the accordion template, then some of the choices are hidden behind the template. The automated tests are failing due to this. -- 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: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3275) metamer: fix editor tests/fragment

by Jiří Štefek (JIRA)

Jiří Štefek created RFPL-3275: --------------------------------- Summary: metamer: fix editor tests/fragment Key: RFPL-3275 URL: https://issues.jboss.org/browse/RFPL-3275 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: QE Environment: RF 4.3.x, RF 4.5.x Reporter: Jiří Štefek It seems that the editor fragment is not working. One cannot send a value with it. It works with RF 5.x. -- 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: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3263) Create tests for pass-through attributes

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RFPL-3263?page=com.atlassian.jira.plugin.... ] Lukáš Fryč resolved RFPL-3263. ------------------------------ Fix Version/s: 5.0.0.Alpha4 (was: 5-Tracking) Resolution: Done > Create tests for pass-through attributes > ---------------------------------------- > > Key: RFPL-3263 > URL: https://issues.jboss.org/browse/RFPL-3263 > Project: RichFaces Planning > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: QE > Reporter: Matej Novotny > Assignee: Matej Novotny > Labels: jsf22 > Fix For: 5.0.0.Alpha4 > > > Based on RFPL-2506, we need to create tests for JSF 2.2 feature - _pass-through attributes_. > It is sensible to test this with input components and maybe some select components as well. Easiest way would to to add some more tests to Metamer, reusing the existing ones. > More information on this feature can be found [here|http://jdevelopment.nl/jsf-22/#1089]. -- 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: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

richfaces-planning-issues March 2014