| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Priority | Type | TC State | Feature | Description | TestID | Test Name | Scenario | Precondition | Steps | Expected Result | Actual Result | TC Status | Last Run | Defect ID |
2 | Automated | Design | Application/SEO-WCAG | Verify there's a no-index meta tag - I don't want the SPA indexed on github pages yet. | tbd | Not Run | |||||||||
3 | Automated | Design | Application/DOM | Verify every chart has an element to render in by #ID | Verify every chart has an element to render in by #ID | Not Run | |||||||||
4 | Automated | Ready | Application/SEO-WCAG | Verify page loads with a Title tag for SEO. | <title> tag presence. | Page loads with non-empty title tag. | Page loads with "Blood..." static tag. | Pass | 2026-03-22 | ||||||
5 | Manual | Ready | UI/User Agent x-browser | Verify page <divs>&<sections> render sanely according to z-index (e.g. header should not draw on top of error banner, obscuring it) in supported desktop+mobile+OS combinations. | <div> .css layer orders x-browser | A warning banner has been triggered. | In IOS/Safari, OS X Safari, Windows/Chrome, Android Chrome: - Inject showGlobalErrorBanner("test") in DevTools. - Open app and scoll up and down. | - Warning banner should draw over header. - charts should not draw over header or warning banner. | Pases, but need OS X test machine or maestro/appium test harness to complete test. | Blocked | 13 | ||||
6 | Manual | Ready | UI/User Agent x-browser | Verify charts that require horizontal scrolling and contain tooltip markers can be scrolled and tooltips triggered - gauge the intended actions can be performed "without a fight". | Charts needing horizontal scrolling not impeded by tooltips. | In IOS/Safari, OS X Safari, Windows/Chrome, Android Chrome: - Load dashboard, locate heatmap chart. - attempt tooltip trigger. - attempt horizontal scrolling - nb for tablets, utilize Dev Tools dimension sizing feature | - Mobile should not have tooltips and be able to be horizontally scrolled - Tablet should have tooltips and horizontal scrolling not impeded. - Desktop should have tooltips, no horizonal scrolling required. | Tooltips are disabled in mobile devices and scrolling is possible. Tooltips and scrolling function in tablets. No horizontal scrolling on desktop and tooltips can be triggered without "a fight". | Pass | ||||||
7 | Manual | Ready | UI/User Agent x-browser | Verify tooltips can be triggered on mobile devices (touch-gesture precision check) - gauge the intended action in the UI. | Mobile markers touch-gesture precision (tooltips). | In IOS and Android: - load dashboard and click data markers on all charts that react with a tooltip. | User can trigger tooltips with a marker touch. | Pulse and Sys/Dia need some fine tuning - it is difficult to trigger tooltips. | Fail | 2026-03-19 | 42 | ||||
8 | Manual | Ready | UI/User Agent x-browser | Verify charts do not overflow parent containers in supported desktop+mobile+OS combinations. | Charts fill, stretch height and width, and do not overflow UI container boxes. | In IOS/Safari, OS X Safari, Windows/Chrome, Android Chrome: - View dashboard, and observe single charts AND horizontal siblings. | Charts to not overflow their parent containers. Charts having a horizontal sibling stretch to have equal heights. | Pases, but need OS X test machine or maestro/appium test harness to complete test. | Blocked | 13 | |||||
9 | Manual | Ready | UI/User Agent x-browser | Headed browsers with javascript disabled. (incl. selenium, google/bing bots & playwrite which execute javascript) | Human/Bots/Automation user agents with javascript disabled receive warning. | Browser client does not support javascript. | - Disable javascript in browser - Then load page in new tab. | - Error banner warning is visble notifying javascript must be turned on to proceed. - UI layout appears with no charts or calculated data rendered. | Banner appears. UI framework intact w/ no charts or data rendered. | Pass | 2026-03-19 | ||||
10 | Manual | Design | UI/User Agent x-browser | Headless browsers don't support javascript - these are the ones that will be tricky to test - e.g. the pre-rendered images that sending links to someone in txt/messenger. | Headless browsers w/no javascript support. | FB&X crawlers/AI LLMs/Lynx/Discord/paranoid chrome&firefox users. | Blocked | 38 | |||||||
11 | Manual | Ready | UI/State | Typical design where the user sees a "loading" animation while an application is working on an api async/await. | Verify data retrieval "loading" animation functions. | There is a lag of some sort while fecthing the data from github (or database API eventually.) | - Execute showLoadingState() in DevTools. - Observe browser Window. | Semi-transparent overlay appears with rotating indicator asking user to wait (for async to complete). | Overaly appears, spinner rotates. | Pass | 2026-03-18 | ||||
12 | Manual | Ready | UI/Error Handling | No runtime errors occur, therefore banner should not be visible to users. | Error banner does not fire (Happy Path). | - Load dashboard in browser - Observe top of page | No error banner <div> is present. | Banner not present. | Pass | 2026-03-18 | |||||
13 | Manual | Ready | UI/Error Handling | Error banner fires for any Application runtime error. | Error banner fires for any application runtime error. | - Generate any Application error handling scenario - load dashboard and observe error banner <div> location. | Error banner is present and contains text equivalent to what was output in console.log. | Banner is present. | Pass | 2026-03-18 | |||||
14 | Automated | Design | Application/Slide-Overs | write parameterized test to click each info-tooltip, make sure the slider opens, and displays the right ./src/docLibrary.js content. | Info icons trigger correct side-slide content | Not Run | |||||||||
15 | Manual | Ready | Frontend/Slide-Overs | Verify slide-overs render sanely with z-index in supported desktop+mobile+OS combinations. | Slide-over open/close x-browser | In IOS/Safari, OS X Safari, Windows/Chrome, Android Chrome: - click each info tooltip button on page - observe slide-out - click close button or semi-transparent page area | - Each slide-over opens at half-page width in desktop or 100% width in mobile - content loads without errors - close button makes slide-over retreat. | Pases, but need OS X test machine or maestro/appium test harness to complete test. | Blocked | 2026-03-18 | 13 | ||||
16 | Automated | Ready | Application/Error Handling | Verify system generates an error if the user is attempting to view data from a malformed .json data source, causing the parser to panic and whole file to fail. | Log is generated if application data source contains a fatal syntax error. | .json data source contains syntax error | Synthesize a malformed record where the application retrieves data from: - Remove a Sys key value pair from bp_readings.json - Hard reload page and observe UI. | Console.log entry generated with "?". | Passes, however a code change is needed - opened Issue # 39 | Pass | 39 | ||||
17 | Automated | Ready | Application/Error Handling | The data source or file is simply not reachable. | Log is generated if application data source is unreachable. | Missing data.json file | Rename or delete bp_readings.json Load dashboard and observe UI. | Console.log entry generated with "?". | Passes, however a code change is needed - opened Issue # 39 | Pass | 39 | ||||
18 | Automated | Ready | Application/Error Handling | The data source returns something, but it is an empty array containing 0 records. | Log is generated if application data source is incomplete. | Empty data.json array | delete all data within .json, leaving "[]" object. Load dashboard and observe UI | Console.log entry generated with "?". | Passes, however a code change is needed - opened Issue # 39 | Pass | 39 | ||||
19 | Automated | Design | Application/Error Handling | .json is ready before the DOM is. Gemini said I handle this, but I don't know where the code is, how to trigger, and how it's handled. | tbd | Not Run | |||||||||
20 | Automated | Design | Application/Error Handling | deconstruct utils/errorhandling.js for cases and make a checklist matrix for documentation plus what's missing; verify banner is triggered for all of them. | tbd | Not Run | |||||||||
21 | Automated | Design | Application/Error Handling | How does AbortController() currently in use work regarding timeouts? Does it console.warn and should it errorbanner the user? | tbd | Not Run | |||||||||
22 | Automated | Design | Application/Data Integrity | Check how non number / utf8 characters affect calculations. Record should be dropped and not make it to charts. | tbd | Not Run | |||||||||
23 | Automated | Design | Application/Data Integrity | Verify what happens if user enters 2 readings in 1 day but workday is y in 1 and n in the other | tbd | Not Run | |||||||||
24 | Manual | Design | Application/Cross Chart Verification | Verify Last Reading is consistent in end of continuous series of dates, and single labels across dashbaord. | Verify consistent last reading across charts. | Pass | 2026-03-123 | 46 | |||||||
25 | Manual | Design | Application/Cross Chart Verification | Verify Averages. This is tricky - I made a conscious decision and wrote it down *somewhere* that averages didn't have to match up. I think it was box&whisker because they dont jive with the summary cards. | Verify averages are consistent across charts. | Load Dashboard: - Compare last tooltip in 7-day Sys+Dia lines to header cards - | Consider rounding and decimal place usage while judging accuracy. | Not Run | |||||||
26 | Manual | Design | Application/Cross Chart Verification | Write test cases for the "Leung" rules highlights in the top cards and raw table conditional formatting. It's a lot of test steps so automate this. I'll have to learn how to inject test data into the load. | 47 |