800 Unit Tests - How Copilot Built Our Full Test Suite
500 methods, no tests, and a Copilot Skill that changed that. Here's how I defined a testing concept once — and let Copilot generate and maintain 800 unit tests automatically, with zero Polarion server required.
I had ~500 methods across my Polarion plugin. No unit tests. Not because I didn't know how — but because writing 800 test methods by hand felt like a week of work that nobody would ever notice until something broke in production.
That changed when I defined a testing concept, handed it to Copilot as a structured skill, and let Copilot generate the entire suite. Today every method is covered, every release runs through a test gate, and I haven't written a single test from scratch.
Here's how that works — and why it's worth setting up.
Table of Contents
- Why Unit Tests at All?
- Why Mockito — and Why Not Test Against a Real Polarion Instance?
- How to Create Tests with Copilot: Skill + Instructions
- Running Tests Locally in VS Code
- Positive, Negative, Edge Case — The Naming Convention That Makes CI Readable
- Tests as a Release Gate
- What This Week Is About
Why Unit Tests at All?
If you've never had a comprehensive unit test suite, the value isn't obvious until the first time it saves you. Here's the short version: