spec
spec copied to clipboard
ruby
The Ruby Spec Suite aka ruby/spec
Refers to #823 Adds specs for one-line pattern matching syntax in Ruby 3.0+, including both Righthand Assignment (`=>`) and one-line match (`in`). **Notes:** I was confused on how to add...
ruby/spec already contains some specs for 2.7, but we should aim to cover all new features and important changes. This will improve the test coverage of these features (and maybe...
There are some deprecated/obsolete methods like `File.exists?`, `Thread#safe_level` etc in the core library. Looks like they aren't covered with tests there and moreover some existing specs were deleted recently -...
There is a test which occasionally exceeds the 30 second timeout on `CI / specs (macos, 2.7.1)`, causing the test suite to fail, even if the changes being tested haven't...
See https://github.com/ruby/spec/pull/753/files#r376792963 `should_not raise_error` is the same as testing nothing. Each example already implicitly test no exception is raised. There might be a few legit cases, but I would expect...
Otherwise, tagging one spec actually skips both specs. I think there are quite a few instances of this in ruby/spec, so we'll need renames in the specs before enforcing the...
This PR adds specs for [Feature #17479](https://bugs.ruby-lang.org/issues/17479) From: - [https://github.com/ruby/spec/issues/923](https://github.com/ruby/spec/issues/923) > Thread::Backtrace > - Thread::Backtrace.limit, which returns the value to limit backtrace length set by `--backtrace-limit` command line option, is...
## Issue * [Write specs for new Ruby 3.1 features and changes #923](https://github.com/ruby/spec/issues/923) ## Change This pull request covers the spec below. > * [ ] Time.new now accepts optional...
Adding test for [Feature #17398](https://bugs.ruby-lang.org/issues/17398) A command syntax is allowed in endless method definitions, i.e., you can now write ``` def foo = puts "Hello" ``` From: https://github.com/ruby/spec/issues/923
Extracted from: https://github.com/ruby/ruby/pull/10235 Ref: https://bugs.ruby-lang.org/issues/20205 Ruby will gradually move towards enabling frozen string literals by default. Making the ruby spec suite compatible is a good first step.
