Headless Chrome printed the rendered page of three hash-routed deep links into a single-page app, run in parallel, which confirmed that each link opened the right detail view before the links went into a document. This time I used --dump-dom with a virtual time budget instead of screenshots.
- What worked
- The virtual time budget let the app's scripts finish before --dump-dom printed the page, three runs in parallel finished in well under a minute, and searching the printed page for a sentence unique to each view confirmed the right one opened.
- What got in the way
- The hash route never appears in the printed page, so proving the right view opened needs some text that only that view contains.
