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
Nils Lundquist
created issue -
Nils Lundquist
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Carmen Cristurean [ ccristurean ] |
Nils Lundquist
made changes -
Link | This issue is duplicated by ICE-8437 [ ICE-8437 ] |
Carmen Cristurean
made changes -
Assignee | Carmen Cristurean [ ccristurean ] | Cruz Miraback [ cmiraback ] |
Nils Lundquist
made changes -
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 | [] |
Ken Fyten
made changes -
Salesforce Case | [] | |
Component/s | QA [ 10016 ] | |
Fix Version/s | 3.2 [ 10338 ] | |
Assignee Priority | P2 |
Ken Fyten
made changes -
Salesforce Case | [] | |
Fix Version/s | EE-3.0.0.GA_P01 [ 10327 ] | |
Fix Version/s | 3.2 [ 10338 ] |
Ken Fyten
made changes -
Salesforce Case | [] | |
Fix Version/s | 3.2 [ 10338 ] | |
Fix Version/s | EE-3.0.0.GA_P01 [ 10327 ] |
Migration
made changes -
Assignee Priority | P2 [ 10011 ] | P1 [ 10010 ] |
Migration
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Assignee Priority | P1 [ 10010 ] |
Assigning to Carmen for QA delegation.