tsv_

8 ms·

1. 1.▲
   by tsv_ 11mo ago

   Thank you for sharing this example! You've perfectly captured one of my main frustrations: pytest tries to be "helpful" by adding extra context, but ends up obscuring the actual error.
2. 2.▲
   by tsv_ 11mo ago

   Thank you for taking the time to explain your perspective, this is exactly the kind of thoughtful feedback that helps me understand different testing philosophies. Your distinction between assertions (preconditions/invariants) vs tests
3. 3.▲
   by tsv_ 1y ago

   Thanks for the feedback, it helps me see things from a different perspective. These are excellent questions, and you're absolutely right that they should be clear from the landing page. I'll work on fixing that. Short answers: 1.
4. 4.▲
   by tsv_ 1y ago

   Thanks for the support! It means a lot, especially from someone who shares the pytest frustration. About bare `assert`s. Vedro is actually flexible enough to use any matchers you prefer, but let me share why I stick with plain asserts: 1. I
5. 5.▲
   by tsv_ 1y ago

   I'm working on Vedro, a Python testing framework as a pytest alternative without the magic and with clear output. The main idea is that tests should just be Python: plain `assert` statements instead of custom matchers, no fixture magic
6. 6.▲
   by tsv_ 2y ago

   Each time a new LLM version comes out, I give it another try at generating tests. However, even with the latest models, tailored GPTs, and well-crafted prompts with code examples, the same issues keep surfacing: - The models often create se