Gary "The Defect Doctor" Brookes’ Post

Software delivery relies on being fed high-quality assets. What does that mean? Software Requirements – Consumed by everyone in delivery. Developers develop against them. Testers test the software against them. Test Data – Accurate and relevant test data is essential. Without it, you can’t test or develop against specific scenarios. Test Cases – The bridge between requirements and outcomes. They drive quality deliverables. We call this the Outer Loop of delivery. When the Outer Loop is deprioritised, it causes havoc across software delivery. Usually productivity and quality suffer. Catch our webinar recording here -> https://buff.ly/4hw8ZoE

🚀 New Blog Post Alert! 🚀 Ever wondered how to ensure your software meets the real-world needs of users? Dive into my latest Medium article on User Acceptance Testing (UAT) and discover best practices, common challenges, and how to overcome them. Your insights and feedback are welcome! https://lnkd.in/dn6xd9p4

#interviewseries- How do you prioritize test cases in a complex project? Answer: Prioritizing test cases involves assessing the criticality of the functionality being tested and the risk involved. On the basis of these two, we can prioritise our testcases. In some companies, according, to the format, you can assign priority to a test case as 1,2,3 meaning high,medium, low priority. You can assign them in JIRA or any other test management tool also. Other main factors to consider include business impact, user interaction frequency, and the complexity of the feature. Test cases for core business functionalities, frequently used features, and high-risk areas should be prioritized as well. Example: In my previous project, we were testing a financial application where security and accuracy were of utmost importance. We prioritized testing payment processing features first because a failure here would have had a critical business impact. Low-risk, less frequently used features, such as settings configuration, were tested in the later phases. #interviewquestionsandanswers #interviewtips #softwaretesting

Stakeholder: "Can we just add a delete button?"  PM :   - What happens to related or linked items?   - Can this action be undone?   - Should we implement a soft delete instead of a hard delete?   - Are there compliance regulations to consider?   - Do we need an audit trail?   - Who should have permission to delete?   - Should this feature be available to free users?   - What's the confirmation flow?   - Should deletion be immediate, or should there be a delay?   - Should notifications be sent for deleted items?   - How do we handle bulk deletion requests?   - Should we support scheduled deletions?  The Development Team :   - How do we design the database to support this?   - What happens to foreign key constraints?   - How do we optimize performance for bulk delete operations?   - What about rollback mechanisms for accidental deletions?   - Do we need to update the API for this?   - How will this impact front-end workflows?   - What’s the test coverage for this feature?   - Are we accounting for edge cases like dependencies or race conditions?  After analysing …   That “simple” delete button request? Now it's a long task! In both product management and development, nothing is ever as “simple” as it sounds. 😉

When speaking to providers the conversation is different each time. I take into account a range of factors such as your current quality ambitions and how you aim to achieve them, challenges and the barriers that hold you back, the size of your organisation, and any feedback you may have from regulators. It’s important that we understand that no provider is the same and our approach and product is not a one size fits all solution. We value your process and the Mesma software should not only align with the way your organisation operates but also enhance it. 𝗧𝗵𝗲 𝗺𝗼𝘀𝘁 𝗽𝗼𝗽𝘂𝗹𝗮𝗿 𝗰𝗼𝗻𝘃𝗲𝗿𝘀𝗮𝘁𝗶𝗼𝗻 𝘁𝗼𝗽𝗶𝗰𝘀 𝗜 𝗰𝗼𝗺𝗲 𝗮𝗰𝗿𝗼𝘀𝘀 𝗮𝗿𝗲:  👉 𝗧𝗵𝗲 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗿𝗲𝗱𝘂𝗰𝗲 𝘁𝗵𝗲 𝘄𝗼𝗿𝗸𝗹𝗼𝗮𝗱 𝗼𝗳 𝘀𝘁𝗮𝗳𝗳 𝗮𝗻𝗱 𝗰𝘂𝘁 𝘁𝗶𝗺𝗲 𝘀𝗽𝗲𝗻𝘁 𝗼𝗻 𝗮𝗱𝗺𝗶𝗻. 👉 𝗜𝗻𝗰𝗿𝗲𝗮𝘀𝗲 𝗰𝗼𝗻𝗳𝗶𝗱𝗲𝗻𝗰𝗲 𝗶𝗻 𝗸𝗻𝗼𝘄𝗶𝗻𝗴 𝘆𝗼𝘂 𝗮𝗿𝗲 𝗱𝗼𝗶𝗻𝗴 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝘁𝗵𝗶𝗻𝗴 𝗮𝗻𝗱 𝗵𝗮𝘃𝗶𝗻𝗴 𝘁𝗵𝗲 𝗲𝘃𝗶𝗱𝗲𝗻𝗰𝗲 𝗿𝗲𝗮𝗱𝗶𝗹𝘆 𝗮𝘃𝗮𝗶𝗹𝗮𝗯𝗹𝗲 𝘁𝗼 𝘀𝘂𝗽𝗽𝗼𝗿𝘁 𝗶𝘁. 👉 𝗔𝗻 𝗮𝗺𝗯𝗶𝘁𝗶𝗼𝗻 𝘁𝗼 𝗵𝗮𝘃𝗲 𝗼𝗻𝗲 𝗹𝗶𝘃𝗲 𝗰𝗲𝗻𝘁𝗿𝗮𝗹 𝘀𝘆𝘀𝘁𝗲𝗺 𝘁𝗵𝗮𝘁 𝗽𝗿𝗼𝘃𝗶𝗱𝗲𝘀 𝗼𝘃𝗲𝗿𝘀𝗶𝗴𝗵𝘁 𝗼𝗳 𝗮𝗹𝗹 𝗾𝘂𝗮𝗹𝗶𝘁𝘆 𝗮𝗰𝘁𝗶𝘃𝗶𝘁𝗶𝗲𝘀 𝘁𝗮𝗸𝗶𝗻𝗴 𝗽𝗹𝗮𝗰𝗲. #QualityAssurance #QualityImprovement

📣 New Blog Post is Live! 🌟 Software testing often faces constraints on time, budget, and resources—so how can teams prioritize effectively? Enter Risk-Based Testing (RBT)! In this new article, we explore: 🎯 Prioritizing tests by failure risk and business impact 🛠️ Focusing on critical areas to minimize potential risks 🚀 Strategies for smarter resource allocation and enhanced software reliability If you're looking to optimize your testing approach and streamline development, this is a must-read! 🔗 Check out the full article: https://lnkd.in/dbWDW2kx #riskbasedtesting #softwarequality #softwaretesting #testingstrategy #runtimeblog #runtimerevolution

As a Tester 🛡️ , it is also important to look back and focus on the impact we are creating as we add on more and more test cases to our suite. is it really worth doing testing on test cases which are always passing and doesn't cover the business operation logic ❓❔ there are many things we can do to scope our test cases to be more accurate , one of them I came across and will like to share with you 💁 Impact of failure 📈 – Business stakeholders can assign a risk rating on the impact the failure would have on their routine operations . Likelihood of failure 🤦– The technical team can assign a risk rating on the solution developed and its likelihood of failure

Why Software Testing Matters for Quality Assurance In software development, testing is essential for delivering reliable and high-quality products. Here’s why testing is a critical part of the process: ✅ Defect Prevention: Fixes issues early to avoid costly errors ⚖️ Quality Assurance: Ensures software meets all standards 😊 User Satisfaction: A well-tested product means happier users 📉 Risk Mitigation: Reduces risks like financial or reputational loss Dive into our latest blog on Software Testing to learn more👉 https://lnkd.in/gNbYVtx3

Day 8/30 of The Pragmatic Programmer.🙂 Requirements Gathering. It’s important to discover the underlying reason why users do a particular thing, rather than just the way they currently do it. Documenting the reasons behind requirements will give your team invaluable information when making daily implementation decisions. There’s a simple technique for getting inside your users’ requirements that isn’t used often enough: become a user. Are you writing a system for the help desk? Spend a couple of days monitoring the phones with an experienced support person. Are you automating a manual stock control system? Work in the warehouse for a week.

Ensuring the dependability and effectiveness of software applications has become indispensable in the contemporary digital age. The ever-increasing complexity of software and diverse platforms necessitates robust testing methodologies. Functional testing, a cornerstone in quality assurance, focuses on simulating actual system usage without assuming any internal system structure. Unlike some approaches, it refrains from making assumptions about the system’s internal structure. This blog delves into the nuances of functional testing, exploring its significance in ensuring the seamless performance of software applications. 🔗 Check comment section