Dive through Issue Distributions

The previous sections showed how to identify potential low-quality components that need more attention, either through the Heatmap or the Component List. In this section, the focus is on two different aspects:1. Identifying problematic packages2. Identifying problem classes that lead to bad quality What are the available Distribution Screens? The…

0
Read More

View and Interpret the Heatmap

What Does the Heatmap Show? The Heatmap can be accessed from the top navigation bar by clicking the box icon next to the fire icon: Clicking on it will bring you to the Heatmap page, which shows the main components of your repository. Each component is represented as a rectangle, where…

0
Read More

Scanning a repository

Scans are the foundation of BrowserStack Code Quality: Once started, BrowserStack Code Quality will analyze the given source code, generate metrics, identify code issues and find software design anti-patterns. So let’s run a scan on the repository we just set up. Run a scan Inside the repository, Apache clicks the…

0
Read More

Linking a repository

Repositories are the storage containers for your source code. Most of today’s repositories are stored using services like Github, GitLab, Bitbucket, etc. (view a full list of supported services here). In order to analyze any code on BrowserStack Code Quality, a repository must first be linked. Steps to link a repository:…

0
Read More

Scanning a repository (v2)

Scans are the foundation of Embold: Once started, Embold will analyze the given source code, generate metrics, identify code-issues and find software design anti-patterns. So let’s run a scan on the repository we just set up. Run a scan There are 2 ways through which scan can happen: Scanning starts…

0
Read More