initial commit for agent context around covered usage, started writin…#34
Conversation
…g around integration, logging level
|
I think we can probably remove the implementation details and focus on the integration / usage. I would then suggest adding a brief section on how to actually approach the problem of improving coverage - e.g. describe the process of running tests with coverage, identifying missing coverage, and then writing a test to cover it. |
|
Got it, will submit another draft either today or tomorrow. |
…ces, usage, security consideratins and a step-by-step list of how to improve coverage
|
For now, I think up until line 112 is good, we should not go into too much detail about the actual test frameworks IMHO. |
|
I also added a step by step explanation of how to iteratively improve a codebase s test coverage at the end. I can remove anything related to testing frameworks and leave the main ideas behind; If you're not okay with that I'll just leave it up to line 112 |
|
I think up to line 112 is good enough for now. The reason why is I want to ensure these files remain focused, so that agents consult them + they should consult other test framework specific files on how to write good tests. If it turns out that this doesn't work well, we can revisit it. I'd rather start a little simpler and increase in complexity (entropy) as required. Is that reasonable? |
…agents to consult the frameworks specific files'
|
Got it, yeah makes perfect sense, I'll update the PR, thanks for the explanation! Let me know if you want me to rebase this into a single commit or anything of the sort. |
7a2e500
into
socketry:main
…g around integration, logging level
As per ioquatix/ioquatix#39 I have opened up a pull request containing some MD agent-ready context.
Types of Changes
Contribution