I like the mediocrity of the example they headlined: the user asks for unit tests. Copilot writes only two test cases, so not exactly great coverage. Plus, the test cases uses python's unittest, which isn't as slick as pytest.
I use Copilot a lot for writing specs. I've come to prefer that it only writes one or two specs to start. It's a good way for me to quickly review it has the structure correct. When it throws too many at me at once, it can be harder to make broad tweaks.
As for `pytest`, I just have to remind it I'm using pytest. "Write pytests for this" is sufficient to get it to do what I want.
You can write a prompt stating how tests should be writen in your project. It goes on some .vscode file. It's consulted anytime it's writing a test, even in a conversation. I state where my factory fixtures are to be found.
Well they didn't ask for pytest tests. I wonder if AIs are like bored developers, doing the minimum necessary to complete the task instead of going the extra mile and make things better. Perhaps that will be the differentiator in the future. Or they just need to adjust the pre-prompt.
