forked from CodeYourFuture/Module-JS2
-
Notifications
You must be signed in to change notification settings - Fork 0
[TECH ED] Do the Chrome Debugger Mini Workshop #20
Copy link
Copy link
Open
Labels
🎯 Topic Code ReviewReading, understanding and analysing codeReading, understanding and analysing code🎯 Topic RequirementsInterpreting requirement with precision and accuracyInterpreting requirement with precision and accuracy🎯 Topic TestingIt is important that software works and people can use itIt is important that software works and people can use it🏕 Priority MandatoryThis work is expectedThis work is expected📅 JS2Worked assigned during JS2Worked assigned during JS2📅 Week 4Work assigned during week 4Work assigned during week 4🦔 Size TinyLess than 30minsLess than 30mins
Description
Activity
Metadata
Metadata
Assignees
Labels
🎯 Topic Code ReviewReading, understanding and analysing codeReading, understanding and analysing code🎯 Topic RequirementsInterpreting requirement with precision and accuracyInterpreting requirement with precision and accuracy🎯 Topic TestingIt is important that software works and people can use itIt is important that software works and people can use it🏕 Priority MandatoryThis work is expectedThis work is expected📅 JS2Worked assigned during JS2Worked assigned during JS2📅 Week 4Work assigned during week 4Work assigned during week 4🦔 Size TinyLess than 30minsLess than 30mins
From Module-JS2 created by SallyMcGrath: CodeYourFuture#94
Link to the coursework
https://developer.chrome.com/docs/devtools/javascript/
Why are we doing this?
For months now we have been building a toolkit to help us write great software. In our toolkit we have:
Specifications, like user stories, acceptance criteria, and Given/When/Then
Help us understand what to write and check we've written the right thing.
Tests, like unit tests and assertions
Help us break down our problems and check our solutions work even when we change things.
Asking questions
Help us formally reason through our problems and identify gaps in our mental models.
Playing computer
Helps us reason about code with a mental model.
Audits, like Lighthouse
Help us identify performance and quality improvements we can make to our code.
And now we can add debuggers to our toolkit.
Debuggers are tools that help us find and fix problems, or "bugs", in our JavaScript code. They let us step through our code line-by-line while it runs to see what is happening. This helps us find the place where our mental model of the code is different from our implementation. Your browser has a debugger and so does VSCode.
Key reasons we use debuggers:
JavaScript debuggers give control over execution flow to methodically test and fix bugs. Complete this tutorial (it's a 7 minute video plus tasks) to explore the Chrome Debugger.
Maximum time in hours
.5
How to get help
AI can help you here. Code along with AI so it has the context and ask it when you get stuck. Use this starting prompt: