OtterWise Changelog

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

We have added helpful suggestions when facing in-app code viewer issues, which for now are: enabling the Code viewer, git annotations, downloading coverage file for import locally, and reauthenticating GitHub user.

Fixed: Deeply nested JLog Unit Test log files would break test performance reporting as we expected a certain max level of nesting. We now process suites recursively.

Fixed: Bash Uploader script would occassionally get an invalid Pull Request number in GitHub Actions and fail upload.

To improve your privacy and security, we are moving the live chat widget out of OtterWise, and in to a dedicated page called Support, which will link to mail and of course the great live chat support you are used to. The support will not be impacted by this change, it is a change made to reduce tracking in areas with potentially sensitive data. A link to support is added to the top right corner next to your user name when logged in.

Cobertura coverage format is now generally available for all organizations. This also opens up for better branch coverage detection compared to Clover XML, when enabled.

Fixed: Tooltips in chart and UI should no longer clip outside of the browser window

Organization admins can now enable Code Viewer inside the new settings tab for organizations.

UI: Leaderboard made cleaner structurally, especially on mobile devices.

UI: Alerts inside the system have gotten increased contrast.

UI: Mobile navigation (Hamburger menu) now renders earlier to not cause UI wrapping.

Fixed: Pull Request base SHA would occassionally drift and get out of sync with certain workflows, resulting in a "According to our records, the base branch and the Pull Request base differs." warning on Pull Request comments.

Fixed: Leaderboard rounding decimals was accidentally fixed to 2, it is now set to organization decimal setting.

Pull Request comment with no (0) Complexity difference shows "-" instead of empty now.

Fixed: UI for Repositories in the Dashboard (Repository list) did not show the coverage when coverage was 0%, it would display an empty text, now it displays 0.00%

You can now see the latest 6 repositories you have viewed inside OtterWise when hovering the "Repositories" menu link. It will display across all organization you have access to, not just the current one.

Dropdowns now activate on hover rather than click. They can still be toggled with click.

Pull Request comments now include CRAP (change risk anti-patterns) numbers for head and base commit. read more in our blog post "Understanding CRAP and Cyclomatic Complexity Metrics"

Pull Request comments now include Type Coverage when uploaded.

Pull Request List now has Type Coverage display when uploaded.

Pull Request individual view now displays test and type coverage more prominently.

Commit list is now generally available for all users and organizations. Let's you easily browse all commits and their coverage data per branch.

Commit show (view data per commit) is now in beta for opted-in organizations.

Added a treemap chart that sizes folders and files by uncovered lines, and colors based on coverage percentage, to quickly identify files that might need coverage improvements, and can greately impact overall coverage if covered. This can be found as a new "Analytics" tab when viewing a repository.

Added option to exclude certain branches from leaderboard stats, per repository, so that stagin->main PRs are not counted towards it.

Test Performance overview is now generally available for Pro plans. Read our documentation here

Added ability to opt into in-app code viewer on org. level

Added optional Weekly Digests by e-mail, which will send you a mail every week containing changes to organizations you are a member of, such as coverage change and activity. You can opt-in from the settings page in top right corner when logged in to OtterWise.

User management: Per popular request we added ability to disable upload access for individual users on the organization level.

UI: Added a organization selector in the main dashboard page, enabling quick filtering and overview of how many private repositories are enabled for each organization.

UI: Added filter for repository privacy setting (all, public, private) to find relevant repositories faster.

Bash Uploader: Performance improvements for large repositories.

Bash Uploader: Automated detection of Pest PHP Type Coverage file (pest-type-coverage.json).

Type Coverage: Added support for Pest PHP Type coverage, read announcement blog post.

Author Matching: Added GitHub web-flow bot to ignored authors.

PR Comments: Table for files with reduced coverage now uses PR number for heading instead of branch name, for better readability on smaller screens.

Reporting: Calendar UI now have tooltips and mobile support!

Reporting: The Organization reports tab is now in open beta. See stats like overall coverage change for all branches, GitHub-like graph of days without coverage decrease, how many merged Pull Requests and more.

Pull Requests: It is now optional if you want the graph to only contain merge commits, or the entire commit history on a branch. This greatly cleans up the chart when working with long-lived feature branches.

Leaderboard: Date range is now fixed to 1 month, showing last month (to always show a complete dataset).

Leaderboard: PR Base branches can now be filtered per repository, for organizations has staging branches and similar workflows, to keep attribution accurate.

Revamped Commit authoring logic to use e-mails as fallback instead of name. This comes after numerous reports of teams with employees committing locally with their first name or an alias, and their GitHub name being something else, causing same user to have multiple author connections. Should GitHub support getting commit (and author) info through the API without access to code one day, we will switch to that immediately.

Commit list (BETA) now uses author avatar from GitHub, instead of always using ui-avatars.com.

Your logged in session will now last up to 9 hours (up from 2), to prevent having to log in multiple times during the span of a work day.

Bash Uploader: Added support for uploading Mutation testing files. Currently we do not track mutation coverage, this will be used in an upcoming release. You can however start uploading it now, and once we release mutation coverage tracking, it will use all previous uploads. Usage: Add this to your OtterWise bash uploader parameters --mutation-file [PATH]. It will later be documented in our setup instructions and documentation.

Bash Uploader: Added support for a .otterwise.yml config file. In an upcoming release we will document usage. This file will be entirely optional, and all configuration will also be accessible from the settings page.

Pull Requests Page: Made draft state icon color lighter to differenciate easier from open state icon.

Fixed PR comment 'Files with reduced coverage' occassionally reporting wrong files if coverage was the same, but only lines/covered lines changed.

Pull Requests Page: Fixed state icons occassionally being blurry.

Fixed coverage data transfer for merge commits, when merging across multiple branches (example: feature-branch -> development -> staging -> main), and having CI runs complete after merge.

PR Comments: Short-SHAs are now included in warning messages to better help explain and diagnose issues, such as PR base being different from PR base branch.

Shareable coverage badges now have configurable colors, instead of static levels. Previously it would for example be red for coverage <= 10, and orange <= 20. Now these values can be adjusted per repository, according to your organization needs.

Shareable coverage badges can now have different cache duration, instead of a fixed 10 minutes. By passing in &cache-seconds=VALUE, you can have the badges updated more often (or less often). Minimum value is 60 seconds.

Bash Uploader: Added more paths for detecting JUnit log files.

Added commit list inside OtterWise (in-app), for coverage on commits without a PR associated (As this is a WIP, it can be enabled in Feature Preview, top right corner)

Bash Uploader: Added support for uploading test framework log files (JUnit), which can later be used to report slow tests and more. Privacy Notice: we do not strip code from these files. Generally they only include test names. If this is a concern to you, please reach out to our support.

Added coverage progress bar to repository list in dashboard

Made in-app coverage badges less visually harsh and easier to distinguish with varius color blindness

Changed coverage graph to start from first entry, instead of fixed 3/12 months back

Made coverage files downloadable from inside OtterWise

Added support for GitHub annotations to display per-line coverage misses

Fixed commit author occassionally being set to organization of repository, instead of Pull Request author

Fixed ingress of pushes (not Pull Requests) from GitHub Actions

Added option to switch branch for shareable coverage badges