What problem are you trying to solve?
As discussed previously, pydepgate has over 1500 tests and there is no centralized place for contributors and users to see what tests we have created.
What feature would solve this?
A dedicated TEST_REGISTRY.md file with all tests listed in tree format.
What does success look like?
A markdown file that is human readable such that a user with no familiarity with the codebase can gain a high-level understanding of test files in this project.
What alternatives have you considered?
Not applicable. Alternatives would come down to formatting preferences and I will defer to 0xIkari in that matter. I have no issues with tree format.
Why does this matter?
Transparency is important for any open source project. Even more so for security tools like pydepgate. having a registry of the tests we have avoids duplicated efforts by contributors and gives users the chance to quickly digest what we have and have not tested.
How critical is this to your use of pydepgate?
Nice to have. I can work around it.
Estimated implementation effort (your best guess)
- Medium
Does this have security implications?
No
Security notes (if applicable)
N/A
Context (optional)
We discussed this in private communication and I am submitting it as an issue to get used to this process and track work end-to-end.
Before submitting
What problem are you trying to solve?
As discussed previously, pydepgate has over 1500 tests and there is no centralized place for contributors and users to see what tests we have created.
What feature would solve this?
A dedicated TEST_REGISTRY.md file with all tests listed in tree format.
What does success look like?
A markdown file that is human readable such that a user with no familiarity with the codebase can gain a high-level understanding of test files in this project.
What alternatives have you considered?
Not applicable. Alternatives would come down to formatting preferences and I will defer to 0xIkari in that matter. I have no issues with tree format.
Why does this matter?
Transparency is important for any open source project. Even more so for security tools like pydepgate. having a registry of the tests we have avoids duplicated efforts by contributors and gives users the chance to quickly digest what we have and have not tested.
How critical is this to your use of pydepgate?
Nice to have. I can work around it.
Estimated implementation effort (your best guess)
Does this have security implications?
No
Security notes (if applicable)
N/A
Context (optional)
We discussed this in private communication and I am submitting it as an issue to get used to this process and track work end-to-end.
Before submitting