There’s a new project on my needles this week… but for once, I can’t show you a single stitch. Not because I’ve messed it up, but because I’m test knitting a new pattern that hasn’t been released yet.
It’s a secret knit.
A hush-hush, zipped-lips, no-spoilers situation. And while I can’t tell you what it is, I can tell you it’s shaping up to be a very enjoyable project - rhythmic to knit, easily memorised repeats and lots of garter stitch.
I’ve test knit (knitted?) a few patterns over the years but every now and then the online conversation rears its head again: is test knitting just unpaid labour? Are we being exploited? Shouldn’t designers just rely on their tech editor?
And you know what? These are fair questions. They come up regularly - usually when someone posts about a test knit with a 10-day deadline, required yarn purchases, styled photos, hashtag usage, cross-promotion, and a cheery “exposure!” thrown in for good measure. In those cases? I agree… it starts to feel a lot like work. Unpaid work.
But not all test knits are created equal.
This one I’m doing? There’s no pressure. No content demands. No expectation to promote the pattern. I can even choose the yarn I use! The designer simply wanted knitters to test clarity, check yardage, confirm tension, and offer feedback. In other words, help make the pattern the best it can be before it's published.
And that’s exactly the kind of test knit I enjoy. It's collaborative. It feels like helping a fellow crafter - not doing someone else’s job.
So why do I do it? Because I choose to. No illusions, no exploitation… I know I won’t get paid, and I’m fine with that. It’s like joining a book club but for yarn: I’m part of a group doing something together that’s meaningful, creative, and a little bit exciting. And, let’s be honest, I love being in on a secret.
There’s a deeper satisfaction in knitting something before the rest of the world sees it. It feels like a small contribution to the patterns we all benefit from later. And I’ve always found that good test knitting experiences come from designers who are clear about expectations and grateful for your time, not trying to squeeze free marketing out of volunteers.
So yes sometimes test knitting is unfairly structured and under-appreciated. But in my experience it’s always been a joy. Sometimes it’s about the thrill of the mystery, the satisfaction of a finished piece you helped shape, and the quiet pride of knowing your feedback mattered.
When this pattern is released, I’ll be excited to show you the finished project. Until then, I’ll keep knitting under the radar… content in the knowledge that I said yes for all the right reasons.
What Do You Think?
I know test knitting can be a bit of a hot topic, and experiences vary wildly. So I’d love to hear from you… have you ever test knitted a pattern? Was it a positive experience? Maybe you’ve considered it but weren’t sure what to expect?
Let’s chat. I’m always curious to hear different perspectives, especially from within our wonderful community.
I’ve applied to test knit on several occasions but have never been ‘chosen’. On several occasions I’ve been asked for my Instagram handle; I don’t post much there so wonder if that is a deciding factor for the knit designer - they are missing out on 65 years of knitting experience but hi hum do I care - strangely, yes!! Is it like not being chosen for games!
I do often send designers corrections for their patterns after publication.
I've done several test knits over the last 5 or so years, mostly for one designer with a few others tossed in. One I actually used the yarn that was recommended, only because it was a new yarn from one of my favorite dyers and I wanted to try it out. All the rest had a suggested yarn but testers were free to use stash if they chose to. For every test knit that I've done the only payment I received was a copy of the tested pattern and sometimes another pattern, either from the designer's collection or a choice of patterns from Ravelry. I pick and choose test knits based on my schedule and if I can fit in the time needed.