Mahathee Dandibhotla’s Post

🌟 A Must-Have Resource for Testers! 🌟 If you're looking for a fantastic source to practice testing or dive deeper into any testing-related aspects, this resource curated by Sarah Deery from Ministry of Testing is highly recommended! 🎯 Whether you're sharpening your skills or sharing valuable learning opportunities with your team, this is worth exploring. https://lnkd.in/gjajNRad Feel free to check it out and share it with your team! #SoftwareTesting #QA #ContinuousLearning #TeamGrowth

🔺 QA Terminology Test. #2.🔺 What is positive testing in the context of functional software testing? Answers: A. It is testing that is aimed at identifying errors and flaws in a program. B. It is testing that is performed only to ensure that the program works correctly. C. It is testing that focuses on negative scenarios and erroneous actions. D. It is testing that verifies that programs function correctly when given correct data and perform expected operations.

✨️ Software test, Note 7: 🔸️ Testing is the process of executing a program with the intent of finding errors. 🔸️ When you test a program, you want to add some value to it. Adding value through testing means raising the quality or reliability of the program.Raising the reliability of the program means finding and removing errors.Therefore, don’t test a program to show that it works; rather, start withthe assumption that the program contains errors (a valid assumption for almost any program) and then test the program to find as many of the errors as possible. 📗 Reference: art of software testing #Software_testing #QA

✨️Software test, Note 6: How much testing is enough? Testing shows only the presence of defects and exhaustive testing is impossible, then it depends on the risk : 🌱 The risk of missing important fault 🌱 The risk of failure cost 🌱 The risk of releasing untested or under tested software 🌱 The risk of losing credibility and market share 🌱 The risk of missing a market window 🌱 The risk of over testing, ineffective testing "Maged Koshty" #Software_Testing #QA

🔺 QA Terminology Test. #1.🔺 What is a test case in the context of software testing? Answers: A. A test case is a program that performs automated testing of an application. B. A test case is a set of data used to run tests. C. A test case is a document that describes the steps to perform a test and the expected results. D. A test case is a data structure used to store data about test users.

🔺 QA Terminology Test. #5.🔺 What is a test case in the context of software testing? Answers: A. This is a document that describes the goals and objectives of testing. B. This is a set of test data used to conduct tests. C. This is a sequence of actions and conditions that determine how testing will be performed. D. This is a report created after testing is completed, containing the results and defects found.

🚨 Exhaustive Testing is NOT Possible! 🚨 In software testing, we cannot test every single input, path, or scenario — it’s just impractical and time-consuming. Instead, we focus on testing what matters most by using risk-based testing strategies. 🔑 Here’s why risk-based testing is essential: 1️⃣ Prioritization: Identify critical features and functionalities. 2️⃣ Efficiency: Allocate resources to high-risk areas. 3️⃣ Time-Saving: Ensure maximum coverage in minimum time. 4️⃣ Quality: Deliver reliable software without chasing perfection. 🛠️ Remember, the goal is optimal testing, not exhaustive testing. Smart testing leads to great results! #SoftwareTesting #QualityAssurance #RiskBasedTesting #QA #TestingBestPractices

🔺 QA Terminology Test. #14.🔺 What is System Level Testing in the context of software testing? Answers: A. This is a type of testing that tests each individual function of a program. B. This is a type of testing that evaluates the interactions between different components or modules of a program. C. This is a type of testing that tests the entire software product as a whole to ensure that it meets the requirements. D. This is a type of testing aimed at checking the performance of a program under different loads.

🔺 Test for QA #13. 🔺 What is test coverage? Answers: A. The number of test cases in a test suite B. The number of tests executed compared to planned tests C. The completeness of the coverage of the software code or requirements for it by tests D. The number of successful tests compared to unsuccessful tests

Difference between a "Test Case" and a "Test Scenario" in QA In Software Testing, understanding the difference between a Test Case and a Test Scenario is essential for effective quality assurance. Let's break it down simply: 👉Test Case: A test case is a detailed step-by-step procedure to verify a particular feature or functionality. It includes input data, expected results, and steps to execute. Example: Verifying login functionality by providing a valid username and password. 👉Test Scenario: A test scenario is a high-level description of what needs to be tested. It's more about identifying the test conditions. It doesn't go into the specifics of inputs or expected outputs. Example: Testing the login functionality for different user roles. In short terms: 👉Test Case: Detailed steps and conditions. 👉Test Scenario: Broad description of what to test. Understanding both helps streamline your testing process and improve the quality of your software! #TestCase #TestScenario #QA #QualityAssurance #SoftwareTesting #SoftwareDevelopment #SoftwareCommunity #TestingCommunity