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
−
|image=FFwebdevtoolsCOPTRwiki.png
+
|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 which non-developers can adapt to record QA methods using built-in browser developer tools.
+
|homepage=[[https://docs.google.com/document/d/1yC3rP6DJrJNi787wYsPq3aHlFZJjHvXbbEaO0YczTlY/edit?usp=sharing|Developer Tools in QA: Novice’s Toolkit]]
−
|homepage=[https://docs.google.com/document/d/1yC3rP6DJrJNi787wYsPq3aHlFZJjHvXbbEaO0YczTlY/edit?usp=sharing Developer Tools in QA: Novice's Toolkit]
 
 
|language=English
 
|language=English
 
|function=Quality Assurance
 
|function=Quality Assurance
Line 11: Line 10:
 
<!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. -->
 
<!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. -->
  
−
 
+
== User Experiences ==
−
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.
+
<!-- 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. -->
−
 
 
−
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.
 
−
 
 
−
<!--== 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. -->
 

Please note that all contributions to COPTR are considered to be released under the Attribution-ShareAlike 3.0 Unported (see COPTR:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

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

Cancel Editing help (opens in new window)

Templates used on this page:

Retrieved from ‘https://coptr.digipres.org/index.php/Developer_Tools_in_QA:_Novice%27s_Toolkit’