View the impact of change

Before you get started Before starting this article, make sure you have:1. An active BrowserStack Code Quality account (Don’t have one? Sign up free here).2. Gone through Your First Scan and Identifying Problems. Assessing Changes builds off of the lessons learned in the previous articles. To get the most out…

0
Read More

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

Using the Partitioning Editor (v2)

When to use the partitioning editor? There are many issues that are a result of classes being too large. This can range from components that are slightly above the recommended lines of code threshold to large components with non–cohesive functionality. A common strategy for dealing with such components is breaking…

0
Read More

Analyse dependencies (v2)

After navigating to the Component Explorer of a certain component, the Dependency View can be accessed by entering into that specific component: The Dependency View can show all incoming or outgoing dependencies of one component. Outgoing dependencies are describing the components that are used by the current component, incoming dependencies…

0
Read More

Component explorer for fixing issues (v2)

Before you get started Before starting this tutorial, make sure you have:1. An active Embold account (Don’t have one? Check Sign up free here).2. Gone through your First Scan and Identifying Problems. Improving Hotspots article builds off the lessons learned in these previous articles. Analysing the component rating In Identifying Problems,…

0
Read More

Dive through Issue Distributions (v2)

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