ReactionMechanismGenerator / ReactionMechanismGenerator/ARC
Test installations
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 51
- Forks
- 25
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 15
Description
Since we can't always trust 3rd-party repos to continuously be up to date in terms of their installation scripts, we can't afford having our CI tests depend on them.
However, we should create a testing script (not part of CI) for users to get an indication which of the external repos is installed correctly and which isn't.
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 identifying the external repositories and their installation scripts that ARC needs to check. Define how a standalone testing script reports which installations succeed or fail, then run it against representative external repositories and verify that the results clearly identify each repository's status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100