Software Testing Practices

it has tests, and better than TDD

co-pilot excels in writing tests. It removes so much of the tedium and boilerplate. It seems to understand fixtures once you define one and understands subsequent changes to the boilerplate such as changing usernames, ids, appending items to lists. It is such a massive boost in productivity that those using it are way ahead of those who resist.

I'm curious why you prefer this over writing tests.

I remember Gherkin (Cucumber for Ruby) had this! It does beat having a ton of assertions.

Not to be too critical but coming from Java/C# I‘m not not so hot they are writing their own tests: https://github.com/unexpectedjs/unchecked/blob/master/test/i...Maybe just a matter of familiarity?

I haven't, thanks for pointing out. Seems like a closely related concept, although appears to be used mostly in security testing context. Also, at least for Python most tools are a bit too complex—I imagined something more like a TestCase subclass (not even a test runner) that augments certain assert methods and possibly provides new ones. Anyway, on a second thought, adopting TDD looks like a better solution.

Have you looked into BDD tools like Behat/Behave/Cucumber ?

This is awesome. Somewhat echoing the other feedback here, I'm a little concerned about the "self test" side of things, and would much rather sweep wrote tests. Given my experience with ChatGPT and copilot though, I feel reassured that it would write tests for me. If it wrote tests by default (or used a heuristic on when to write tests), I would find it impossible to not use this I think.Great job.

Love it!> "never have to write and maintain your tests again!"this feels a bit misleading though.What are you doing step ci? :D

what would you recommend to read to be better at writing tests?