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

Use clearer example data in unit tests

Open
  • Is something wrong?
#76 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
testing-qa

Research direction

Start by locating the unit tests that use "config" as a mode and "subject_id" as a scope. Confirm whether the proposed "debug" and "version" examples are both in scope, then update the examples and run the affected unit-test suite to verify the behavior remains correct.

Written by the indexing model from the issue text.

Description

Right now we use "config" as a mode, which is kind of confusing. We should make it "debug" mode or something.

Also, maybe "version" would be a better example scope than "subject_id". I haven't super thought through it, but I think a "version" scope would be a good way to handle deploying major version updates to apps, and the awkward period of time when you need to support multiple versions with different config schemas running in various places.

Dominant language
Python
Stars
1
Forks
0
Avg merge
5d 19h
Merged PRs (30d)
4

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 AllenNeuralDynamics/ficus

All issues in AllenNeuralDynamics/ficus

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.