By the time my patterns reach testers they have already been knit (most of the time by me) and professionally tech-edited and revised, sometimes several times. Even if I think tech-editing is critical to provide the most accurate, detailed and thoughtful patterns, this is not self-sufficient and test knits are as crucial in my opinion. By joining one of my test, you’re joining my team and I’m very grateful for you to volunteer your craft time to help me refine my patterns before publication. As for any classic test knit, feedback is very much appreciated, especially on general clarity of the pattern, the fit of the finished item, and French translation hiccups that may have been overlooked.
Important Rules for my tests
- You need to be able to communicate in English. I’ll only host one test thread for each new pattern, merging English and French versions of the pattern because I don’t have the bandwidth to host two different ones at the moment. In order to have everyone understanding everything and allow anyone to register, we need to write our posts in English.
- You will get an beta version of the pattern and a deadline. The test deadline will be close to the release date of the pattern (think around two weeks prior to it). Please do you best to match the deadline and only sign-up for tests if you’re confident about meeting the deadline. If you are unable to complete the test, please let me know as soon as that becomes clear to you. Life happens and that’s okay, I only need to be kept in the loop because if that happens early in the test process, I might be able to enrol another tester.
- All discussions will be held in Slack. You’ll get both a PDF version of the pattern and a Google Doc version of the pattern which will be our working copy of the pattern. It’s a cloud-hosted file and you need to know how to comment a file to give me your feedback.
- Please do not share the pattern with anyone else. Sometimes a test knit needs to be super secret and neither I or you will be allowed to share pictures of WIPs or FOs before the pattern release day. This will always be clearly stated on the test call page and email. Otherwise, you’re very welcome to share what you’re working on with the world. If you do so, don’t forget to tag me as indicated in the presentation info.
- In order for the test to go smoothly both for you and me, I’ll need to track your progress along the way. Please let us know when you reach the stages described in the requirements section (specific for each test).
- Once all the stages described in the Mandatory section are done, you’ll be marked as “Finished”. You’ll get the pattern for free in your Ravelry library upon publication.
- If you managed to also do the Optional stages, you’ll get a coupon code valid in my Ravelry store without expiration date for one extra free pattern.
- If you’re not done by the test deadline date, but you’ve participated along the way, that’s fine. Then you’ll still get a copy of the pattern for your library, but no coupon code for another.
- If you have taken the test and not participated in the KAL along the way, do not finish by the deadline and do not post your project to the pattern page, well, that’s not really in the spirit so you will not be asked to participate again, your Slack account will be deactivated and will not have a copy of the pattern in your library.
how do I build a test team?
When I choose testers, I try to take several things into account:
- Sufficient knitting experience to complete the project, without needing too much help from me or the other testers;
- Completion record if you’ve already participated in tests (mine of orthers);
- Aiming for yarns from a variety of different budget points and different from the one I used;
- Welcoming back previous testers as frequently as possible while seeking new perspectives by choosing knitters new to my testing team.
what about modifications?
what about pictures?