ReactionMechanismGenerator / ReactionMechanismGenerator/ARC
Make sure that tests always use the default settings.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 51
- Forks
- 25
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 15
Description
Is your feature request related to a problem? Please describe.
If a user tries to make test after adding some settings to their .arc folder, some tests might fail because of that. This is extremely important for developers, especially when trying to implement a new software, as the non- default settings may interfere with the testing and may lead to waste of time troubleshooting, waiting for CI's to converge, and so on.
Describe the solution you'd like
I would like a flag like testing = False, that turns True if testing, and then only reads the default settings, skipping the .arc folder.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the settings-loading path used by make test, including how the .arc folder is read and where default settings are selected. Verify the behavior with tests that run after custom settings are present; done means tests consistently use default settings without interference from .arc.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100