Configs that haven't been covered by tests

Open
#630 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
cli, testing

Research direction

Start with Context#initialize and the existing tests in test_context.rb, then trace each listed IRB.conf config to understand its expected behavior. Add coverage for AP_NAME, LOAD_MODULES, USE_TRACER, USE_LOADER, IGNORE_EOF, BACK_TRACE_LIMIT, IRB_NAME, and EXTRA_DOC_DIRS, with tests demonstrating the intended behavior for each.

Written by the indexing model from the issue text.

Description

rubyconf-hackdays

These are the configs (IRB.conf[config_name]) referenced in Context#initialize but not covered by any test cases (probably `test_context.rb):

  • :AP_NAME
  • :LOAD_MODULES
  • :USE_TRACER - This could be broken with ruby/tracer version. May need to drop it directly
  • :USE_LOADER
  • :IGNORE_EOF
  • :BACK_TRACE_LIMIT
  • :IRB_NAME
  • :EXTRA_DOC_DIRS
Dominant language
Ruby
Stars
477
Forks
165
Avg merge
1d 19h
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ruby/irb

All issues in ruby/irb

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.