racket / racket/htdp

Make *test-object* in test-engine a parameter

Open
#199 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

test engine
Dominant language
Racket
Stars
112
Forks
73
Avg merge
9h 41m
Merged PRs (30d)
1

Description

This looks like something that could be a parameter:

https://github.com/racket/htdp/blob/73ec2b90055f3ab66d30e54dc3463506b25e50b4/htdp-lib/test-engine/test-engine.rkt#L146

And if it were also exposed as such, it would be helpful.

As one example: I would like to be able to dynamically load a module and not have it register any of its tests (as the only reason I'm loading it is to grab a definition from its namespace). That would be easy to do if it were a parameter, but seems quite hard currently.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Read htdp-lib/test-engine/test-engine.rkt around line 146 to understand how test-object is currently defined and used. Check how the test engine exposes configuration, then verify that making it a parameter allows dynamically loaded modules to avoid registering tests.

Written by the indexing model from the issue text.

Assessment

Domain
testing, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.