Hi peeps, So I’m fairly new to Riblr and have been wanting to test patterns on here. A lot of the terminology and requirements are fairly self explanatory but as someone who’s never seen this before, what does it mean when creators ask for a ‘journal’?
Also, what else makes a perfect pattern tester from the perspective of creators so that I can do a good job :3 thanks!
A journal is basically a review of a pattern. So if you where to go to any pattern on the website, below the pattern description there are reviews and makes, which has photos of the finished object made by other crafters. To make a journal all you need to do is, once you have finished the pattern, take a nice photo, at the very end of rhe pattwrn there is a bit that says “you have completed this pattern… review this pattern” and if you click on that it will take you to the jounral where you can upload the photo and write out your thpughts on the pattern. (You can also make a jounral by click the journal button at the top of the page for a desktop or at thw bottom of the oagw for a phone)
As for what makes a good tester:
Can not stress this enough, but someone who is willing to read through the ENTIRE pattern and be through. I have gotton testers who clearly just want to pattern for free, so they’ll make it, but will have no notes of how it was or anything they saw amiss in the pattern. We want to know your thoughts and don’t want to publish mistakes.
Have nice photos of their finished objects. When picking testers, most designers will look at the makes of the applicants and how nice the photos look can be a big deciding factor on whether you are choosen or not. Designers often make tester appreciations and will use tester photos in promotional material to show how it turned out for other crafters and you’d want your pattern to look as best as it can. (So things like good lighting, clean/cohesive background, etc.)
COMMUNICATION. If you’re having trouble understanding something, you found a mistake, or if you had something come up and can no longer test:; contact the designer to let them know, don’t put the mistake you found in your journal where its public without giving the designer a chance to fix it or just completely ghost a designer.
Simply put, add photos of progress. Write the yarn and hook size used. (maybe more for others and yourself later). NEVER put issues with the pattern in the journal. That is for the message or chat.
Communication
The first and maybe most important is communication. I check in daily with the patterns I test. Hmmm, sometimes by adding photos to the journal … they can be deleted later to fine tune the overall look.
Communication
While this seems duplicated, this is separate. Do not be shy of telling us what you think. Can it be better? More clear? Does it need a video. Little things mean a lot.
Spellcheck
Self explanatory.
Check for consistency.
Check row numbers, wording etc …
Row counts
This is important to me. If the sts add up to 10, yet the ending st # is [12] … that needs addressed.
MOST important
DO NOT just do it the way you THINK it is meant to be. Do it as written, then communicate what would make it better.
Offer ideas
While it’s not always possible, it is helpful to have feedback of a better wording, etc …
Remember who’s pattern it is
Mostly, what this says. While you offer help, it is ultimately the creator’s pattern. They don’t have to incorporate what you suggested
Don’t steal the pattern
in any way.
Fun
Maybe this could have been first, but have fun. Be respectful. Be helpful.
Do Not
Pet peeve here. Do not simply make the pattern and say: Done. Found no issues. This is almost always a do not use tester again for me. Especially if multiple issues are found later …
All of the above for sure. My thoughts which include repeats:
Active and keeps open communication. I check in with testers after I’ve been ghosted a few times. If people don’t respond to check in (unless I was proudly notified), I remove them.
Finishing early is great but rushing through and not finding errors is what can kill a pattern. I’ve had multiple testers somehow not notice entire errors in rows where I didn’t use all the stitches or counts are off. Don’t just assume it’s your error and ‘make it work’ cause it’s possible it isn’t. I’d rather you question my pattern than me have an error in a published pattern since it looks bad on me.
Don’t apply if you don’t have the time (could be too much on your plate or the designers due date is too close). Procrastinators cause a delay in releasing patterns. While it’s not a huge deal, it’s a bummer to have to wait and makes me feel like the bad guy if I tell people no to extensions. If you do need an extension, it’s helpful to prove you’re working on it (progress Pic or something).
I love partial journals that show your progress but some don’t. Biggest thing is don’t put errors in the journal. Put them in the group chat so they can be fixed. Journals stick around so people may think the error is in the final. Now if the designer doesn’t fix it, def put it in the journal after it’s published with the error.
Oh and when applying for a tester call, read the whole thing. People who don’t, in my eyes, will not be good testers since if they can’t read the tester call post, I can’t trust them to read every word of the pattern. Like intro, materials, everything.
About the pattern tester - you can’t really know until they actually start testing. If I would pick, I would look at skill level. Check out their makes and shop. Look at their stitches, especially in the recent posts. Also, I think seeing them in other posts/ being active in community is a great thing to look for.