Edit Tool: Developer Tools in QA: Novice's Toolkit

To edit this page, please answer the question that appears below (more info):

What short name does OAIS use for an information package that is used for submission?

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.

Image: In another tab, use the "Upload file" link to upload a logo image. Paste the name of the image here:
Purpose* A single sentence describing the function of the tool. Keep it factual and concise:	A collaborative document which non-developers can adapt to record QA methods using built-in browser developer tools.
Homepage The URL of the homepage:
Sourcecode The URL for the source code:
License:
Cost:
Platforms:
Language:
Wikidata ID:
Input formats Start typing and select from the available list. Only add a new format if necessary:
Output Formats: Start typing and select from the available list. Only add a new format if necessary:
Function*: Start typing and select one or more functions from the available list. Only add a new function if absolutely necessary:
Content: Start typing and select one or more content types from the available list. Only add a new content type if absolutely necessary:

OpenHub ID:
Mailing_lists:
Releases_rss:
Issues_rss:

Free text:

== Description ==  A beginner's guide to using built-in browser developer tools to explore Quality Assurance (QA) issues in web archive captures. This toolkit is focused primarily on archivists who have [[Archive-It]] subscriptions and use [[Heritrix]], [[Brozzler]] and [[Webrecorder]]/Conifer. The toolkit has been used primarily with Google Chrome and Firefox browsers, although the same type of analysis could be applied to other browsers. It is a "living document", intended to be shared and updated collaboratively. It is aimed at new web archivists, and web archivists who are new to using web developer tools for QA. Web developer tools can be quickly accessed in Firefox by pressing Crtl+Shift+E, Crtl+Shift+I in Chrome. 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.

Summary:

Cancel

Edit Tool: Developer Tools in QA: Novice's Toolkit

Navigation menu

Search