That should be line seven, where it says: addPlace ( 'Nairobi', 'Kenya' ) Go back to placesTest.js and add a breakpoint on the line just before where the first test failure occurs. You’ll need to comment out the last three lines you added in places.js otherwise the tests won’t run as expected. Go back to the dropdown and select Mocha Tests.
Places, addPlace : ( city, country ) => , You’ll need to open the debug-project folder in VS Code ( File > Open Folder) and select the file from within the editor.
The first file I’d like you to look at is src/places.js. Once we’re finished, you’ll never want to use a console.log() again. We’ll also look at how to use the Debugger for Chrome extension that allows VS Code to integrate with Chrome Dev Tools. In this this article, we’ll look at how to use the debugging facilities provided by Visual Studio Code. In fact, every major browser provides its own tools. There are a number of tools available for debugging JavaScript code, such as the Chrome Dev Tools, Node Debugger, Node Inspect and others. To remedy this, we need to change our habits and start using debugging tools. Often you’ll find yourself laying down console.log traps all over your code to see which one will reveal the culprit. However, things can get finicky at times if you don’t know where and what is causing the bug. For a long time, most developers, including myself, have been using console.log to debug broken code. The answer lies in using debugging tools. I’m pretty sure the first question you’d ask yourself would be “How am I ever going to confirm my code is working correctly?” Imagine for a moment that the console.log() function did not exist in JavaScript. This article covers two tools that will help you debug JavaScript like a pro. Debugging JavaScript isn’t the most fun aspect of JavaScript programming, but it’s a vital skill.
0 kommentar(er)
