Factor | Details / Explanation |
---|---|
Regulations & Security | Mission/safety-critical orgs may prefer commercial tools due to standards and certifications. |
Financial Aspects | - Open-source: Lower initial cost, community-supported. - Commercial: Licensing and support costs. - Custom: Unpredictable cost; depends on dev phase. Maintenance and training costs apply to all. |
Stakeholder Requirements | Tools must address all key stakeholder needs. Custom tools may fit best when others can't meet specific needs. |
Software Landscape & Strategy | Tool selection must align with existing tools, integrations, preferred vendors, and internal support models. |
🧪 Q1 (K2):
Why might a safety-critical software company prefer a commercial tool?
A. It’s cheaper
B. It offers free training
C. It often comes with necessary certifications
D. It supports more file formats
✅ Answer: C. It often comes with necessary certifications
🧪 Q2 (K2):
Which tool type typically has the lowest initial cost?
A. Custom tool
B. Open-source tool
C. Commercial tool
D. Legacy tool
✅ Answer: B. Open-source tool
🧪 Q3 (K3):
Your company uses a full-service support model with a preferred vendor. What should you consider before choosing a new test tool?
A. The color scheme of the tool
B. If the tool fits within the current vendor ecosystem
C. Whether the tool is open-source
D. The length of the user manual
✅ Answer: B. If the tool fits within the current vendor ecosystem
🧪 Q4 (K3):
A tool meets most stakeholder needs, but lacks one critical requirement. What should be considered?
A. Modify the stakeholder need
B. Customize a commercial tool
C. Consider a custom tool if other tools fail to meet requirements
D. Select the tool anyway and manage later
✅ Answer: C. Consider a custom tool if other tools fail to meet requirements
🧪 Q5 (K2):
What is a potential disadvantage of custom tools?
A. Lack of branding
B. Easily replaceable
C. Cost and development effort are hard to predict
D. Too many users
✅ Answer: C. Cost and development effort are hard to predict
🧪 Q6 (K3):
An organization is considering a new test tool but already has integrations with specific defect management and CI/CD systems. What is most important?
A. Choosing an open-source tool
B. Selecting the most expensive tool
C. Ensuring the new tool integrates well with the current systems
D. Asking developers what they prefer
✅ Answer: C. Ensuring the new tool integrates well with the current systems
🧪 Q7 (K2):
Which of the following is true for all types of tools (commercial, open-source, custom)?
A. They are free to use
B. They require no training
C. They incur maintenance and support costs over time
D. They only work for manual testing
✅ Answer: C. They incur maintenance and support costs over time
🧪 Q8 (K3):
A stakeholder insists on a feature that no tool provides. What is the most logical decision?
A. Use the tool that is most visually appealing
B. Ignore the stakeholder
C. Consider building a custom tool to fulfill the requirement
D. Buy a tool with similar features and hope it works
✅ Answer: C. Consider building a custom tool to fulfill the requirement
🧪 Q9 (K4):
You’re comparing two tools: one integrates easily with your software landscape, but is costly. The other is cheap but has poor integration. Which is likely better?
A. Cheaper tool, as cost matters most
B. Integrated tool, since long-term maintenance and fit matter
C. Neither, select a third
D. Use both
✅ Answer: B. Integrated tool, since long-term maintenance and fit matter
🧪 Q10 (K3):
When deciding on a tool, why is it important to understand the software landscape?
A. To avoid choosing trendy tools
B. To ensure color matching with UI themes
C. To support integration and align with tool strategy
D. To impress auditors
✅ Answer: C. To support integration and align with tool strategy
No comments:
Post a Comment