"The additional learning material for our testers is easily available on our Discord server."
In this article, you'll discover additional content from our Discord server to improve your testing skills and be more productive once you've read and understood all Academy articles in our Getting Started collection.
We know that getting the hands-on testing takes time and additional personal effort, so to help you build a solid testing foundation, we've selected the best Discord posts written by our Education Team to show you everything from best practices from do's and don'ts to tutorials, for both mobile and desktop devices, and even streaming testing.
Posts About Testing
If you're new to the platform, navigate like a pro after these 2 excellent posts: A survival kit for new testers on the Test IO platform – Part 1 and here is Part 2.
These are 10 things testers should do while testing on every single test cycle.
To keep growing on our platform, follow the advice on How to be a valuable member of the Test IO Community.
Despite what they're called, rejections are good for improving what we do and getting better at testing. Learn how to get the most from them with the post: How to deal with rejections.
You've learned about your scores and started worrying about them? Do not worry; there is always a way to increase them, and this post tells you how to do, How to increase your quality after a massive drop-down.
Learn how to test on other languages from the post: How to test German websites and apps if you don't speak German?
The types of testing Test IO offers to the customers are an excellent way to start picking the proper test for you. In this post, Test IO's type of tests on the table! You'll know what these are and what is expected during each type of test.
Find 9 pieces of advice from Team Leaders on improving your testing: What can we learn from TLs? A curated list of advice for testers.
Tips on looking for bugs are shared in the post, Tips from Academy - Where to look for bugs.
Find 3 different methods to test directly from experienced testers: What can we learn from New Testers? From their own experience to all of us!
If you're struggling with managing your time because you're joining many test cycles simultaneously, you can find helpful tips in the post, How to Efficiently Manage Time. We even created a miniseries on our YouTube channel called Work Smarter, Not Harder that you should listen to. For instance, listen to this episode, How To Be More Productive While Testing.
After some testing, you may want to start trying new paths while testing; here are some excellent ideas: Where to look for bugs on an app if you run out of ideas.
User Stories are easy to execute and provide much information about a product's design. Learn how to avoid the most common mistakes while executing them, User Stories… mind the length of screencasts!
Reproductions are a quick start for testing with Test IO. They give you an idea of bugs and how testers do the job in just 15 seconds or less; however, there are many ways to get them wrong. Learn how to execute them with the post, Bug Reproductions survival tips.
One of the most important features to understand is Navigation. In this article, you'll find a description and a PDF with examples of how this feature is presented on desktop and mobile devices according to different designs, Glossary: Navigation.
You are new to the platform and got a request from the Team Leader; now, what do you do? This post is a survival guide to attend thoroughly to any request, Deal With TL's Request Like A Pro.
If you are new to working from home, this is your post, How to work from home – a survival guide.
If you haven't heard about performance testing, here is the best post to start with: Performance tests 1 on 1.
Post About Functional, Visual and Content Bugs
The Cart is one of the most essential features regarding functional bugs. Understanding how it works will help you catch important, highly paid-bugs. Find how to do it in the post: A few testing tips for testing the shopping cart.
Testing validations are commonplace while testing since forms can be found everywhere! In this post, you'll learn how to do so: How to avoid rejections with validation bugs?
There is no single rule when it comes to classifying defective links! Here are 4 more general cases to help you correctly classify a broken link as functional (any severity) or content bug: Broken links – 404 the ultimate guide.
The browser back button is a vital testing element because it is commonly used for users! This post explains the browser structure and the back button behaviour to test the functionality correctly.
By now, you've already learned what a crash log is, so deep your knowledge of iOS crash logs with the references in this post and what you should be looking for on these files can be found in this other post. And for Android devices, What info should you include in your bug report in order to help devs while testing an Android app?
Content and visual bugs must have screenshots for documentation, so learn how to make them the best way possible on mobile devices: How to mark screenshots using Android and iOS devices. And for functional bugs, here is a guide for screencasts, Testing Advice – How to use ApowerRec.
You already know that rapid tests only look for critical issues. Now it's time to learn how to identify this severity and work on these special tests with a 2 parts post, Rapid Tests And How To Stay Focused Only On Critical Issues - Part 1 and Rapid Tests And How To Stay Focused Only On Critical Issues - Part 2.
Endless loading issues are a particular type of bug. In this post, so, endless loadings, hmph! You'll get to know how to report them properly.
Whenever you need to change the region on your Apple devices, you can follow this comprehensive step-by-step tutorial on how to do so on the AppStore.
Testing on the desktop is convenient, but we also have numerous mobile testing! Do you know how to use them both for testing? Learn everything about it, How to mirror your phone to a PC.
Posts About Reporting
Good reports are also well written, so learn how to avoid spelling mistakes and typos by following this advice.
Good reports also look good! Enhance the readability of your reports with this post on How to format bug reports?
Calling buttons by the correct name is critical for understanding a bug and, more importantly, a report. Here are the most common button names to use on your bug reports.
When identifying underlying issues (repetitive or duplicate bugs), there are several layers to consider and ways to find them. Find out how to do so on Repetitive problems or déjà-bug?
Basic HTML is always helpful, especially when you know what is needed during testing, and this post covers it all, HTML Basics - SOS For Noobs - Locating The Element On Which The Bug Occurs.
And because we can continuously improve things, you can find more information to look more professional while testing using browser profiles.
Sometimes, customers ask for information about our devices; find out how and where to find it on the post: how to find information about your devices and browsers.
Posts About Streaming Testing
If you need to use a VPN, learn about it and how to use a VPN connection on Roku and Chromecast devices".
Learn the most streaming device buttons and function names to report your bugs properly.
And there is even more about streaming devices! Here are some apps you should download for these particular tests.
Now you've all the possible knowledge you might need to keep improving your testing and building up your career with Test IO directly from our Discord server; as you can see, it's more than just a server… it is a Community.