▲ | brookst 5 days ago | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Same plan, same experience. Trying to get it to develop and execute tests and it frequently modifies the test to succeed even if the libraries it calls fail, and then explains that it’s doing so because the test itself works but the underlying app has errors. Yes, I know. That’s what the test was for. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▲ | zarzavat 5 days ago | parent [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Anthropic, if you're listening, please allow zoned access enforcement within files. I want to be able to say "this section of the file is for testing", delineated by comments, and forbid Claude from editing it without permission. My fear when using Claude is that it will change a test and I won't notice. Splitting tests into different files works but it's often not feasible, e.g. if I want to write unit tests for a symbol that is not exported. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|