Bug 1564136 - [QEDevCollab] C&U: discrepancy in rounding of data for Graphs and Table causing automation failures
Summary: [QEDevCollab] C&U: discrepancy in rounding of data for Graphs and Table causi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.10.0
Assignee: Robin Knaur
QA Contact: Nikhil Dhandre
URL:
Whiteboard:
Depends On:
Blocks: 1578972
TreeView+ depends on / blocked
 
Reported: 2018-04-05 12:45 UTC by Nikhil Dhandre
Modified: 2019-02-11 13:58 UTC (History)
6 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1578972 (view as bug list)
Environment:
Last Closed: 2019-02-11 13:58:46 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Network IO screenshot (108.09 KB, image/png)
2018-04-05 12:45 UTC, Nikhil Dhandre
no flags Details

Description Nikhil Dhandre 2018-04-05 12:45:40 UTC
Created attachment 1417685 [details]
Network IO screenshot

Description of problem:
----------------------
I am reading graph data from tooltip of c3 graphs which is normally round to two decimal places but the table is rounded to one decimal place. why is the discrepancy between rounding of data for graphs compared to tables? Due to one decimal rounding, we are losing smaller data.


Affected form location:
-----------------------
All C&U graphs and tables.


Expected results:
----------------
For graph and table rounding should be same. It's better to go with two decimal places for both graph and respective table, so the customer will not face any confusion for smaller data reading on graph and table also automation will run fine.


Additional info:
----------------
- Attaching automation failure cause[0], please check line no. 26 where table reading is 2.8 and graph reading is 2.85. automation rounding graph reading to one decimal place so it's become 2.9 result assertion error.
 
- For smaller data like 0.0x kbps [1]. graph showing it but table showing it as zero. we are losing data here.

- In Network I/O screenshot[2], data is 0.04 kbps but due to one decimal place rounding table showing it as zero.


[0] http://pastebin.test.redhat.com/571071
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1513390

Comment 11 CFME Bot 2018-05-11 08:02:13 UTC
New commit detected on ManageIQ/manageiq-ui-classic/master:

https://github.com/ManageIQ/manageiq-ui-classic/commit/b3e56cc78f08162aeaf8c41ab18bd20d043c8653
commit b3e56cc78f08162aeaf8c41ab18bd20d043c8653
Author:     PanSpagetka <rknaur>
AuthorDate: Fri Apr 20 07:34:19 2018 -0400
Commit:     PanSpagetka <rknaur>
CommitDate: Fri Apr 20 07:34:19 2018 -0400

    Chart tooltips should match table
    https://bugzilla.redhat.com/show_bug.cgi?id=1564136

 app/assets/javascripts/miq_application.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comment 13 Nikhil Dhandre 2018-08-02 09:19:22 UTC
Tested on Version 5.10.0.6.20180725145922_d299ff5 with Vsphere.


Note You need to log in before you can comment on or make changes to this bug.