minitest-rack 0.2.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 811e3dd7e9502b380de1de9211f7b9a661d353fc8e93072c3075fb9a4a1ab059
+  data.tar.gz: 1853dc9d7db3ed7344cc56ff9fd9060152cbc8afd6728e1fd2b9990a6294a642
+SHA512:
+  metadata.gz: a8c2725fab0f829e0329a6427c8cf6aef182cd3e1aa98b2b65ad8616b0b9a1ed273ee32c2e95310f498392af676a6715b4c13d432df4eae91a8b1dcebc6f8ceb
+  data.tar.gz: 0e14362d96fbfe2d1231a8cc834bda466c62b693527146d124bc9a05f0a7cac7134a821d4a5c065c16976a547937d3f6c8dbd12e39ef4e05ffb09bf37625572d

data/.github/dependabot.yml

@@ -0,0 +1,24 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "saturday"
+      time: "21:30"
+      timezone: Asia/Kuala_Lumpur
+  - package-ecosystem: "bundler" # See documentation for possible values
+    directory: "/" # Location of package manifests
+    groups:
+      patch-and-minor-dependencies:
+        update-types: ["patch", "minor"]
+    schedule:
+      interval: "weekly"
+      day: "saturday"
+      time: "21:30"
+      timezone: Asia/Kuala_Lumpur

data/.github/workflows/ruby.yml

@@ -0,0 +1,45 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+# GitHub recommends pinning actions to a commit SHA.
+# To get a newer version, you will need to update the SHA.
+# You can also reference a tag or branch, but the action may change without warning.
+
+name: Ruby
+
+on:
+  push:
+    branches: ["master", "ruby-v3x"]
+  pull_request:
+    branches: ["master", "ruby-v3x"]
+
+permissions:
+  contents: read
+
+jobs:
+  lint_and_test:
+    env:
+      RACK_ENV: test
+      COVERAGE: "true"
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        ruby-version: ["3.0", "3.1", "3.2", "3.3"]
+        # Disable JRuby for now
+        # ruby-version: ["3.0", "3.1", "3.2", "3.3", "jruby-9.4"]
+    runs-on: ${{ matrix.os }}
+    timeout-minutes: 3
+
+    steps:
+      - uses: actions/checkout@v4
+      - name: Set up Ruby
+        # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby,
+        # change this to (see https://github.com/ruby/setup-ruby#versioning):
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby-version }}
+          bundler-cache: true # runs 'bundle install' and caches installed gems automatically
+      - name: Run rake (lint and test)
+        run: bundle exec rake

data/.gitignore

@@ -0,0 +1,9 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+/Gemfile.lock

data/.rubocop.yml

@@ -0,0 +1,33 @@
+inherit_from: .rubocop_todo.yml
+
+require:
+  - rubocop-minitest
+  - rubocop-performance
+  - rubocop-rake
+
+# The behavior of RuboCop can be controlled via the .rubocop.yml
+# configuration file. It makes it possible to enable/disable
+# certain cops (checks) and to alter their behavior if they accept
+# any parameters. The file can be placed either in your home
+# directory or in some project directory.
+#
+# RuboCop will start looking for the configuration file in the directory
+# where the inspected file is and continue its way up to the root directory.
+#
+# See https://docs.rubocop.org/rubocop/configuration
+
+AllCops:
+  TargetRubyVersion: "3.0"
+  NewCops: enable
+
+Style/StringLiterals:
+  EnforcedStyle: single_quotes
+
+Style/StringLiteralsInInterpolation:
+  EnforcedStyle: double_quotes
+
+Layout/LineLength:
+  Enabled: true
+  Max: 100
+  Exclude:
+    - "**/*.gemspec"

data/.rubocop_todo.yml

@@ -0,0 +1,7 @@
+# This configuration was generated by
+# `rubocop --auto-gen-config`
+# on 2024-11-11 09:26:46 UTC using RuboCop version 1.68.0.
+# The point is for the user to remove these configuration records
+# one by one as the offenses are removed from the code base.
+# Note that changes in the inspected code, or installation of new
+# versions of RuboCop, may require this file to be generated again.

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at kematzy@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -0,0 +1,83 @@
+# frozen_string_literal: true
+
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in minitest-assert_errors.gemspec
+gemspec
+
+# adding these to silence warnings for Ruby v3.5
+gem 'fiddle'
+gem 'logger'
+gem 'ostruct'
+
+group :development do
+  # A command line tool to easily handle events on file system modifications
+  # DOCS: https://github.com/guard/guard
+  gem 'guard'
+  # automatically runs your tests with Minitest framework
+  # DOCS: https://github.com/guard/guard-minitest
+  gem 'guard-minitest'
+
+  # Ruby testing framework
+  # DOCS: https://github.com/seattlerb/minitest
+  gem 'minitest', '~> 5.7', '>= 5.7.0'
+  # Around and before_all/after_all hooks for Minitest
+  # DOCS: https://github.com/jeremyevans/minitest-hooks
+  gem 'minitest-hooks', '~> 1.1', '>= 1.1.0'
+  # Colored red/green output for Minitest
+  # DOCS: https://github.com/blowmage/minitest-rg
+  gem 'minitest-rg', '~> 5.3', '>= 5.3.0'
+
+  # Ruby build program with capabilities similar to Make
+  # DOCS: https://github.com/ruby/rake
+  gem 'rake', '~> 13.0'
+
+  # Ruby static code analyzer and formatter
+  # DOCS: https://github.com/rubocop/rubocop
+  gem 'rubocop', '~> 1.31', require: false
+  # Code style checking for Minitest files
+  # DOCS: https://github.com/rubocop/rubocop-minitest
+  gem 'rubocop-minitest', require: false
+  # Performance optimization analysis for your projects
+  # DOCS: https://github.com/rubocop/rubocop-performance
+  gem 'rubocop-performance', require: false
+  # A RuboCop extension focused on enforcing Rake best practices and coding conventions
+  # DOCS: https://github.com/rubocop/rubocop-rake
+  gem 'rubocop-rake', require: false
+
+  # Sequel: The Database Toolkit for Ruby
+  # DOCS: https://github.com/jeremyevans/sequel/
+  gem 'sequel'
+  # SQLite3 interface for Ruby
+  # DOCS: https://github.com/sparklemotion/sqlite3-ruby
+  gem 'sqlite3'
+
+  # Code coverage for Ruby
+  # DOCS: https://github.com/simplecov-ruby/simplecov
+  gem 'simplecov'
+
+  # A Ruby language server that provides intellisense, code completion, and inline documentation
+  # DOCS: https://github.com/castwide/solargraph
+  gem 'solargraph'
+end
+
+# Linux-specific gems
+install_if -> { RUBY_PLATFORM.include?('linux') } do
+  # Linux inotify wrapper for Ruby
+  # DOCS: https://github.com/guard/rb-inotify
+  gem 'rb-inotify', require: false
+end
+
+# macOS-specific gems
+install_if -> { RUBY_PLATFORM.include?('darwin') } do
+  # FSEvents API with signals handled for macOS
+  # DOCS: https://github.com/thibaudgg/rb-fsevent
+  gem 'rb-fsevent', require: false
+end
+
+# Windows-specific gems
+install_if -> { Gem.win_platform? } do
+  # Windows Directory Monitor - A library which can be used to monitor directories for changes
+  # DOCS: https://github.com/Maher4Ever/wdm
+  gem 'wdm'
+end

data/Guardfile

@@ -0,0 +1,26 @@
+# frozen_string_literal: true
+
+# A sample Guardfile
+# More info at https://github.com/guard/guard#readme
+
+## Uncomment and set this to only include directories you want to watch
+# directories %w(app lib config test spec features) \
+#  .select{|d| Dir.exist?(d) ? d : UI.warning("Directory #{d} does not exist")}
+
+## Note: if you are using the `directories` clause above and you are not
+## watching the project directory ('.'), then you will want to move
+## the Guardfile to a watched dir and symlink it back, e.g.
+#
+#  $ mkdir config
+#  $ mv Guardfile config/
+#  $ ln -s config/Guardfile .
+#
+# and, you'll have to watch "config/Guardfile" instead of "Guardfile"
+
+guard :minitest do
+  # with Minitest::Spec
+  watch(%r{^spec/(.*)_spec\.rb$})
+  # watch(%r{^lib/minitest/rack/(.+)\.rb$}) { 'spec' }
+  watch(%r{^lib/(.+)\.rb$})         { |m| "spec/#{m[1]}_spec.rb" }
+  watch(%r{^spec/spec_helper\.rb$}) { 'spec' }
+end

data/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2018 Kematzy
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/README.md

@@ -0,0 +1,99 @@
+<!-- markdownlint-disable MD013 MD033 -->
+
+# Minitest::Rack
+
+[![Ruby](https://github.com/kematzy/minitest-rack/actions/workflows/ruby.yml/badge.svg?branch=master)](https://github.com/kematzy/minitest-rack/actions/workflows/ruby.yml) - [![Gem Version](https://badge.fury.io/rb/minitest-rack.svg)](https://badge.fury.io/rb/minitest-rack) - [![Minitest Style Guide](https://img.shields.io/badge/code_style-rubocop-brightgreen.svg)](https://github.com/rubocop/rubocop-minitest)
+
+Coverage: **100%**
+
+[Minitest](https://github.com/seattlerb/minitest) & [rack-test](https://github.com/rack/rack-test)
+convenience assertions/expectations for DRY'er faster testing.
+
+Save time and energy by writing short effecient obvious assertions/expectations with Rack-test
+when using Minitest.
+
+---
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'minitest-rack'
+```
+
+And then execute:
+
+```bash
+bundle
+```
+
+Or install it yourself as:
+
+```bash
+gem install minitest-rack
+```
+
+## Usage
+
+Add the gem to your _Gemfile_ or _.gemspec_ file and then load the gem in your
+`(test|spec)_helper.rb` file as follows:
+
+```ruby
+ # <snip...>
+
+ require 'minitest/autorun'
+ require 'minitest/rack'
+
+ # <snip...>
+```
+
+Adding the above to your `spec_helper.rb` file automatically adds the key helper methods to the
+`Minitest::Assertions` to test for Rack output.
+
+---
+
+## Requirements
+
+- [json](https://github.com/flori/json)
+- [rack-test](https://github.com/brynary/rack-test)
+- [minitest](https://github.com/seattlerb/minitest) ~> 5.0
+
+## Acknowledgements
+
+Inspiration for this gem was taken from the
+[`rack-minitest`](https://github.com/brandonweiss/rack-minitest) gem by Brandon Weiss
+
+Copyright (c) 2012 Brandon Weiss and released under the MIT license.
+
+---
+
+## Development
+
+After checking out the repo, run `bundle install` to install dependencies.
+Then, run `bundle exec rake spec` to run the tests.
+
+To install this gem onto your local machine, run `bundle exec rake install`.
+
+To release a new version:
+
+1. update the version number in `version.rb`
+2. run `bundle exec rake release`, which will create a git tag for the version
+3. push git commits and tags
+4. push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on [GitHub](https://github.com/kematzy/minitest-assert_errors).
+
+This project is intended to be a safe, welcoming space for collaboration, and contributors are
+expected to adhere to the [Contributor Covenant](contributor-covenant.org) code of conduct.
+
+## Copyright
+
+Copyright (c) 2015 - 2024 Kematzy
+
+## License
+
+The gem is available as open source under the terms of the
+[MIT License](http://opensource.org/licenses/MIT).

data/Rakefile

@@ -0,0 +1,24 @@
+# frozen_string_literal: true
+
+require 'bundler/gem_tasks'
+require 'rubocop/rake_task'
+require 'rake/testtask'
+
+RuboCop::RakeTask.new
+
+Rake::TestTask.new(:spec) do |t|
+  t.libs << 'spec'
+  t.libs << 'lib'
+  t.test_files = FileList['spec/**/*_spec.rb']
+end
+
+task default: %i[rubocop coverage]
+
+desc 'alias for spec task'
+task test: :spec
+
+desc 'Run specs with coverage'
+task :coverage do
+  ENV['COVERAGE'] = '1'
+  Rake::Task['spec'].invoke
+end

data/lib/minitest/rack/all.rb

@@ -0,0 +1,7 @@
+# frozen_string_literal: true
+
+require 'rack/test'
+require 'minitest/rack'
+require 'minitest/rack/headers'
+require 'minitest/rack/json'
+require 'minitest/rack/status'