Pragmatic Testing of Ruby Core
summary
Explains how to run CRuby’s tests end to end: build the interpreter with ./configure --disable-install-doc, run make then make check and use targeted tasks like make test-all -j4 to run stdlib, bootstrap and sample suites; notes bootstrap tests run via runner_ruby, some stdlib use minitest directly, and ruby-spec is a reference test set not the formal spec. Calls out six main steps, local runs take ~90–120 minutes, ruby-ci catches platform-specific failures, and coverage tooling currently breaks in some cases.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker background
- 5:19Challenges of Ruby documentation
- 6:48Why testing is easier for contributions
- 9:23Running Ruby language tests
- 11:18Understanding Ruby's test structure
- 16:34Bootstrap and sample tests
- 19:52Extension library tests
- 21:17Running full test suites
- 23:22Test framework dependencies
- 25:14Porting RubyGems and Bundler
- 27:01RSpec vs RubySpec
- 29:53RubySpec execution details
- 31:18Ruby CI and cross-platform testing
- 33:28Additional test tools
- 34:11Summary and call to action
related talks
08mHow to Begin Developing Ruby Core
29mIntroduction to CRuby source code
29mIntroduction to CRuby source code
31mReal World Ruby Testing
45mWhat does my Ruby do?
49mRuby Software Continuously Delivered and Exhaustively Explained
26mReading Ruby - A Visual Walkthrough of the Source Code
26mTales of Interest