#Visual studio code coverage colors how to#

The basics of unit testing and experience with any testing framework (understanding what is a test file, a test, a test assertion). The current paragraph is marked with the border as an example.Īfter at least one module is marked as completed, modules that have not yet been completed, or modules that contain modified content are marked with the same color in the Tutorial Modules list on the right side of the screen.īefore you start, there are a couple of things that you are expected to know in order to get the most out of this tutorial:

When significant changes or additions are made to the module after it has been marked as completed, the module gets automatically marked as Not Completed and new/modified parts are marked with the right border. After a module has been marked as completed, the completion progress is saved locally. Once you finish following a module, it can be marked as Completed using a corresponding checkbox at the end of each module and next to the module’s header. Inside a typical module you will find instructions to follow, feature guides, color-code sections with self-descriptive headers, and helpful images and videos. If you make any undesired changes while following a module, or something stops working for you, you may use the Restart module icon located next to the module’s header. For example click to open the README file. In the module you may see links decorated with VS Code icon, clicking such links opens related files in VS Code. Once a tutorial module has been started in VS Code, you may start following the module's content. The currently started module’s name is displayed in the tutorial’s sticky header with the Active module label. Starting the module makes Wallaby run the module’s tests and code in your editor. Some modules can be started in your opened VS Code instance right from the tutorial page using VS Code icon in the module’s header. The tutorial consists of several modules that cover specific Wallaby features.

If this does not help, please try using Chrome in case your browser is blocking the localhost web socket connection that Wallaby uses to synchronize VS Code with the tutorial page. In this case you may try running the Wallaby.js: Open Tutorial command in your editor to restore the connection. If the tutorial cannot connect to VS Code because it's not running, or if the tutorial page disconnects from VS Code for some reason, you will see the Not connected to editor label at the right side of the tutorial header.

We recommend positioning the VS Code window with the opened tutorial repository side-by-side with the tutorial browser window for the best user experience.Īlternatively, you may follow the tutorial without having VS Code opened, however in this case you will not be able to open source files or save your learning progress. The command downloads and opens a GitHub repository with code examples for the tutorial. The tutorial is supposed to be opened by running the Wallaby.js: Open Tutorial command (or using the links on the Wallaby Welcome VS Code page).

#Visual studio code coverage colors how to#

The tutorial is suitable for new users, and existing users who want to learn how to use new features as they are released. Welcome to the Wallaby VS Code interactive tutorial. Explore other Wallaby features About the Tutorial