33290896dc
The leakchecker will report leaked file descriptors when tests do things like access `Etc.getgrgid`, for example, if NSS modules (like `sss`) handle these lookups by connecting to a daemon like `sssd` and leave the connection open. To address this, we can call glibc's `__nss_configure_lookup` to override NSS modules configured in /etc/nsswitch.conf and only use ordinary file/DNS lookups. (This is a cherry-pick of a patch applied to ruby/mspec here: https://github.com/ruby/mspec/pull/62) |
||
|---|---|---|
| .. | ||
| bin | ||
| lib | ||
| spec | ||
| tool | ||
| .rspec | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE | ||
| README.md | ||
| Rakefile | ||
README.md
Overview
MSpec is a specialized framework that is syntax-compatible with RSpec 2 for
basic things like describe, it blocks and before, after actions.
MSpec contains additional features that assist in writing specs for
Ruby implementations in ruby/spec.
MSpec attempts to use the simplest Ruby language features so that beginning Ruby implementations can run the Ruby specs. For example, no file from the standard library or RubyGems is necessary to run MSpec.
MSpec is not intended as a replacement for RSpec. MSpec attempts to provide a subset of RSpec's features in some cases and a superset in others. It does not provide all the matchers, for instance.
However, MSpec provides several extensions to facilitate writing the Ruby specs in a manner compatible with multiple Ruby implementations.
-
MSpec offers a set of guards to control execution of the specs. These guards not only enable or disable execution but also annotate the specs with additional information about why they are run or not run.
-
MSpec provides a different shared spec implementation specifically designed to ease writing specs for the numerous aliased methods in Ruby.
-
MSpec provides various helper methods to simplify some specs, for example, creating temporary file names.
-
MSpec has several specialized runner scripts that includes a configuration facility with a default project file and user-specific overrides.
-
MSpec support "tagging", that is excluding specs known as failing on a particular Ruby implementation, and automatically adding and removing tags while running the specs.
Requirements
MSpec requires Ruby 2.6 or more recent.
Bundler
A Gemfile is provided. Use Bundler to install gem dependencies. To install Bundler, run the following:
gem install bundler
To install the gem dependencies with Bundler, run the following:
ruby -S bundle install
Development
Use RSpec to run the MSpec specs. There are no plans currently to make the MSpec specs runnable by MSpec: https://github.com/ruby/mspec/issues/19.
After installing the gem dependencies, the specs can be run as follows:
ruby -S bundle exec rspec
To run an individual spec file, use the following example:
ruby -S bundle exec rspec spec/helpers/ruby_exe_spec.rb
Documentation
See CONTRIBUTING.md in ruby/spec
for a list of matchers and how to use mspec.
Source Code
See https://github.com/ruby/mspec
License
See the LICENSE in the source code.