Get Ahead with Our Exam Q&A

Explore our extensive collection of questions and answers to enhance your learning experience and prepare for exams effectively

Decision Table Testing maps input conditions to outcomes in a tabular format, ensuring all combinations are considered.

Non-Functional Testing evaluates the characteristics of the system, such as its performance, usability, security, and reliability. The other options are types of Functional Testing, which verify what the system does.

Usability Testing assesses how easy and pleasant the software is to use from an end-user perspective.

Security Testing focuses on finding weaknesses that could be exploited, ensuring data and system integrity.

Smoke Testing (or Build Verification Testing) is a preliminary check to determine if a new build is stable enough to proceed with further, more detailed testing. If the smoke test fails, the build is rejected.

Retesting is specific: you run a failed test case again to ensure a bug has been fixed. Regression Testing is broad: you test existing, previously working features to ensure the new changes haven’t broken anything.

After a minor change or bug fix, Sanity Testing is performed on that specific area to quickly verify that the change works as expected and hasn’t obviously broken the related functionality. It’s a subset of regression testing.

Equivalence Partitioning reduces the number of test cases by grouping inputs into equivalent classes, testing one representative from each.

Boundary Value Analysis targets the edges of input ranges (e.g., minimum, maximum) where defects are more likely to occur.

Component Testing (a form of Integration Testing) verifies individual components before full system integration.

Entri Contact Image

Get Expert Advice for Free: Register for Your Free Consultation Now!

    [honeypot honeypot-100]