Tech Notes Documentation

Insights, tutorials, and deep-dives into QA automation and software engineering.

QA Process & Strategy Last updated: 10 Agustus 2026

End-to-End QA Testing Process: From Risk Analysis and Test Planning to Execution

Last updated: August 14, 2026

Ensuring the quality of software is not a trial-and-error guessing game, but a structured process. Before discussing advanced tools or automation scripts, a QA must understand the core business. Adhering to the ISTQB (International Software Testing Qualifications Board) standard, testing phases must be executed step-by-step.

QA Lifecycle
🔄 ISTQB-Aligned Systematic Stages
1. Planning & Control → 2. Analysis → 3. Design & Implementation → 4. Execution & Defect Management → 5. Test Completion 📊
1. Test Planning

This is the foundation. If the project team (like a Product Manager or Developer) asks, "What is actually inside a Test Plan document?", the answer is simple. A Test Plan is an agreement that contains:

  • What we test (In-Scope): e.g., We are only focusing on testing the property search feature.
  • What we DO NOT test (Out-of-Scope): e.g., The user profile feature is not tested because no code changes were made there.
  • Who does what: Task delegation, such as who tests on Android devices versus iPhones.
  • Timeline: When testing begins and when it is targeted to finish.
💡 Example: The team is releasing a "Property Search Filter" feature. In the Planning document, QA agrees that the initial testing will be done manually (clicked by a human). However, QA also requests extra time at the end of the week to start writing automation code, so in the future, this feature won't need to be tested manually over and over again.
2. Test Analysis (Risk Analysis)

At this stage, QA focuses on reading the feature guidebook (PRD) and puts themselves in the shoes of a normal user. The goal is to figure out: "Which part of this application will cost the company the most money if it breaks?"

💡 Example: While reading how the "Contact Agent Form" works, QA identifies a major risk: "What happens if a buyer successfully clicks 'Send Message', but the notification email never reaches the real estate agent's phone?" This scenario is immediately marked as top priority because failing here means losing a potential buyer.
3. Test Design & Implementation

Once we know which parts are risky, QA creates a "testing playbook" called Test Cases. A Test Case contains step-by-step instructions, like: Click this, type that, and expect a success message to appear.

This is where automation starts to come in. If the steps are too long and boring to click manually every day, QA starts building a robot program to do it.

💡 Example: QA creates a scenario to ensure "Sort Property Prices: Lowest to Highest" works smoothly. Manually checking the prices of hundreds of houses one by one is exhausting. So, QA starts writing automation scripts using Playwright to have a robot check the visual order on the screen, and uses Postman to ensure the data coming from the server (API) is actually sorted.
4. Test Execution & Defect Management

This is the "hands-on" phase. The application is actively used and buttons are clicked (either by a human or by automation robots). If something doesn't work as it should (a bug or defect), QA must quickly report it to the developer with clear evidence.

💡 Example: Developers just pushed new code. The automation system (via GitHub Actions) instantly runs the script QA built earlier. It detects a bug: "House images do not show up if the status is marked as 'Sold'." The system automatically logs this issue into Jira, complete with a screenshot, so developers can fix it right away.
5. Test Completion

Once everything is tested and major issues are fixed, QA doesn't just say "Okay, we're done." QA must provide a formal "Report Card" called a Test Summary Report to the whole team as proof that the application is safe and ready for the public.

💡 Example: Before the property portal is launched, QA sends a summary to the Slack/Teams group: "Release v4.0 Testing is Finished. Search and Agent Forms are 100% safe. There is 1 minor bug regarding a button color that does not block users. Conclusion: The app is Ready for Go-Live."
Conclusion

Structured QA work ensures no gaps are missed. Automation (using robots to test) is not a replacement for manual testing, but a helpful tool so we can test faster and more accurately. Product quality must be strictly guarded from the initial idea all the way to the consumer's hands.