Jonathan Ginsburg

## Long String Truncation Omits Failure Cause in Message Long failure messages get truncated and omit the culprit. ## Current Behavior When using: ``` expect(a).toBe(b); ``` And `a` and `b`...

Conduct Exhaustive Testing in CI

6

Since CI does not conduct all tests in all environments (OS and Node.js version) it can miss failures, such as what happened with https://github.com/karma-runner/karma/pull/3780. This will ensure that is less...

Update Docs On All Relevant Merges

1

Recently https://github.com/karma-runner/karma/pull/3761 got merged, updating some docs. However the corresponding Release workflow did not trigger updating the public website. We should ensure that the Karma website docs get updated as...

Reuse the GH Actions Testing Workflow in the Release One

1

https://docs.github.com/en/actions/learn-github-actions/reusing-workflows https://github.com/karma-runner/karma/pull/3701#discussion_r729072939

Updating the contributors in the corresponding field of the `package.json` file is one of the tasks that CD undertakes in every release of at least the [Karma core][karma-core-uc] and the...

Having a beta release should improve the Karma org health. Early community testing of breaking changes is a hallmark of mature projects. Also, it gives a chance for many breaking...

Prefer "Rebase Merging"

1

I think preserving the commit history of the head branches of PRs when merging can provide value: prefer ["Rebase Merging"][rebase-merge] over the current "Squash Merging" approach. @devoto13 ? [rebase-merge]: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github#rebasing-and-merging-your-commits

Disallow `chore` Commit Type Across Org

2

Right! We should aim for consistency. Therefore, we should disallow chore in the [core repo](https://github.com/karma-runner/karma) as well. Right? _Originally posted by @jginsburgn in https://github.com/karma-runner/karma-chrome-launcher/pull/249#discussion_r819012769_

Upgrade Node.js's Support

2

Maybe we should add 14 and 16 directly? Given that 10 is already out of support (but we probably should only drop it after Karma core drops it) and 12...

There are many outstanding issues. We should aim to close as many as we can. Many are Q&A threads that have been abandoned.