Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Decouple the Activation and Discovery

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
testing

Research direction

Start by tracing how activators, discovery, and attributes currently interact; the issue does not name specific files or tests. Determine how dynamic activators produce multiple tests and where discovery needs that information. Done means activation and discovery have separate responsibilities and the resulting design is validated by the project’s tests.

Written by the indexing model from the issue text.

Description

One of the major draw backs to having the activators be used by discovery is that if the activator is dynamic and generates multiple tests, the list of test is unknown at the point of discovery and are only know when the tests run.

Instead of making the attributes enable test activation, it should instead enable test discovery and be responsible for passing the activator once the test are discovered.

Something like IDiscoverable<TActivation> ??

Dominant language
C#
Stars
5
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 bitcobblers/ZeUnit

All issues in bitcobblers/ZeUnit

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.