Sample questions
Qa Exploratory Manual TestingDifficulty 1
What best describes exploratory testing?
- aRunning a fixed suite of pre-written scripted test cases without deviation
- bDesigning and running tests at the same time, letting each result shape the next step✓
- cWriting automated checks that run on every code commit
- dReviewing requirements documents to confirm they are complete before coding starts
Explanation:Exploratory testing is defined by the parallel, iterative nature of test design and execution: the tester learns about the system while testing it, and each observation shapes the next action. It is not the execution of a pre-fixed script, not automation, and not a documentation review.
Qa Exploratory Manual TestingDifficulty 1
How is exploratory testing generally positioned relative to test automation?
- aAs a replacement for automation once a team becomes mature enough
- bAs a competing approach where a team must pick only one
- cAs a complementary approach, working alongside automation rather than replacing it✓
- dAs a legacy technique that modern automated pipelines have made obsolete
Explanation:Exploratory testing and automation address different needs and are complementary, not rivals. Automation is excellent at repeatedly verifying known expectations quickly and consistently; exploratory testing is better suited to discovering unanticipated problems, usability issues, and gaps that no one thought to script. Mature teams use both together.
Qa Exploratory Manual TestingDifficulty 1
In session-based test management, what is a "session"?
- aA time-boxed block of testing focused on a mission, closed out with a report✓
- bA single automated test run triggered by a scheduler
- cThe period between two software releases
- dA meeting where the team reviews open bugs
Explanation:A session in session-based test management is a time-boxed, focused period of testing work directed at a specific mission or charter, uninterrupted by other tasks, and closed out with a report summarizing coverage, findings, and any deviations from the plan. It is not an automated run, a release window, or a bug-review meeting.
Qa Exploratory Manual TestingDifficulty 1
What is a "test charter" in exploratory testing?
- aA step-by-step script listing the exact clicks and inputs to perform
- bA legal document signed by the customer before testing begins
- cThe final report listing every bug found during a release
- dA short mission-and-scope statement that guides a session, not an exact-step script✓
Explanation:A test charter is a concise statement of what to explore, why, and with what resources or constraints in mind — it sets direction and scope for a session but deliberately leaves the exact steps to the tester's judgment, which is what allows exploration. It is not a detailed script, a legal document, or a final bug report.
Qa Exploratory Manual TestingDifficulty 1
What does usability testing primarily evaluate?
- aWhether the application returns correct results under heavy concurrent load
- bHow easily real users can accomplish their goals with the product✓
- cWhether the source code follows the team's style guide
- dWhether the database schema is normalized correctly
Explanation:Usability testing focuses on the user's experience: can people understand the interface, complete tasks efficiently, and avoid confusion or frustration. It is unrelated to load handling, code style, or schema design, which are covered by other kinds of testing or review.
Qa Exploratory Manual TestingDifficulty 2
What is the basic goal of accessibility testing?
- aConfirming the application loads within an acceptable response time
- bConfirming the application encrypts data correctly in transit
- cConfirming that people with disabilities can perceive, navigate, and use the product✓
- dConfirming that the API returns the correct HTTP status codes
Explanation:Accessibility testing checks that a product can be perceived, understood, navigated, and used by people with a range of disabilities, including those relying on assistive technology, keyboard-only navigation, or screen readers. Response time, encryption, and status codes belong to performance, security, and functional testing respectively.