You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, we are manually running through the following manual test cases to ensure things are working properly(the list may change overtime)
npm start runs and loads code into the browser window automatically.
Browser window should show the expected test pattern.
Browser refresh reloads the view.
Browser window should show Input widgets at top: filename, start bin, left and right buttons, path name, position, jump button, Use Vertical Compression, Row Height, Column Width.
Browser window starts populated with a graphic showing the current data.
Light grey blocks for coverage (shouldn't be everywhere). Dark grey connectors in between Components (light grey background boxes).
Links appear as colorful arrows immediately above the Component boxes.
Link Color matches Box Color in the Column immediately below either end of the link.
Links horizontal runs stack up neatly without overlapping (broken in current screenshot).
Mouse over Link and it changes to black.
Click Orphan Link (only one small arrow). View should jump to corresponding section with the other side of the link and matching color.
Matching link is visually highlighted (#6 not implemented yet).
Clicking on the newly highlighted link should take you back to precisely where you came from (2-way link travel) with your orphan link centered in the view.
Mouseover cells (grey blocks) should show e.g. "Path_name: 2365-27289. Coverage: 0.23, Inversion: 0.0". Mouseovers should be different for each cell. Mouseover disappears when not over cell.
We can always automate that and check that using some end-to-end testing framework like cypress and let the linter do all the important tests for us in CI when someone submits a PR, that way the reviewer's work is reduced to reviewing other aspects of the code like checking logic errors, or improving code structure.
The text was updated successfully, but these errors were encountered:
@josiahseaman you can assign this to me to research and add basic end-to-end testing(if possible) for this project. IMHO it will make our work easier. Wdyt?
Description
Right now, we are manually running through the following manual test cases to ensure things are working properly(the list may change overtime)
npm start
runs and loads code into the browser window automatically.We can always automate that and check that using some end-to-end testing framework like cypress and let the linter do all the important tests for us in CI when someone submits a PR, that way the reviewer's work is reduced to reviewing other aspects of the code like checking logic errors, or improving code structure.
The text was updated successfully, but these errors were encountered: