As Mediavine develops new products for publishers, we often need beta testers to use those products, offer feedback, and help us to improve. This is where you come in!
If you are interested in beta testing Mediavine products - anything from new ad units to Trellis or Create, etc, you can email us at email@example.com to let us know. We will get you added to the right list!
What's a beta tester?
Beta testers are real users who are willing to try out new software products and give valuable feedback to our team. So much of what we do here at Mediavine is based on customer feedback - what you send us can help shape the final product!
Being a beta tester is similar to helping taste-test a new recipe. Are the muffins too salty? Not fluffy enough? Too dry? All of this is important feedback that will help the baker make a better muffin 🧁
It's the same for software, and we need Beta Testers who won't hold anything back when it comes to feedback.
If I sign up to be a beta tester, what should I expect?
There may be bugs. You're trying something before it's available to the public, so it's important to remember that there will be kinks to iron out. Your experience with the beta might not be 100% perfect, and that's normal.
We want your feedback. If you find a bug, we want to know. We hope that you'll be honest and transparent with our team about what is working, and what isn't. If you have ideas, we're all ears.
How do I know if I would be a good beta tester?
A good beta tester will be level-headed and patient when they run into issues. Our software is built from scratch, and part of our process is to log and prioritize every bug. It can sometimes take time to work through every issue depending on the priority assigned.
We're looking for bloggers who will offer clear, concise, detailed feedback, and who will be responsive to messages so we can help get to the bottom of any issues, ASAP.
It can help to be somewhat technology savvy, but that's definitely not a requirement — we want our products to be easy to figure out, no matter your skill level.
What are the best practices?
Back up your website often. It's always a good idea to make frequent copies of your site. Your host or tech help might be able to recommend a plugin that can do this for you automatically, or you can follow these instructions from WordPress.
Take lots of notes and screenshots or screen recordings. Something not working? Record all the steps you took to get to the bug, and show us what is happening with a screenshot or a screen recording. Our team likes Skitch and Gyazo for screenshots, and Loom for screen recordings, but use whatever you're comfortable with.
Don't test on your most popular content. We understand why you'd want to try something new on your most popular content, but we'd actually recommend testing on something that your readers don't frequent — just in case.
If I find a bug, what should I do?
Check that you're on the latest release of the plugin or theme that you're testing. In your WordPress dashboard, go to Plugins. Next to Mediavine Create, click the 'Check for updates' link. It's possible that by the time you've noticed a bug, we've already put out a fix!
What device are you using? e.g. Macbook Pro, PC, iPhone X, Samsung Galaxy S8, etc.
What browser are you using? e.g. Chrome, Safari, Firefox, etc.
What steps did you take to get the bug? Keep this part short yet detailed.
Example feedback: "Earlier I was on the Settings page, changed my body font, then clicked Save. When I returned to my site, the font change hadn't saved."
Any attachments? If you were able to take screenshots or get a screen recording, please send those as well!
Interested in being a beta tester?
Great! We'd love to have you.
Email us at firstname.lastname@example.org and we will get you added!