Details
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
Field | Original Value | New Value |
---|---|---|
Assignee | Carmen Cristurean [ ccristurean ] |
Link | This issue is duplicated by ICE-8437 [ ICE-8437 ] |
Assignee | Carmen Cristurean [ ccristurean ] | Cruz Miraback [ cmiraback ] |
Summary | ace:dataTable rewrite ace:progressBar test cases not to use getter-incremented progress | ace regressions - rewrite ace:progressBar test cases not to use getter-incremented progress |
Salesforce Case | [] |
Salesforce Case | [] | |
Component/s | QA [ 10016 ] | |
Fix Version/s | 3.2 [ 10338 ] | |
Assignee Priority | P2 |
Salesforce Case | [] | |
Fix Version/s | EE-3.0.0.GA_P01 [ 10327 ] | |
Fix Version/s | 3.2 [ 10338 ] |
Salesforce Case | [] | |
Fix Version/s | 3.2 [ 10338 ] | |
Fix Version/s | EE-3.0.0.GA_P01 [ 10327 ] |
Assignee Priority | P2 [ 10011 ] | P1 [ 10010 ] |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Assignee Priority | P1 [ 10010 ] |