From issues at jboss.org Mon Mar 3 06:42:49 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 3 Mar 2014 06:42:49 -0500 (EST) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3263) Create tests for pass-through attributes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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 From issues at jboss.org Thu Mar 6 06:35:33 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 6 Mar 2014 06:35:33 -0500 (EST) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3275) metamer: fix editor tests/fragment In-Reply-To: References: Message-ID: 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 From issues at jboss.org Thu Mar 6 06:45:33 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 6 Mar 2014 06:45:33 -0500 (EST) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3276) metamer: increase height of contextmenu sample In-Reply-To: References: Message-ID: 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 From issues at jboss.org Thu Mar 6 06:53:33 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 6 Mar 2014 06:53:33 -0500 (EST) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3277) metamer: reimplement hotkey test: testPreventDefaultFalse In-Reply-To: References: Message-ID: 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 From issues at jboss.org Thu Mar 6 06:53:33 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 6 Mar 2014 06:53:33 -0500 (EST) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3276) metamer: increase height of contextmenu sample In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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 From issues at jboss.org Thu Mar 6 06:55:33 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 6 Mar 2014 06:55:33 -0500 (EST) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3276) metamer: increase height of contextmenu and menugroup sample in accordion template In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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 From issues at jboss.org Thu Mar 6 08:31:34 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Thu, 6 Mar 2014 08:31:34 -0500 (EST) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3278) Stablilize framework tests for RF5 on WildFly In-Reply-To: References: Message-ID: 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 From issues at jboss.org Tue Mar 11 05:03:10 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Tue, 11 Mar 2014 05:03:10 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3279) TestEditor#testReadonly wrong implementation In-Reply-To: References: Message-ID: 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 From issues at jboss.org Tue Mar 11 06:01:13 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 11 Mar 2014 06:01:13 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3268) Reimplement MatrixConfigurator in Metamer tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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/application/src/main/java/org/richfaces/tests/metamer/Template.java] 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 From issues at jboss.org Tue Mar 11 06:01:14 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 11 Mar 2014 06:01:14 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3268) Reimplement MatrixConfigurator in Metamer tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951855#comment-12951855 ] 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/application/src/main/java/org/richfaces/tests/metamer/Template.java] 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/application/src/main/java/org/richfaces/tests/metamer/Template.java] 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 From issues at jboss.org Tue Mar 11 06:03:10 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 11 Mar 2014 06:03:10 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3268) Reimplement MatrixConfigurator in Metamer tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951855#comment-12951855 ] Ji?? ?tefek edited comment on RFPL-3268 at 3/11/14 6:01 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/application/src/main/java/org/richfaces/tests/metamer/Template.java] 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, that will 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 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/application/src/main/java/org/richfaces/tests/metamer/Template.java] 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 From issues at jboss.org Tue Mar 11 06:03:11 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 11 Mar 2014 06:03:11 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-1467) @Test annotation param dependsOnMethods in Metamer's ftest causes IllegalStateException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-1467: ------------------------------ Fix Version/s: 5.0.0.Alpha4 (was: 5-Future) > @Test annotation param dependsOnMethods in Metamer's ftest causes IllegalStateException > --------------------------------------------------------------------------------------- > > Key: RFPL-1467 > URL: https://issues.jboss.org/browse/RFPL-1467 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: QE > Environment: Metamer 4.1.0-snapshot, r.22501 > Reporter: J?n Jamrich > Assignee: Pavol Pitonak > Fix For: 5.0.0.Alpha4 > > > When tried set dependsOnMethods param to @Test annotation in Metamer's ftests, get IllegalStateException thrown from MatrixConfigurator. > There aren't any other methods annotated by @Test with dependsOnMethods param, so its possible that this issue is in Metamer longer time without being discovered. > By debugging observed that list of methods set to be executed by TestRunner depends on this param. In other word, when set dependsOnMethods param to @Test annotation - this method (on which was this param set to annotation) doesn't appear in list of methods being executed (LinkedList methods attribute of MatrixConfigurator). > This attribute is initialized in method > public List intercept(List methodInstances, ITestContext context) > which is called directly from org.testng.TestRunner, which give param List methodInstances depending on dependsOnMethods param set to @Test annotation as well. > This behavior should be ok, since methods which are not depending on another else method should be executed first. > But what seems worse is that when run this again - for method anotated by @Test with param dependsOnMethod, then list of methods which going to be executed is empty - do no test method called. > And in case when all methods except one depends on another method, different exception is result of run testsuite: > Running TestSuite > org.apache.maven.surefire.booter.SurefireExecutionException: null; nested exception is java.lang.NullPointerException: null > java.lang.NullPointerException > at org.richfaces.tests.metamer.ftest.MetamerTestInfo.getConfigurationInfo(MetamerTestInfo.java:50) > at org.richfaces.tests.metamer.ftest.MetamerTestInfo.getConfigurationInfoInParenthesses(MetamerTestInfo.java:77) > at org.richfaces.tests.metamer.ftest.MetamerSeleniumLoggingTestListener.getMessage(MetamerSeleniumLoggingTestListener.java:35) > at org.jboss.test.selenium.listener.SeleniumLoggingTestListener.logStatus(SeleniumLoggingTestListener.java:82) > at org.jboss.test.selenium.listener.SeleniumLoggingTestListener.onTestFailure(SeleniumLoggingTestListener.java:55) > at org.testng.internal.Invoker.runTestListeners(Invoker.java:1634) > at org.testng.internal.Invoker.runTestListeners(Invoker.java:1618) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1101) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:137) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:121) > at org.testng.TestRunner.runWorkers(TestRunner.java:1030) > at org.testng.TestRunner.privateRun(TestRunner.java:709) > at org.testng.TestRunner.run(TestRunner.java:579) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:331) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:326) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:288) > at org.testng.SuiteRunner.run(SuiteRunner.java:193) > at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:910) > at org.testng.TestNG.runSuitesLocally(TestNG.java:879) > at org.testng.TestNG.run(TestNG.java:787) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:62) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:141) > at org.apache.maven.surefire.Surefire.run(Surefire.java:177) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) > So this should be issue related to TestNG itself (current version 5.12.1), tried 5.13, but the same behavior. > There is stack trace: > java.lang.IllegalStateException: can't find more configured methods > at org.richfaces.tests.metamer.ftest.MatrixConfigurator.configureMethod(MatrixConfigurator.java:150) > at org.richfaces.tests.metamer.ftest.MatrixConfigurator.beforeInvocation(MatrixConfigurator.java:101) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:62) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:141) > at org.apache.maven.surefire.Surefire.run(Surefire.java:177) > at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) > ... Removed 22 stack frames -- 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 From issues at jboss.org Tue Mar 11 06:03:11 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 11 Mar 2014 06:03:11 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-1467) @Test annotation param dependsOnMethods in Metamer's ftest causes IllegalStateException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek resolved RFPL-1467. ------------------------------- Resolution: Out of Date Was fixed with resolving of https://issues.jboss.org/browse/RFPL-3268 > @Test annotation param dependsOnMethods in Metamer's ftest causes IllegalStateException > --------------------------------------------------------------------------------------- > > Key: RFPL-1467 > URL: https://issues.jboss.org/browse/RFPL-1467 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: QE > Environment: Metamer 4.1.0-snapshot, r.22501 > Reporter: J?n Jamrich > Assignee: Pavol Pitonak > Fix For: 5.0.0.Alpha4 > > > When tried set dependsOnMethods param to @Test annotation in Metamer's ftests, get IllegalStateException thrown from MatrixConfigurator. > There aren't any other methods annotated by @Test with dependsOnMethods param, so its possible that this issue is in Metamer longer time without being discovered. > By debugging observed that list of methods set to be executed by TestRunner depends on this param. In other word, when set dependsOnMethods param to @Test annotation - this method (on which was this param set to annotation) doesn't appear in list of methods being executed (LinkedList methods attribute of MatrixConfigurator). > This attribute is initialized in method > public List intercept(List methodInstances, ITestContext context) > which is called directly from org.testng.TestRunner, which give param List methodInstances depending on dependsOnMethods param set to @Test annotation as well. > This behavior should be ok, since methods which are not depending on another else method should be executed first. > But what seems worse is that when run this again - for method anotated by @Test with param dependsOnMethod, then list of methods which going to be executed is empty - do no test method called. > And in case when all methods except one depends on another method, different exception is result of run testsuite: > Running TestSuite > org.apache.maven.surefire.booter.SurefireExecutionException: null; nested exception is java.lang.NullPointerException: null > java.lang.NullPointerException > at org.richfaces.tests.metamer.ftest.MetamerTestInfo.getConfigurationInfo(MetamerTestInfo.java:50) > at org.richfaces.tests.metamer.ftest.MetamerTestInfo.getConfigurationInfoInParenthesses(MetamerTestInfo.java:77) > at org.richfaces.tests.metamer.ftest.MetamerSeleniumLoggingTestListener.getMessage(MetamerSeleniumLoggingTestListener.java:35) > at org.jboss.test.selenium.listener.SeleniumLoggingTestListener.logStatus(SeleniumLoggingTestListener.java:82) > at org.jboss.test.selenium.listener.SeleniumLoggingTestListener.onTestFailure(SeleniumLoggingTestListener.java:55) > at org.testng.internal.Invoker.runTestListeners(Invoker.java:1634) > at org.testng.internal.Invoker.runTestListeners(Invoker.java:1618) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1101) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:137) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:121) > at org.testng.TestRunner.runWorkers(TestRunner.java:1030) > at org.testng.TestRunner.privateRun(TestRunner.java:709) > at org.testng.TestRunner.run(TestRunner.java:579) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:331) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:326) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:288) > at org.testng.SuiteRunner.run(SuiteRunner.java:193) > at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:910) > at org.testng.TestNG.runSuitesLocally(TestNG.java:879) > at org.testng.TestNG.run(TestNG.java:787) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:62) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:141) > at org.apache.maven.surefire.Surefire.run(Surefire.java:177) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) > So this should be issue related to TestNG itself (current version 5.12.1), tried 5.13, but the same behavior. > There is stack trace: > java.lang.IllegalStateException: can't find more configured methods > at org.richfaces.tests.metamer.ftest.MatrixConfigurator.configureMethod(MatrixConfigurator.java:150) > at org.richfaces.tests.metamer.ftest.MatrixConfigurator.beforeInvocation(MatrixConfigurator.java:101) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:62) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:141) > at org.apache.maven.surefire.Surefire.run(Surefire.java:177) > at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) > ... Removed 22 stack frames -- 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 From issues at jboss.org Tue Mar 11 08:55:11 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Tue, 11 Mar 2014 08:55:11 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3279) TestEditor#testReadonly wrong implementation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny resolved RFPL-3279. --------------------------------- Resolution: Done I rewrote the test to use JS api to verify if editor is readonly. Only master branch was changed since this concerns reworked editor for RF 5. > 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 From issues at jboss.org Tue Mar 11 10:43:13 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 11 Mar 2014 10:43:13 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3276) metamer: increase height of contextmenu and menugroup sample in accordion template In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3276: ------------------------------ Fix Version/s: 5.0.0.Alpha4 > 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 > Fix For: 5.0.0.Alpha4 > > > 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 From issues at jboss.org Tue Mar 11 10:43:14 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 11 Mar 2014 10:43:14 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3276) metamer: increase height of contextmenu and menugroup sample in accordion template In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek resolved RFPL-3276. ------------------------------- Resolution: Done > 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 > Fix For: 5.0.0.Alpha4 > > > 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 From issues at jboss.org Tue Mar 11 10:43:15 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 11 Mar 2014 10:43:15 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3277) metamer: reimplement hotkey test: testPreventDefaultFalse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek reassigned RFPL-3277: --------------------------------- Assignee: Ji?? ?tefek > 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 > Assignee: 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 From issues at jboss.org Wed Mar 12 04:41:10 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 12 Mar 2014 04:41:10 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3277) metamer: reimplement hotkey test: testPreventDefaultFalse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek resolved RFPL-3277. ------------------------------- Fix Version/s: 5.0.0.Alpha4 Resolution: Done > 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 > Assignee: Ji?? ?tefek > Fix For: 5.0.0.Alpha4 > > > 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 From issues at jboss.org Wed Mar 12 10:25:10 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 12 Mar 2014 10:25:10 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3278) Stabilize framework tests for RF5 on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RFPL-3278: ------------------------------ Summary: Stabilize framework tests for RF5 on WildFly (was: Stablilize framework tests for RF5 on WildFly) > Stabilize 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 From issues at jboss.org Mon Mar 17 05:14:10 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 17 Mar 2014 05:14:10 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3274) fix photoalbum smoke tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek resolved RFPL-3274. ------------------------------- Fix Version/s: 4.3.5 Resolution: Done > fix photoalbum smoke tests > -------------------------- > > Key: RFPL-3274 > URL: https://issues.jboss.org/browse/RFPL-3274 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Fix For: 4.3.5 > > > Fix photoalbum smoke test. Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/4.3/job/richfaces-4.3-photoalbum-ftest-eap61-win/ . -- 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 From issues at jboss.org Mon Mar 17 13:04:10 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 17 Mar 2014 13:04:10 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3275) metamer: fix editor tests/fragment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RFPL-3275: -------------------------------- Fix Version/s: 5.0.0.Alpha4 > 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 > Fix For: 5.0.0.Alpha4 > > > 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 From issues at jboss.org Mon Mar 17 13:04:11 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 17 Mar 2014 13:04:11 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3275) metamer: fix editor tests/fragment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RFPL-3275: -------------------------------- Assignee: Ji?? ?tefek > 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 > Assignee: Ji?? ?tefek > Fix For: 5.0.0.Alpha4 > > > 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 From issues at jboss.org Mon Mar 17 13:04:11 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 17 Mar 2014 13:04:11 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3275) metamer: fix editor tests/fragment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RFPL-3275: -------------------------------- Assignee: Matej Novotny (was: Ji?? ?tefek) > 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 > Assignee: Matej Novotny > Fix For: 5.0.0.Alpha4 > > > 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 From issues at jboss.org Fri Mar 21 05:00:10 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Fri, 21 Mar 2014 05:00:10 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3275) metamer: fix editor tests/fragment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12954859#comment-12954859 ] Matej Novotny commented on RFPL-3275: ------------------------------------- The problem was that the fix for this was applied only to RF 5 branch (it was done by JS instead of selenium - [link|https://github.com/richfaces/richfaces/blob/master/build/page-fragments/src/main/java/org/richfaces/fragment/editor/RichFacesEditor.java#L86]). I applied the same changes to RF 4 branches and the tests are now successful. > 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 > Assignee: Matej Novotny > Fix For: 5.0.0.Alpha4 > > > 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 From issues at jboss.org Fri Mar 21 05:18:10 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Fri, 21 Mar 2014 05:18:10 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3275) metamer: fix editor tests/fragment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny resolved RFPL-3275. --------------------------------- Resolution: Done > 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 > Assignee: Matej Novotny > Fix For: 5.0.0.Alpha4 > > > 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 From issues at jboss.org Mon Mar 24 06:35:12 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Mon, 24 Mar 2014 06:35:12 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-2257) Review test coverage of autocomplete In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12955446#comment-12955446 ] Matej Novotny commented on RFPL-2257: ------------------------------------- [~ppitonak] we are missing tests for most attributes of both versions of autocomplete - RF4 and RF5. I will create some tests to cover at least handlers and basic attributes for branch 4.3.x and then cherry-pick them to other branches. > Review test coverage of autocomplete > ------------------------------------- > > Key: RFPL-2257 > URL: https://issues.jboss.org/browse/RFPL-2257 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.2.2.Final > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Fix For: 5-Future > > > Review which attributes of rich:autocomplete are covered by tests and if needed, create new Se2 tests. > I couldn't find tests e.g. for: > * onclick and other handlers > * inputClass > * minChars > * style, styleClass > * ... -- 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 From issues at jboss.org Mon Mar 24 09:33:19 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 24 Mar 2014 09:33:19 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-2751) Metamer: rich:dropTarget: all tests fails within richCollapsibleSubTable template In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RFPL-2751: -------------------------------- Component/s: QE (was: testing) > Metamer: rich:dropTarget: all tests fails within richCollapsibleSubTable template > --------------------------------------------------------------------------------- > > Key: RFPL-2751 > URL: https://issues.jboss.org/browse/RFPL-2751 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.3.0.Final > Environment: accross containers, browser FF > Reporter: J?n Jamrich > Attachments: screenshot-dnd-dropTargetFailure.png > > > Run dropTarget tests (using webDriver) within all templates fails every time for richCollapsibleSubTable template, even in other templates can pass, and run this test only within richCollapsibleSubTable template passed too. > There is example job using jbas-71 container to simulate this behavior [1] > Analyzing screenshots/observing job during test using VNC found the ERROR status after drop event performed, while drop action not processed, so all tests fails on waiting for element created on drop accept handling method (it is bellow the drop area, and displays attributes of dropped object). > For more info see referenced job using jbas-71 and all templates [1] > [1] http://hudson.qa.jboss.com/hudson/view/RF-QE/job/richfaces-metamer-ftest--server-compatibility-dnd-jbas71/4/ -- 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 From issues at jboss.org Mon Mar 24 09:33:20 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 24 Mar 2014 09:33:20 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-2751) Metamer: rich:dropTarget: all tests fails within richCollapsibleSubTable template In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak resolved RFPL-2751. --------------------------------- Resolution: Out of Date Works fine in 4.3, 4.5 and 5.0 > Metamer: rich:dropTarget: all tests fails within richCollapsibleSubTable template > --------------------------------------------------------------------------------- > > Key: RFPL-2751 > URL: https://issues.jboss.org/browse/RFPL-2751 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.3.0.Final > Environment: accross containers, browser FF > Reporter: J?n Jamrich > Attachments: screenshot-dnd-dropTargetFailure.png > > > Run dropTarget tests (using webDriver) within all templates fails every time for richCollapsibleSubTable template, even in other templates can pass, and run this test only within richCollapsibleSubTable template passed too. > There is example job using jbas-71 container to simulate this behavior [1] > Analyzing screenshots/observing job during test using VNC found the ERROR status after drop event performed, while drop action not processed, so all tests fails on waiting for element created on drop accept handling method (it is bellow the drop area, and displays attributes of dropped object). > For more info see referenced job using jbas-71 and all templates [1] > [1] http://hudson.qa.jboss.com/hudson/view/RF-QE/job/richfaces-metamer-ftest--server-compatibility-dnd-jbas71/4/ -- 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 From issues at jboss.org Mon Mar 24 10:03:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 24 Mar 2014 10:03:13 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3280) Proof of Concept: Jenkins on OpenShift In-Reply-To: References: Message-ID: Pavol Pitonak created RFPL-3280: ----------------------------------- Summary: Proof of Concept: Jenkins on OpenShift Key: RFPL-3280 URL: https://issues.jboss.org/browse/RFPL-3280 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: QE Reporter: Pavol Pitonak Assignee: Pavol Pitonak Try to implement custom Jenkins master with 2 slaves on OpenShift usable for building RichFaces framework, documentation, demos and running unit and functional tests. -- 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 From issues at jboss.org Mon Mar 24 10:17:12 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 24 Mar 2014 10:17:12 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3280) Proof of Concept: Jenkins on OpenShift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12955638#comment-12955638 ] Pavol Pitonak commented on RFPL-3280: ------------------------------------- Jenkins was created on https://jenkins-richfaces.rhcloud.com/ There are these limitations: # Use doesn't have write access to his home directory which means that Maven can't use standard local repository (~/.m2/repository). Workaround is to create custom settings.xml in ~/app-root/data and set path to the local repository there or check the private repository checkbox in every build configuration. * Our functional tests need a web browser but user can't install packages (firefox, xvnc). Workaround could be to use a remote Selenium grid, e.g. SauceLabs. However, it's not clear how it would influence stability of test suite. * Every medium gear on OpenShift provides 1GB of disk space which is too little for storing .m2/repository. * Artifacts generated when building richfaces-qa repository are deployed to an internal Maven repository which means that e.g. Metamer tests cannot run on a slave unless whole repository had been built on the same slave. This could be worked around by using some shared disk but OpenShift doesn't provide such a functionality yet. > Proof of Concept: Jenkins on OpenShift > -------------------------------------- > > Key: RFPL-3280 > URL: https://issues.jboss.org/browse/RFPL-3280 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Pavol Pitonak > Assignee: Pavol Pitonak > > Try to implement custom Jenkins master with 2 slaves on OpenShift usable for building RichFaces framework, documentation, demos and running unit and functional tests. -- 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 From issues at jboss.org Tue Mar 25 05:52:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 25 Mar 2014 05:52:13 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3281) Test new implemetation of file upload In-Reply-To: References: Message-ID: Pavol Pitonak created RFPL-3281: ----------------------------------- Summary: Test new implemetation of file upload Key: RFPL-3281 URL: https://issues.jboss.org/browse/RFPL-3281 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: QE Affects Versions: 5.0.0.Alpha3 Reporter: Pavol Pitonak Assignee: Juraj H?ska The file upload component in RichFaces 5 was reimplemented. * Everything expected to work * Using Servlet 3.0 API for file uploads - won't work on Tomcat 6 * Files are sent through an XHR request (as opposed to the previous iframe approach) * Originally had to intercept the request early to get upload progress updates but now we monitor the upload progress on the client, so this is not needed -- 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 From issues at jboss.org Thu Mar 27 08:34:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 27 Mar 2014 08:34:13 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3281) Test new implemetation of file upload In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12956977#comment-12956977 ] Juraj H?ska commented on RFPL-3281: ----------------------------------- New implementation of fileUpload is in branch RF-13514-fileupload-progress-update > Test new implemetation of file upload > ------------------------------------- > > Key: RFPL-3281 > URL: https://issues.jboss.org/browse/RFPL-3281 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 5.0.0.Alpha3 > Reporter: Pavol Pitonak > Assignee: Juraj H?ska > > The file upload component in RichFaces 5 was reimplemented. > * Everything expected to work > * Using Servlet 3.0 API for file uploads - won't work on Tomcat 6 > * Files are sent through an XHR request (as opposed to the previous iframe approach) > * Originally had to intercept the request early to get upload progress updates > but now we monitor the upload progress on the client, so this is not needed -- 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 From issues at jboss.org Thu Mar 27 11:16:14 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 27 Mar 2014 11:16:14 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3281) Test new implemetation of file upload In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12957058#comment-12957058 ] Juraj H?ska commented on RFPL-3281: ----------------------------------- Please see [this|https://issues.jboss.org/browse/RF-13514?focusedCommentId=12957057&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12957057] comment for so far issues I have found on the new implementation of the {{fileUpload}}. > Test new implemetation of file upload > ------------------------------------- > > Key: RFPL-3281 > URL: https://issues.jboss.org/browse/RFPL-3281 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 5.0.0.Alpha3 > Reporter: Pavol Pitonak > Assignee: Juraj H?ska > > The file upload component in RichFaces 5 was reimplemented. > * Everything expected to work > * Using Servlet 3.0 API for file uploads - won't work on Tomcat 6 > * Files are sent through an XHR request (as opposed to the previous iframe approach) > * Originally had to intercept the request early to get upload progress updates > but now we monitor the upload progress on the client, so this is not needed -- 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 From issues at jboss.org Fri Mar 28 05:22:12 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 28 Mar 2014 05:22:12 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3036) Metamer enhancements for more effective work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RFPL-3036: ----------------------------------- Assignee: Juraj H?ska (was: Pavol Pitonak) > Metamer enhancements for more effective work > -------------------------------------------- > > Key: RFPL-3036 > URL: https://issues.jboss.org/browse/RFPL-3036 > Project: RichFaces Planning > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > We have discussed couple of enhancements to Metamer: > # put all components to the first page > # make a search input on the home page with automatic focus after page load ,which will be able to filter the components > # I am also thinking about making similar search box for attributes in the sample pages -- 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 From issues at jboss.org Fri Mar 28 05:24:14 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 28 Mar 2014 05:24:14 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-1870) QE Create new tests for attribute onlisthide/onlistshow of component inplace select In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RFPL-1870: ----------------------------------- Assignee: Matej Novotny (was: Pavol Pitonak) Matej, please investigate if it still a valid task. > QE Create new tests for attribute onlisthide/onlistshow of component inplace select > ----------------------------------------------------------------------------------- > > Key: RFPL-1870 > URL: https://issues.jboss.org/browse/RFPL-1870 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Fix For: 5-Tracking > > > Create new Selenium tests in Metamer for attribute onlisthide/onlistshow of component inplace select. -- 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 From issues at jboss.org Fri Mar 28 05:26:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 28 Mar 2014 05:26:13 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-2273) PoC: RushEye for Metamer tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RFPL-2273: ----------------------------------- Assignee: Juraj H?ska (was: Pavol Pitonak) > PoC: RushEye for Metamer tests > ------------------------------ > > Key: RFPL-2273 > URL: https://issues.jboss.org/browse/RFPL-2273 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Pavol Pitonak > Assignee: Juraj H?ska > Priority: Critical > > Try Jakub Dunia's RushEye Manager. > # Add group "screenshot" to about 20 tests in Metamer. Select only one test for one RichFaces component. Select tests which cause significant visual changes in components. > # Create a Jenkins job which will generate screenshots > {code} > mvn clean verify -Dtemplates=plain -Pjbossas-managed-7-1,screenshots > {code} > # Build RushEye Manager [1] and try to analyze at least two sets of images generated by Jenkins. > [1] https://github.com/cube88/arquillian-rusheye -- 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 From issues at jboss.org Fri Mar 28 05:29:07 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 28 Mar 2014 05:29:07 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-2258) Create a visual suite creating screenshots for selected components in Metamer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RFPL-2258: ----------------------------------- Assignee: Juraj H?ska (was: Pavol Pitonak) > Create a visual suite creating screenshots for selected components in Metamer > ----------------------------------------------------------------------------- > > Key: RFPL-2258 > URL: https://issues.jboss.org/browse/RFPL-2258 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Luk?? Fry? > Assignee: Juraj H?ska > > Jakub Dunja is working on creating the RushEye Manager, > which would take the set of screenshots, turn them into RushEye suite descriptor and run the test suite against second set of screenshots. > ---- > What we need is screenshots reflecting the state of components in two RF versions ({{4.1}} and {{4.2}}) to prove it works and see the real results of the tool. > The goals: > Create the tool to turn Selenium tests into suite of images. > Use the notes in the [Automated Visual Comparison of Browser Screen Captures|http://is.muni.cz/th/207442/fi_b/?lang=en] ([PDF|http://is.muni.cz/th/207442/fi_b/automated-testing-of-browser-screen-captures.pdf]) as a base. > ---- > Watch the [Forum Reference] for more information on the development. -- 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 From issues at jboss.org Fri Mar 28 05:30:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 28 Mar 2014 05:30:13 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-1049) Test for the component attributes list In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak resolved RFPL-1049. --------------------------------- Fix Version/s: (was: 5-Future) Resolution: Won't Fix > Test for the component attributes list > -------------------------------------- > > Key: RFPL-1049 > URL: https://issues.jboss.org/browse/RFPL-1049 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Luk?? Fry? > Assignee: Pavol Pitonak > Original Estimate: 1 day > Remaining Estimate: 1 day > > Currently we don't have the way how to found that the component attributes has changed (was added, changed values, etc.). > Implement mechanism which will each build check the list of attributes and compare it with predefined list. > This way we will be able to found attributes, which has been added or has been changed. -- 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 From issues at jboss.org Fri Mar 28 05:30:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 28 Mar 2014 05:30:13 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-941) Metamer - implement test's combination-space cutting using right template combination selection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak resolved RFPL-941. -------------------------------- Fix Version/s: (was: 5-Future) Resolution: Won't Fix > Metamer - implement test's combination-space cutting using right template combination selection > ----------------------------------------------------------------------------------------------- > > Key: RFPL-941 > URL: https://issues.jboss.org/browse/RFPL-941 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.0.0.Milestone4 > Reporter: Luk?? Fry? > Assignee: Pavol Pitonak > -- 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 From issues at jboss.org Fri Mar 28 08:54:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 28 Mar 2014 08:54:13 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3281) Test new implemetation of file upload In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12957333#comment-12957333 ] Juraj H?ska commented on RFPL-3281: ----------------------------------- Tests for new fileUpload are failing because of Graphene bug: ARQGRA-432 - Graphene {{guardAjax}} does not work with XHR2. > Test new implemetation of file upload > ------------------------------------- > > Key: RFPL-3281 > URL: https://issues.jboss.org/browse/RFPL-3281 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 5.0.0.Alpha3 > Reporter: Pavol Pitonak > Assignee: Juraj H?ska > > The file upload component in RichFaces 5 was reimplemented. > * Everything expected to work > * Using Servlet 3.0 API for file uploads - won't work on Tomcat 6 > * Files are sent through an XHR request (as opposed to the previous iframe approach) > * Originally had to intercept the request early to get upload progress updates > but now we monitor the upload progress on the client, so this is not needed -- 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 From issues at jboss.org Mon Mar 31 22:15:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 31 Mar 2014 22:15:13 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3282) Showcase failure 2014-03-31 In-Reply-To: References: Message-ID: Brian Leathem created RFPL-3282: ----------------------------------- Summary: Showcase failure 2014-03-31 Key: RFPL-3282 URL: https://issues.jboss.org/browse/RFPL-3282 Project: RichFaces Planning Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Leathem Showcase failed with an out-of-memory failure: {code} 2014/03/26 11:48:18,664 ERROR [org.apache.coyote.http11] (http-/127.6.77.1:8080-58) JBWEB003038: Error processing request: java.lang.OutOfMemoryError: Java heap space at org.apache.tomcat.util.buf.CharChunk.allocate(CharChunk.java:124) [jbossweb.jar:7.3.0.Final-redhat-2] at org.apache.tomcat.util.buf.CharChunk.(CharChunk.java:87) [jbossweb.jar:7.3.0.Final-redhat-2] at org.apache.catalina.connector.InputBuffer.(InputBuffer.java:171) [jbossweb.jar:7.3.0.Final-redhat-2] at org.apache.catalina.connector.InputBuffer.(InputBuffer.java:154) [jbossweb.jar:7.3.0.Final-redhat-2] at org.apache.catalina.connector.Request.(Request.java:295) [jbossweb.jar:7.3.0.Final-redhat-2] at org.apache.catalina.connector.Connector.createRequest(Connector.java:879) [jbossweb.jar:7.3.0.Final-redhat-2] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:295) [jbossweb.jar:7.3.0.Final-redhat-2] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb.jar:7.3.0.Final-redhat-2] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb.jar:7.3.0.Final-redhat-2] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb.jar:7.3.0.Final-redhat-2] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] {code} -- 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 From issues at jboss.org Mon Mar 31 22:23:14 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 31 Mar 2014 22:23:14 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3282) Showcase failure 2014-03-31 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12957941#comment-12957941 ] Brian Leathem commented on RFPL-3282: ------------------------------------- An automatic restart is recorded in the logs, but the showcase remains unresponsive. Checking the local jboss with curl yields a 404: {code} [showcase-richfaces.rhcloud.com 52ec0be35973ca57c9000064]\> curl -v $OPENSHIFT_JBOSSEAP_IP:$OPENSHIFT_JBOSSEAP_HTTP_PORT * About to connect() to 127.6.77.1 port 8080 (#0) * Trying 127.6.77.1... connected * Connected to 127.6.77.1 (127.6.77.1) port 8080 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.3.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2 > Host: 127.6.77.1:8080 > Accept: */* > < HTTP/1.1 404 Not Found < Server: Apache-Coyote/1.1 < Content-Length: 0 < Date: Tue, 01 Apr 2014 02:17:33 GMT < Connection: close < * Closing connection #0 {code} > Showcase failure 2014-03-31 > ---------------------------- > > Key: RFPL-3282 > URL: https://issues.jboss.org/browse/RFPL-3282 > Project: RichFaces Planning > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > > Showcase failed with an out-of-memory failure: > {code} > 2014/03/26 11:48:18,664 ERROR [org.apache.coyote.http11] (http-/127.6.77.1:8080-58) JBWEB003038: Error processing request: java.lang.OutOfMemoryError: Java heap space > at org.apache.tomcat.util.buf.CharChunk.allocate(CharChunk.java:124) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.tomcat.util.buf.CharChunk.(CharChunk.java:87) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.InputBuffer.(InputBuffer.java:171) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.InputBuffer.(InputBuffer.java:154) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.Request.(Request.java:295) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.Connector.createRequest(Connector.java:879) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:295) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb.jar:7.3.0.Final-redhat-2] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > {code} -- 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 From issues at jboss.org Mon Mar 31 22:25:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 31 Mar 2014 22:25:13 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3282) Showcase failure 2014-03-31 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12957944#comment-12957944 ] Brian Leathem commented on RFPL-3282: ------------------------------------- Restarting the app with: {code} rhc app restart -l richfaces at redhat.com -a showcase {code} The _server.log_ file does not indicate any showcase deployment. I'll next try re-deploying the application. > Showcase failure 2014-03-31 > ---------------------------- > > Key: RFPL-3282 > URL: https://issues.jboss.org/browse/RFPL-3282 > Project: RichFaces Planning > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > > Showcase failed with an out-of-memory failure: > {code} > 2014/03/26 11:48:18,664 ERROR [org.apache.coyote.http11] (http-/127.6.77.1:8080-58) JBWEB003038: Error processing request: java.lang.OutOfMemoryError: Java heap space > at org.apache.tomcat.util.buf.CharChunk.allocate(CharChunk.java:124) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.tomcat.util.buf.CharChunk.(CharChunk.java:87) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.InputBuffer.(InputBuffer.java:171) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.InputBuffer.(InputBuffer.java:154) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.Request.(Request.java:295) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.Connector.createRequest(Connector.java:879) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:295) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb.jar:7.3.0.Final-redhat-2] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > {code} -- 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 From issues at jboss.org Mon Mar 31 23:15:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 31 Mar 2014 23:15:13 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3282) Showcase failure 2014-03-31 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12957945#comment-12957945 ] Brian Leathem commented on RFPL-3282: ------------------------------------- Looking in the deployments folder I can see the app got undeployed. Simply removing the undeployed marker file and restarting the app was sufficient to trigger a re-deploy: {code} [showcase-richfaces.rhcloud.com 52ec0be35973ca57c9000064]\> ls jbosseap/standalone/deployments/ ROOT.war ROOT.war.undeployed [showcase-richfaces.rhcloud.com 52ec0be35973ca57c9000064]\> rm jbosseap/standalone/deployments/ROOT.war.undeployed {code} > Showcase failure 2014-03-31 > ---------------------------- > > Key: RFPL-3282 > URL: https://issues.jboss.org/browse/RFPL-3282 > Project: RichFaces Planning > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > > Showcase failed with an out-of-memory failure: > {code} > 2014/03/26 11:48:18,664 ERROR [org.apache.coyote.http11] (http-/127.6.77.1:8080-58) JBWEB003038: Error processing request: java.lang.OutOfMemoryError: Java heap space > at org.apache.tomcat.util.buf.CharChunk.allocate(CharChunk.java:124) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.tomcat.util.buf.CharChunk.(CharChunk.java:87) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.InputBuffer.(InputBuffer.java:171) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.InputBuffer.(InputBuffer.java:154) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.Request.(Request.java:295) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.Connector.createRequest(Connector.java:879) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:295) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb.jar:7.3.0.Final-redhat-2] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > {code} -- 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 From issues at jboss.org Mon Mar 31 23:15:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 31 Mar 2014 23:15:13 -0400 (EDT) Subject: [richfaces-planning-issues] [JBoss JIRA] (RFPL-3282) Showcase failure 2014-03-31 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RFPL-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RFPL-3282. --------------------------------- Assignee: Brian Leathem Resolution: Done > Showcase failure 2014-03-31 > ---------------------------- > > Key: RFPL-3282 > URL: https://issues.jboss.org/browse/RFPL-3282 > Project: RichFaces Planning > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > > Showcase failed with an out-of-memory failure: > {code} > 2014/03/26 11:48:18,664 ERROR [org.apache.coyote.http11] (http-/127.6.77.1:8080-58) JBWEB003038: Error processing request: java.lang.OutOfMemoryError: Java heap space > at org.apache.tomcat.util.buf.CharChunk.allocate(CharChunk.java:124) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.tomcat.util.buf.CharChunk.(CharChunk.java:87) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.InputBuffer.(InputBuffer.java:171) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.InputBuffer.(InputBuffer.java:154) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.Request.(Request.java:295) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.Connector.createRequest(Connector.java:879) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:295) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb.jar:7.3.0.Final-redhat-2] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb.jar:7.3.0.Final-redhat-2] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > {code} -- 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