Following the previous “Guidelines for developers”, here are some basic rules/advice for Quality Assurance (aka QA) based on my experience. You will notice that sometimes it is seen from the developer’s perspective, the rest consist of things I’ve seen. Once again, it is not exhaustive, so feel free to add your own! All the rules may not apply to your projects, but I’m sure you can find equivalents. 1. Prepare your tests Have scenarios ready, know what you need to do, list all the variations of things you can come across, etc. 2. A feature cannot be tested by its … Continue reading Guidelines #2 for QA →