OtterWise Changelog

Fixed: API Token creation was mistakenly hidden behind a feature flag for ~50% of users, which meant that some users could not create API Tokens. This has been fixed and all users can now create API Tokens. This was reported by users using our Browser Extensions, which requires API Tokens to work.

Pull Requests: Added "Outdated Base" badge on Pull Requests where the base branch has had more recent coverage uploaded in the Pull Requests overview inside OtterWise. This is to help identify Pull Requests that might need a rebase or merge to get the latest coverage data from the base branch.

Pull Requests: Added new filter option "Open with Outdated Base" to the Pull Requests overview inside OtterWise, to quickly find Pull Requests that have an outdated base branch.

Coverage graph now goes to latest commit date rather than today, filling out the graph better for repositories with infrequent commits.

Fixed: The sparklines introduced in a recent release now shows coverage data only for the default branch, rather than all commits for the repository. This was causing confusion as the sparklines would show data for branches that were not the default branch, and could be misleading.

Removal of Test Performance: We made the decision to remove the test performance feature due to low usage. All repositories with test performance data will continue to have access to it, but it will not be possible to enable going forward. We will focus on adding and improving other features that are more widely used.

The dashboard now features sparklines for enabled repositories with data, showing latest 28 commits with coverage data. This is a great way to quickly see how your coverage is trending over time. Its not fixed to a 0-100 y axis, and will therefor display even small changes in coverage very clearly. Hovering it will display time and coverage %.

GitHub status checks now link to the new commit view if not associated to a pull request (eg when pushing directly to main branch, or before making a PR).

Coverage graph points for commits without a pull request associated can now also be clicked, leading to the new commit view.

Viewing specific commits and their coverage data is now generally available. You find it under the repository -> commits and clicking the commit message.

Added LCOV coverage format support for code coverage. This is a popular format for JavaScript and other languages, and can be used in combination with Jest, Karma, Istanbul and more.

Improved frontend performance for organizations with more than 200 repositories, which could appear sluggish when loading the dashboard and reports. Reports should now be more than 60% faster than before, when having +200 repositories.

Added a link to go directly to GitHub repository from OtterWise to smoothen the workflow when going between the two systems.

Changed icons for file list to be sharper and slightly smaller (from 20x20 to 16x16).

Changed icon "Go to Pull Request in GitHub" to be sharper and slightly smaller (from 20x20 to 16x16).

Fixed large code bases with Pull Requests being merged / closed while OtterWise is processing coverage data, would occassionally set pull request state wrongly as we had loaded the data from GitHub before merge/close event was processed. It now updates accurately, and any affected pull request has been reprocessed.

Added new "Change-Risk Anti-Patterns (CRAP) per line" badge option which gives an indication of how risky it is to make changes to your code. The math is simple: 'CRAP' divided by lines of code. The badge will show a color based on the value, from bright green (0.0) to red (+1.00). You can read more about CRAP in our blog post Understanding CRAP and Cyclomatic Complexity Metrics.

Added "Per-line Complexity" and "Per-line CRAP" options for the dashboard statistics, which gives you an average across all repositories, of either complexity or CRAP divided by lines of code. So for example if you have a complexity of 200 and 300 lines of code, your per-line complexity is ~0.66. This addition in relation to our new Complexity badge added in version 2024-10-10, and the customizeable dashboards added in version 2024-09-29.

Added new "Complexity per line" badge option which shows how complex your code is. The math is simple: Cyclomatic Complexity divided by lines of code. The badge will show a color based on the complexity, ranging from bright green (0.0) to red (+0.85). You can read more about complexity in our blog post Understanding CRAP and Cyclomatic Complexity Metrics.

Added ability to toggle the visibility (see Changelog version 2024-09-03) of public repositories, for situations where you might want to hide them from non-registered users.

Added complexity and Average CRAP (crap divided by lines of code) score to the repository overview page, to quickly see how complex the repository is, and how much change-risk there is in the codebase.

Updated the repository overview page to make room for the new statistics while retaining responsiveness.

As mentioned in Changelog version 2024-09-03, the dashboard statistics included 4 values that were up for change based on user feedback. With the feedback given we have added the ability to change the statistics per block, as well as added new statistics blocks to choose from, such as total/average complexity, average CRAP and type coverage. The setting is persisted per user, so each of your team members can display their own preferred statistics.

Fixed: Dashboard statistics would count averages including enabled repositories without any commits, which would skew the numbers, making coverage etc. appear much lower if your organization had enabled-but-unused repositories.

Per request, we have added the ability to view basic information about public repositories without signing up. For now this is historical coverage data (code coverage, and type coverage if applicable) for repository and per file. Code viewing will not be available without an authenticated session. This is still being publicly tested and might change in the future, such as adding pull request and commit overview as well. Attempting to access private repositories without a session or permission will of course not be permitted.

Added a new "Pull Requests" tab in the organization view, which shows all Pull Requests across all repositories in the organization, with coverage data and more. We believe this will be a great way to stay up to date on your organization.

We have added four new statistics blocks on the dashboard that shows organization-wide: number of open pull requests, average coverage, lines of code and CRAP score. These might change depending on user feedback, so please let us know what you think.

Fixed test performance report on main branches occassionally having duplicate entries after merging pull requests

Weekly digest now includes latest week changelog entries from OtterWise, so you can stay up to date with changes we are shipping.

Fixed Pull Request comment lines / covered lines diff display in "Files with reduced coverage" having decimals despite always being a whole number.

Improved Pull Request comment patch text when no lines are covered. Read more #1