Implement client-side rendering (CSR) detection in QA#992
Draft
Implement client-side rendering (CSR) detection in QA#992
Conversation
adds option to analyze replayed html content to detect csr clues such as framework indicators, hydration data, web components, and dom manipulation patterns to identify client-side rendered pages will follow with text analysis using & not using additional page resources
emma-sg
force-pushed
the
qa-csr-clues-and-text-compare
branch
from
ba2edf1 to
e40d96f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds option (
--qaDetectClientSideRendering) to analyze replayed html content to detect CSR clues such as framework indicators, hydration data, web components, and DOM manipulation patterns to identify client-side rendered pages. Output is written to theinfowarcs along with the rest of the page info (pages, comparison info, etc).Will follow up with extracted text analysis using & not using additional page resources.