Details
Task
Major
Description
The getter-incremented configuration currently used in the progressBar isn't a sensible use case to test for, considering that there are many reason that getters may be run more than once per life cycle, or outside of the intended scope of effects; like as discovered during testing, in @all ace:ajax renders.
My suggestion would be that the value of the progressBar be a calculation showing the proportion of time expired out of an arbitrary 30s interval begun when some button is clicked.
My suggestion would be that the value of the progressBar be a calculation showing the proportion of time expired out of an arbitrary 30s interval begun when some button is clicked.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Assigning to Cruz to investigate and update the test application.
Show
Carmen Cristurean
added a comment - Assigning to Cruz to investigate and update the test application.
Committed example, at revision 32476, of how tests should work to avoid fixed increments when calling the getter. Assigning back to Cruz.
Show
Arturo Zambrano
added a comment - - edited Committed example, at revision 32476, of how tests should work to avoid fixed increments when calling the getter. Assigning back to Cruz.
I've completed updating the tests using the provided example, as well as adjusting some of the scripts. Tests are located at http://server.ice:8888/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Nightly/progressBar.
Show
Cruz Miraback
added a comment - - edited I've completed updating the tests using the provided example, as well as adjusting some of the scripts. Tests are located at http://server.ice:8888/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Nightly/progressBar .
Assigning to Carmen for QA delegation.