[UI] Summary Table

[amehta-scottlogic]

Acceptance Criteria

• Summary page shows a table which has measurements/forecast data for all locations where measurements exist
• All pollutant values should be shown in ug/m3
• Overall AQI value should be shown as well as difference
• Table should be sorted in order of worst offenders desc - if equal positive comes first
• ag-grid is to round up each value to one decimal place

Test Checklist:

• [x] Test Analysis & discussion with developer
• [x] Write Test Cases / Charters
• [x] Test Cases & Charters Reviewed
• [ ] Test Cases Executed
• [ ] Test Charters Executed
• [x] Regression tests executed
• [ ] Automation Tests added to project

[mnyamunda-scottlogic]

Test Analysis.

Front landing page. The first thing user will see.

• Verify that pollutants are shown accurately within UI unit wise ug/m3
• Verify worst offenders are sorted correctly (DESC). This should be the highest delta between forecast and in-situ. Can be something like the next rows value must be equal to or lower than the row above.
• Lighthouse accessibility test should pass at threshold 90
• Verify that information shown matches that of the database. We can seed data or mock an API call to make sure we get the same thing back each time. This is because we cannot guarantee that the specific city will actually have any pollutant data attacked to it
• Verify all locations with data are displayed
• Verify locations with no data are not displayed.

Charter Ideas

• Using Light house to explore possible areas for improvement
• Exploring responsiveness with different viewports to discover possible screen resolution issues
• Exploring filter functionality in UI to catch possible issues (Using Heuristics cheat sheet?)

[mnyamunda-scottlogic]

Notes: Column starts out unevenly spaced. May need a default width which can later be manually spaced by user? (depends on screen size)

• When there are no matches on query, there is no message that tells the user the case. e.g. "there is currently no data for Harare"

• User can truncate the columns as shown below? Should they have a truncation limit?

• Horizontal scroll bar is hidden until the user reaches the button of the list or scrolls outside of the table.

• Refreshing the screen doesn't hold state of previous column widths

• Lighthouse run as of 19/06/2024

• Purple text on new entries, should this rest once new data comes in? link wise?

[mwalker-scottlogic]

forecast_api_seeded_data_tests.py, forecast_api_validation_tests.py, cams_known_grib_test.py, forecast_calibration_tests.py & open_aq_etl_tests.py tests all passed.

Executed manual test cases, had to make some changes to test assertions, but expected behaviour was observed