Editing Developer Tools in QA: Novice's Toolkit
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
{{Infobox tool | {{Infobox tool | ||
− | + | |purpose=A collaborative document providing an easy entry point for non-developers and novice web archivers to identify Quality Assurance issues using built-in browser developer tools. | |
− | |purpose=A collaborative document | + | |homepage=https://docs.google.com/document/d/1yC3rP6DJrJNi787wYsPq3aHlFZJjHvXbbEaO0YczTlY/edit?usp=sharing |
− | |homepage= | ||
|language=English | |language=English | ||
|function=Quality Assurance | |function=Quality Assurance | ||
Line 18: | Line 17: | ||
The toolkit includes diagnostic use cases for the "elements", "console" and "network" sections of browser development tools. These can help the archivist spot locations of missing [https://en.wikipedia.org/wiki/CSS CSS] elements, [https://en.wikipedia.org/wiki/JavaScript javascript] issues which might affect replay, and errors occurring in network requests, which can help identify resources missing in a copy. | The toolkit includes diagnostic use cases for the "elements", "console" and "network" sections of browser development tools. These can help the archivist spot locations of missing [https://en.wikipedia.org/wiki/CSS CSS] elements, [https://en.wikipedia.org/wiki/JavaScript javascript] issues which might affect replay, and errors occurring in network requests, which can help identify resources missing in a copy. | ||
− | + | == User Experiences == | |
− | Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --> | + | <!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --> |