Improving hotspot
BrowserStack Code Quality helps to analyze your data. There are a few ways through which hotspot can be improved:
Analyze dependencies (v2)
After navigating to the Component Explorer of a certain component, the Dependency View can be accessed via the top menu: 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 show which…
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…
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…
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,…
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…
Identify top priorities with the component list (v2)
What does the component list show? The component list can be accessed from the top navigation bar by clicking the Components tab: The overall score with a list of all components of your software can be seen in ascending order. The components with the worst score are at the top. Similarly,…
View and interpret heatmap (v2)
What Does the Blueprint Show? The blueprint can be accessed from the top navigation bar by clicking the Blueprint tab: When you click it, you’ll be taken to the Blueprint page, which displays the major components of your repository. Each component is represented as a rectangle, where the size of the…
Overview of your software (v2)
1. You need an active Embold account. (Don’t have one? Sign up free here).2. Identifying Problems builds off of the lessons learned in the previous articles. To get the most out of this article we recommend you finish your first scan. Embold rating system The Embold rating system is a numeric…
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…
- 1
- 2