kettle-test 1.0.10 → 2.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 79fc981181a8f3b48ffa133eeeea78ad356c5f1bc2816facd7890196b818ca4a
-  data.tar.gz: 301dffb357aa9de2b960e8b7e8026f10d9d3d3770f39beda8856fdecf3e68828
+  metadata.gz: 29bb20818a80f275c15b25bef0078baca3d702d7a37e192c58ef9b5cf6363f07
+  data.tar.gz: 9c57bdc7c6fe26a0c2f2889c07c1575042cfeb1eb4bf378669551d84d01c453f
 SHA512:
-  metadata.gz: 5f71ae20e1df354bd9a7df27798bcbcbbc72c18e2d37675887a4b5fae0c71f61d4303963147cad26c3bbc6e236a318f478f60f961416069d895f471b2c481cc4
-  data.tar.gz: 3e49306564d004d2660f7c097a65dcb193bd475de691f43e960eb54229db76af340b55d2b28a080257761a45ae2af805098dd7f35d2079029e99ff38ddf5c0dc
+  metadata.gz: 82aa8c0ce12527b49efc55f43ee3d6354ef14b0839b0bc234ef20779c6a6cb780ad536793fbc86229940f44671d288d43bdc902dcb64d336530bd54d7a6f20ba
+  data.tar.gz: de92fabfcfc30947573b6b68ce1818794256d565a06149e2b69d57e7b7327b9f45b474c039c2f0228641cebb5ebb755887178a7b06ebc3fc7062b94b3982b941

data/CHANGELOG.md

@@ -30,6 +30,62 @@ Please file a bug if you notice a violation of semantic versioning.
 
 ### Security
 
+## [2.0.1] - 2026-05-25
+
+- TAG: [v2.0.1][2.0.1t]
+- COVERAGE: 100.00% -- 91/91 lines in 15 files
+- BRANCH COVERAGE: 100.00% -- 2/2 branches in 15 files
+- 90.00% documented
+
+### Changed
+
+- Refreshed generated project templates and CI workflows.
+- Refreshed project templating and generated documentation after the 2.0.0
+  release.
+- Pruned generated binstubs to the current curated kettle-jem set.
+- Updated local modular Gemfile sibling wiring for coverage, documentation, and templating.
+- Updated the coverage bundle to require `kettle-soup-cover` 1.1.3 or newer.
+
+### Fixed
+
+- `kettle-test` now invokes `kettle-soup-cover`'s turbo coverage setup and
+  cleanup APIs directly around the default `turbo_tests2` runner, so collated
+  coverage artifacts are published even when the host Rakefile does not load the
+  optional turbo coverage rake tasks.
+- `kettle-test --help` now prints usage and exits without creating
+  `tmp/kettle-test` logs or invoking the configured test runner.
+
+## [2.0.0] - 2026-05-23
+
+- TAG: [v2.0.0][2.0.0t]
+- COVERAGE: 100.00% -- 91/91 lines in 15 files
+- BRANCH COVERAGE: 100.00% -- 2/2 branches in 15 files
+- 90.00% documented
+
+### Added
+
+- Added the `kettle-test` executable, which runs RSpec through Bundler, captures
+  full output under `tmp/kettle-test/`, and prints a compact failure, seed,
+  timing, and coverage summary.
+- Added default `kettle/test/rspec` integration coverage for exported RSpec
+  helpers and configuration constants.
+
+### Changed
+
+- `kettle-test` now runs specs through `turbo_tests2` by default, with
+  `KETTLE_TEST_RUNNER=rspec` available as an opt-out for direct RSpec runs.
+- Added `KETTLE_TEST_TURBO_PROCESSES`, `KETTLE_TEST_TURBO_RUNTIME_LOG`, and
+  `KETTLE_TEST_TURBO_NICE` controls for the default `turbo_tests2` runner.
+- Switched the coverage test stack to `turbo_tests2 ~> 3.0`.
+- Migrated local development dependency wiring to the current nomono-based
+  modular Gemfile pattern used by the kettle-rb template.
+- Refreshed project templating, CI workflows, and release support files from the
+  current kettle-jem full template.
+- Changed the project license metadata and generated license files to
+  `AGPL-3.0-only`.
+- Dropped support for Ruby 2.3 because `turbo_tests2` is now a runtime
+  dependency and requires Ruby 2.4 or newer.
+
 ## [1.0.10] - 2026-02-06
 
 - TAG: [v1.0.10][1.0.10t]
@@ -200,7 +256,11 @@ Please file a bug if you notice a violation of semantic versioning.
   - silent_stream
   - timecop-rspec
 
-[Unreleased]: https://github.com/kettle-rb/kettle-test/compare/v1.0.10...HEAD
+[Unreleased]: https://github.com/kettle-rb/kettle-test/compare/v2.0.1...HEAD
+[2.0.1]: https://github.com/kettle-rb/kettle-test/compare/v2.0.0...v2.0.1
+[2.0.1t]: https://github.com/kettle-rb/kettle-test/releases/tag/v2.0.1
+[2.0.0]: https://github.com/kettle-rb/kettle-test/compare/v1.0.10...v2.0.0
+[2.0.0t]: https://github.com/kettle-rb/kettle-test/releases/tag/v2.0.0
 [1.0.10]: https://github.com/kettle-rb/kettle-test/compare/v1.0.9...v1.0.10
 [1.0.10t]: https://github.com/kettle-rb/kettle-test/releases/tag/v1.0.10
 [1.0.9]: https://github.com/kettle-rb/kettle-test/compare/v1.0.8...v1.0.9

data/CITATION.cff

@@ -1,19 +1,19 @@
 cff-version: 1.2.0
-title: kettle-test
+title: "kettle-test"
 message: >-
   If you use this work and you want to cite it,
   then you can use the metadata from this file.
 type: software
 authors:
-  - given-names: Peter Hurn
-    family-names: Boling
-    email: peter@railsbling.com
-    affiliation: railsbling.com
+  - given-names: "Peter H."
+    family-names: "Boling"
+    email: "floss@galtzo.com"
+    affiliation: "galtzo.com"
     orcid: 'https://orcid.org/0009-0008-8519-441X'
 identifiers:
   - type: url
     value: 'https://github.com/kettle-rb/kettle-test'
-    description: kettle-test
+    description: "kettle-test"
 repository-code: 'https://github.com/kettle-rb/kettle-test'
 abstract: >-
   kettle-test

data/CONTRIBUTING.md

@@ -8,19 +8,27 @@ To submit a patch, please fork the project, create a patch with tests, and send
 
 Remember to [![Keep A Changelog][📗keep-changelog-img]][📗keep-changelog] if you make changes.
 
+## Developer Certificate of Origin
+
+In order to protect users of this project, we require all contributors to comply with the
+[Developer Certificate of Origin](https://developercertificate.org/).
+This ensures that all contributions are properly licensed and attributed.
+
 ## Help out!
 
-Take a look at the `reek` list which is the file called `REEK` and find something to improve.
+Take a look at the open issues and pull requests, or use the gem and find something to improve.
 
 Follow these instructions:
 
-1. Fork the repository
-2. Create a feature branch (`git checkout -b my-new-feature`)
-3. Make some fixes.
-4. Commit changes (`git commit -am 'Added some feature'`)
-5. Push to the branch (`git push origin my-new-feature`)
-6. Make sure to add tests for it. This is important, so it doesn't break in a future release.
-7. Create new Pull Request.
+1. Join the Discord: [![Live Chat on Discord][✉️discord-invite-img]][✉️discord-invite]
+2. Fork the repository
+3. Create your feature branch (`git checkout -b my-new-feature`)
+4. Make some fixes.
+5. Commit your changes (`git commit -am 'Added some feature'`)
+6. Push to the branch (`git push origin my-new-feature`)
+7. Make sure to add tests for it. This is important, so it doesn't break in a future release.
+8. Create new Pull Request.
+9. Announce it in the channel for this org in the [Discord][✉️discord-invite]!
 
 ## Executables vs Rake tasks
 
@@ -42,6 +50,22 @@ There are many Rake tasks available as well. You can see them by running:
 bin/rake -T
 ```
 
+## Code quality checks
+
+Run the Reek task when you want a smell check that fails on current findings:
+
+```shell
+bin/rake reek
+```
+
+Refresh the checked-in `REEK` backlog through the rake task, not by redirecting
+the raw `reek` executable output. The rake task uses the project bundle and
+avoids stale generated binstubs shadowing the Reek gem executable:
+
+```shell
+bin/rake reek:update
+```
+
 ## Environment Variables for Local Development
 
 Below are the primary environment variables recognized by stone_checksums (and its integrated tools). Unless otherwise noted, set boolean values to the string "true" to enable.
@@ -52,7 +76,7 @@ General/runtime
 - CI: When set to true, adjusts default rake tasks toward CI behavior
 
 Coverage (kettle-soup-cover / SimpleCov)
-- K_SOUP_COV_DO: Enable coverage collection (default: true in .envrc)
+- K_SOUP_COV_DO: Enable coverage collection (default: true in `mise.toml`)
 - K_SOUP_COV_FORMATTERS: Comma-separated list of formatters (html, xml, rcov, lcov, json, tty)
 - K_SOUP_COV_MIN_LINE: Minimum line coverage threshold (integer, e.g., 100)
 - K_SOUP_COV_MIN_BRANCH: Minimum branch coverage threshold (integer, e.g., 100)
@@ -78,7 +102,7 @@ Git hooks and commit message helpers (exe/kettle-commit-msg)
 - GIT_HOOK_FOOTER_SENTINEL: Required when footer append is enabled — a unique first-line sentinel to prevent duplicates
 - GIT_HOOK_FOOTER_APPEND_DEBUG: Extra debug output in the footer template (true/false)
 
-For a quick starting point, this repository’s `.envrc` shows sane defaults, and `.env.local` can override them locally.
+For a quick starting point, this repository’s `mise.toml` defines the shared defaults, and `.env.local` can override them locally. Copy `.env.local.example` to `.env.local`, use `KEY=value` lines, and either activate `mise` in your shell or run commands through `mise exec -C /path/to/project -- ...`.
 
 ## Appraisals
 
@@ -97,22 +121,20 @@ bin/rake appraisal:reset
 
 When adding an appraisal to CI, check the [runner tool cache][🏃‍♂️runner-tool-cache] to see which runner to use.
 
-## The Reek List
-
-Take a look at the `reek` list which is the file called `REEK` and find something to improve.
+## Run Tests
 
-To refresh the `reek` list:
+Run tests via `kettle-test` (provided by `kettle-test`). It runs RSpec, writes the full log to
+`tmp/kettle-test/rspec-TIMESTAMP.log`, and prints a compact highlight block with timing, seed,
+pass/fail count, failing example list, and SimpleCov coverage percentages.
 
 ```console
-bundle exec reek > REEK
+bundle exec kettle-test
 ```
 
-## Run Tests
-
-To run all tests
+For targeted runs, disable the hard coverage threshold to avoid false failures:
 
 ```console
-bundle exec rake test
+K_SOUP_COV_MIN_HARD=false bundle exec kettle-test spec/path/to/spec.rb
 ```
 
 ### Spec organization (required)
@@ -183,33 +205,34 @@ NOTE: To build without signing the gem set `SKIP_GEM_SIGNING` to any value in th
 1. Run `bin/setup && bin/rake` as a "test, coverage, & linting" sanity check
 2. Update the version number in `version.rb`, and ensure `CHANGELOG.md` reflects changes
 3. Run `bin/setup && bin/rake` again as a secondary check, and to update `Gemfile.lock`
-4. Run `git commit -am "🔖 Prepare release v<VERSION>"` to commit the changes
-5. Run `git push` to trigger the final CI pipeline before release, and merge PRs
+4. Run `bin/rake yard` to regenerate the docs site using the canonical docs task
+5. Run `git commit -am "🔖 Prepare release v<VERSION>"` to commit the changes
+6. Run `git push` to trigger the final CI pipeline before release, and merge PRs
     - NOTE: Remember to [check the build][🧪build].
-6. Run `export GIT_TRUNK_BRANCH_NAME="$(git remote show origin | grep 'HEAD branch' | cut -d ' ' -f5)" && echo $GIT_TRUNK_BRANCH_NAME`
-7. Run `git checkout $GIT_TRUNK_BRANCH_NAME`
-8. Run `git pull origin $GIT_TRUNK_BRANCH_NAME` to ensure latest trunk code
-9. Optional for older Bundler (< 2.7.0): Set `SOURCE_DATE_EPOCH` so `rake build` and `rake release` use the same timestamp and generate the same checksums
+7. Run `export GIT_TRUNK_BRANCH_NAME="$(git remote show origin | grep 'HEAD branch' | cut -d ' ' -f5)" && echo $GIT_TRUNK_BRANCH_NAME`
+8. Run `git checkout $GIT_TRUNK_BRANCH_NAME`
+9. Run `git pull origin $GIT_TRUNK_BRANCH_NAME` to ensure latest trunk code
+10. Optional for older Bundler (< 2.7.0): Set `SOURCE_DATE_EPOCH` so `rake build` and `rake release` use the same timestamp and generate the same checksums
     - If your Bundler is >= 2.7.0, you can skip this; builds are reproducible by default.
     - Run `export SOURCE_DATE_EPOCH=$EPOCHSECONDS && echo $SOURCE_DATE_EPOCH`
     - If the echo above has no output, then it didn't work.
     - Note: `zsh/datetime` module is needed, if running `zsh`.
     - In older versions of `bash` you can use `date +%s` instead, i.e. `export SOURCE_DATE_EPOCH=$(date +%s) && echo $SOURCE_DATE_EPOCH`
-10. Run `bundle exec rake build`
-11. Run `bin/gem_checksums` (more context [1][🔒️rubygems-checksums-pr], [2][🔒️rubygems-guides-pr])
+11. Run `bundle exec rake build`
+12. Run `bin/gem_checksums` (more context [1][🔒️rubygems-checksums-pr], [2][🔒️rubygems-guides-pr])
     to create SHA-256 and SHA-512 checksums. This functionality is provided by the `stone_checksums`
     [gem][💎stone_checksums].
     - The script automatically commits but does not push the checksums
-12. Sanity check the SHA256, comparing with the output from the `bin/gem_checksums` command:
+13. Sanity check the SHA256, comparing with the output from the `bin/gem_checksums` command:
     - `sha256sum pkg/<gem name>-<version>.gem`
-13. Run `bundle exec rake release` which will create a git tag for the version,
+14. Run `bundle exec rake release` which will create a git tag for the version,
     push git commits and tags, and push the `.gem` file to the gem host configured in the gemspec.
 
-[📜src-gl]: https://gitlab.com/kettle-rb/kettle-test/
+[📜src-gl]: https://gitlab.com/kettle-rb/kettle-test
 [📜src-cb]: https://codeberg.org/kettle-rb/kettle-test
 [📜src-gh]: https://github.com/kettle-rb/kettle-test
 [🧪build]: https://github.com/kettle-rb/kettle-test/actions
-[🤝conduct]: https://gitlab.com/kettle-rb/kettle-test/-/blob/main/CODE_OF_CONDUCT.md
+[🤝conduct]: https://github.com/kettle-rb/kettle-test/blob/main/CODE_OF_CONDUCT.md
 [🖐contrib-rocks]: https://contrib.rocks
 [🖐contributors]: https://github.com/kettle-rb/kettle-test/graphs/contributors
 [🚎contributors-gl]: https://gitlab.com/kettle-rb/kettle-test/-/graphs/main
@@ -225,3 +248,4 @@ NOTE: To build without signing the gem set `SKIP_GEM_SIGNING` to any value in th
 [📌major-versions-not-sacred]: https://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html
 [🚎appraisal2]: https://github.com/appraisal-rb/appraisal2
 [🏃‍♂️runner-tool-cache]: https://github.com/ruby/ruby-builder/releases/tag/toolcache
+[✉️discord-invite]: https://discord.gg/3qme4XHNKN

data/FUNDING.md

@@ -19,7 +19,7 @@ Many paths lead to being a sponsor or a backer of this project. Are you on such
 [🖇polar-img]: https://img.shields.io/badge/polar-donate-a51611.svg?style=flat
 [🖇polar]: https://polar.sh/pboling
 [🖇kofi-img]: https://img.shields.io/badge/ko--fi-%E2%9C%93-a51611.svg?style=flat
-[🖇kofi]: https://ko-fi.com/O5O86SNP4
+[🖇kofi]: https://ko-fi.com/pboling
 [🖇patreon-img]: https://img.shields.io/badge/patreon-donate-a51611.svg?style=flat
 [🖇patreon]: https://patreon.com/galtzo
 [🖇buyme-small-img]: https://img.shields.io/badge/buy_me_a_coffee-%E2%9C%93-a51611.svg?style=flat

data/LICENSE.md

@@ -0,0 +1,13 @@
+# License
+
+This project is made available under the following licenses.
+Choose the option that best fits your use case:
+
+- [AGPL-3.0-only](AGPL-3.0-only.md)
+- [PolyForm-Small-Business-1.0.0](PolyForm-Small-Business-1.0.0.md)
+
+If none of the above licenses fit your use case, please [contact us](mailto:floss@galtzo.com) to discuss a custom commercial license.
+
+## Copyright Notice
+
+Required Notice: Copyright (c) 2023, 2025-2026 Peter H. Boling