February 2014 - richfaces-planning-issues

[JBoss JIRA] (RFPL-3269) RF5 Editor: Initial QE Tasks

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RFPL-3269?page=com.atlassian.jira.plugin.... ] Matej Novotny commented on RFPL-3269: ------------------------------------- JS tests are created and pull request was sent - [link|https://github.com/richwidgets/richwidgets/pull/186]. There is an [issue|https://github.com/richwidgets/richwidgets/issues/187] with toolbar due to which some tests have yet to be ignored. > RF5 Editor: Initial QE Tasks > ---------------------------- > > Key: RFPL-3269 > URL: https://issues.jboss.org/browse/RFPL-3269 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Priority: Blocker > Fix For: 5.0.0.Alpha4 > > > # review components - widget, JSF component, see demos and dev examples > # create JavaScript tests for component > # create/update Jenkins job(s) to run JavaScript tests continuously > # add component to Metamer (on feature branch as long as it is in sandbox) > # create/update page fragment if it makes sense > # create/update framework tests for component for each component's attribute and for each major feature > # create Metamer tests for those use-cases requiring templates > # review documentation - JavaDoc, VDL doc, Developer Guide, Component Reference > # update Migration Guide https://github.com/richfaces/richfaces/wiki/RichFaces-5-Migration-Guide > Link all found issues in component to this issue. -- 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-3274) fix photoalbum smoke tests

by Jiří Štefek (JIRA)

Jiří Štefek created RFPL-3274: --------------------------------- Summary: 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 photoalbum smoke test. Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/4.3/... . -- 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-3273) check the results of stateless views tests

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RFPL-3273?page=com.atlassian.jira.plugin.... ] Jiří Štefek updated RFPL-3273: ------------------------------ Description: Check results from job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/... and report RF issues. > check the results of stateless views tests > ------------------------------------------ > > Key: RFPL-3273 > URL: https://issues.jboss.org/browse/RFPL-3273 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Jiří Štefek > Assignee: Jiří Štefek > > Check results from job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/... and report RF issues. -- 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-3273) check the results of stateless views tests

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RFPL-3273?page=com.atlassian.jira.plugin.... ] Jiří Štefek updated RFPL-3273: ------------------------------ Summary: check the results of stateless views tests (was: check the results from tatelessviews tests) > check the results of stateless views tests > ------------------------------------------ > > Key: RFPL-3273 > URL: https://issues.jboss.org/browse/RFPL-3273 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Jiří Štefek > -- 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-3273) check the results of stateless views tests

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RFPL-3273?page=com.atlassian.jira.plugin.... ] Jiří Štefek reassigned RFPL-3273: --------------------------------- Assignee: Jiří Štefek > check the results of stateless views tests > ------------------------------------------ > > Key: RFPL-3273 > URL: https://issues.jboss.org/browse/RFPL-3273 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Jiří Štefek > Assignee: Jiří Štefek > -- 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-3273) check the results from tatelessviews tests

by Jiří Štefek (JIRA)

Jiří Štefek created RFPL-3273: --------------------------------- Summary: check the results from tatelessviews tests Key: RFPL-3273 URL: https://issues.jboss.org/browse/RFPL-3273 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jiří Štefek -- 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-3264) Create tests for @FlowScoped annotation

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-3264?page=com.atlassian.jira.plugin.... ] Brian Leathem commented on RFPL-3264: ------------------------------------- All we really need to do is test that our components (particularly our stateful ones and ajax heavy-ones) work as expected with Flowscoped backing beans. Eg. the tab component, EDT, etc. These don't need to be automated tests, smoke testing should be sufficient. If any problems arise we can drill down further with automated tests. We should be able to take an existing sample and convert some of the beans to flow scoped and see that it works. Perhaps metamer, the showcase, or maybe the photoalbum demo if we need something with a workflow. > Create tests for @FlowScoped annotation > --------------------------------------- > > Key: RFPL-3264 > URL: https://issues.jboss.org/browse/RFPL-3264 > Project: RichFaces Planning > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: QE > Reporter: Matej Novotny > Assignee: Matej Novotny > Labels: jsf22 > > Based on RFPL-2506, we need to create tests to verify that our components work correctly with @FlowScoped annotation introduced in JSF 2.2. > As for test creation it would be possible to reuse a wizard use-case in Showcase (r:togglePanel - Wizard creation), or any other similar scenario. > For more information about @FlowScoped in JSF 2.2, visit this [page|http://jdevelopment.nl/jsf-22/#730]. -- 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 Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RFPL-3263?page=com.atlassian.jira.plugin.... ] Matej Novotny commented on RFPL-3263: ------------------------------------- I have created a simple test which has both ways of adding a pass-though attribute and tests the mark-up (presence of att) and also the basic functionality to ensure it is not affected. I have placed this into a separate [branch|https://github.com/richfaces/richfaces/tree/RFPL-3263] under RF 5, also I already sent a [pull request| https://github.com/richfaces/richfaces/pull/82]. > 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-Tracking > > > 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

[JBoss JIRA] (RFPL-3264) Create tests for @FlowScoped annotation

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RFPL-3264?page=com.atlassian.jira.plugin.... ] Matej Novotny edited comment on RFPL-3264 at 2/24/14 8:24 AM: -------------------------------------------------------------- [~bleathem] I was looking into this a bit deeper and I am not sure what should be tested. The point of the FlowScoped bean is to preserve bean state from the beginning of the flow to the end. If we add any component into this flow, how do we test it? I mean the component inside the flow can surely see the bean state (that would a JSF issue not ours) and then it can react appropriately as if it was connected to any other bean. And even if we decided to create tests, what components should we test? We surely cannot test all of them. Most used pattern for flows is something as an e-shop - several pages connected together allowing user to fill out required information and proceed to next page. As for content of such page, it can be anything. I might be mistaken so please correct me, but atm I cannot see clearly what is here to test from RF point of view. was (Author: manovotn): [~bleathem]] I was looking into this a bit deeper and I am not sure what should be tested. The point of the FlowScoped bean is to preserve bean state from the beginning of the flow to the end. If we add any component into this flow, how do we test it? I mean the component inside the flow can surely see the bean state (that would a JSF issue not ours) and then it can react appropriately as if it was connected to any other bean. And even if we decided to create tests, what components should we test? We surely cannot test all of them. Most used pattern for flows is something as an e-shop - several pages connected together allowing user to fill out required information and proceed to next page. As for content of such page, it can be anything. I might be mistaken so please correct me, but atm I cannot see clearly what is here to test from RF point of view. > Create tests for @FlowScoped annotation > --------------------------------------- > > Key: RFPL-3264 > URL: https://issues.jboss.org/browse/RFPL-3264 > Project: RichFaces Planning > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: QE > Reporter: Matej Novotny > Assignee: Matej Novotny > Labels: jsf22 > > Based on RFPL-2506, we need to create tests to verify that our components work correctly with @FlowScoped annotation introduced in JSF 2.2. > As for test creation it would be possible to reuse a wizard use-case in Showcase (r:togglePanel - Wizard creation), or any other similar scenario. > For more information about @FlowScoped in JSF 2.2, visit this [page|http://jdevelopment.nl/jsf-22/#730]. -- 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-3264) Create tests for @FlowScoped annotation

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RFPL-3264?page=com.atlassian.jira.plugin.... ] Matej Novotny commented on RFPL-3264: ------------------------------------- [~bleathem]] I was looking into this a bit deeper and I am not sure what should be tested. The point of the FlowScoped bean is to preserve bean state from the beginning of the flow to the end. If we add any component into this flow, how do we test it? I mean the component inside the flow can surely see the bean state (that would a JSF issue not ours) and then it can react appropriately as if it was connected to any other bean. And even if we decided to create tests, what components should we test? We surely cannot test all of them. Most used pattern for flows is something as an e-shop - several pages connected together allowing user to fill out required information and proceed to next page. As for content of such page, it can be anything. I might be mistaken so please correct me, but atm I cannot see clearly what is here to test from RF point of view. > Create tests for @FlowScoped annotation > --------------------------------------- > > Key: RFPL-3264 > URL: https://issues.jboss.org/browse/RFPL-3264 > Project: RichFaces Planning > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: QE > Reporter: Matej Novotny > Assignee: Matej Novotny > Labels: jsf22 > > Based on RFPL-2506, we need to create tests to verify that our components work correctly with @FlowScoped annotation introduced in JSF 2.2. > As for test creation it would be possible to reuse a wizard use-case in Showcase (r:togglePanel - Wizard creation), or any other similar scenario. > For more information about @FlowScoped in JSF 2.2, visit this [page|http://jdevelopment.nl/jsf-22/#730]. -- 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 February 2014