WorksheetsCritical Thinking dalam Proses STLC
Total questions: 10
Worksheet time: 5mins
What is the primary definition of critical thinking in Quality Assurance?
Following established testing procedures without question
The objective analysis and evaluation of information to form reasoned judgments about software quality
Criticizing development team's work to find more defects
Thinking negatively about software functionality
Which of the following is NOT one of the six pillars of critical thinking?
Clarity
Creativity
Precision
Fairness
Confirmation bias in QA testing refers to:
Confirming that all tests have passed successfully
The tendency to search for, interpret, and recall information that confirms pre-existing beliefs
Getting confirmation from stakeholders before testing
Bias towards confirming requirements are met
When designing test cases, which approach best demonstrates critical thinking for edge cases?
Only test the happy path scenarios
Systematically identify boundary conditions, invalid inputs, and unusual user behaviors
Copy test cases from previous similar projects
Focus only on functional requirements
The "5 Whys" technique in Root Cause Analysis helps QA professionals to:
Ask five different people about the same defect
Iteratively drill down to the fundamental cause by repeatedly asking "why"
Create five different test scenarios for each defect
Question why testing is necessary in the first place
In risk-based testing, critical thinking helps QA professionals to:
Test everything equally without prioritization
Identify, assess, and prioritize areas based on probability and impact of failure
Avoid testing risky areas completely
Only test low-risk functionalities to save time
Groupthink bias in QA teams can lead to:
Better team collaboration and faster testing
Suppression of dissenting opinions and reduced critical evaluation of testing approaches
More comprehensive test coverage
Improved communication with developers
When analyzing user stories for hidden assumptions, a critical thinking approach involves:
Accepting user stories as complete and accurate
Questioning implicit requirements, identifying gaps, and validating assumptions with stakeholders
Only testing what is explicitly written in the story
Making assumptions based on previous similar features
A Fishbone Diagram (Ishikawa Diagram) in QA root cause analysis is used to:
Create a visual hierarchy of test cases
Systematically categorize and visualize potential causes of a defect or problem
Track the flow of data through the system
Organize team members by their expertise areas
Which pillar of critical thinking is most important when evaluating the logical flow of test execution results?
Accuracy
Logic
Relevance
Clarity
