New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISTQB ATTA Exam - Topic 10 Question 118 Discussion

Actual exam question for ISTQB's ATTA exam
Question #: 118
Topic #: 10
[All ATTA Questions]

Part 7 "Test Process & Incident Management"

The development manager asks you to identify suitable test coverage entry criteria for a component test. Which TWO of the following would you recommend as appropriate for entry criteria to a component testing phase? 2 credits [K3]

Show Suggested Answer Hide Answer
Suggested Answer: D, E

Contribute your Thoughts:

0/2000 characters
Tony
16 hours ago
E is a must-have for quality assurance!
upvoted 0 times
...
Larae
6 days ago
C seems unnecessary; who needs a test log before testing?
upvoted 0 times
...
Precious
11 days ago
Wait, isn't 100% coverage unrealistic?
upvoted 0 times
...
Joesph
16 days ago
Haha, 100% statement coverage? Good one! That's like trying to catch a greased pig. B and E are the practical choices here.
upvoted 0 times
...
Cheryl
21 days ago
Hmm, I'd say B and C. Test logs are crucial for tracking progress and identifying issues. Can't have a proper component test without that.
upvoted 0 times
...
Blythe
27 days ago
I'd go with B and D. Code review is a must before you even think about testing. Gotta make sure the code is up to par first.
upvoted 0 times
...
Mose
1 month ago
B and E are definitely the way to go. No critical defects and a clean static analysis - that's the sweet spot for component testing.
upvoted 0 times
...
Ronny
1 month ago
I feel like "Code review completed" is a solid choice too. It ensures that the code has been vetted before we start testing, right?
upvoted 0 times
...
Wai
1 month ago
I recall that having a test log available is important, but I'm not convinced it should be a strict entry criterion. Maybe it’s more of a best practice?
upvoted 0 times
...
Chauncey
2 months ago
I'm not entirely sure about 100% statement coverage being necessary. I remember some practice questions suggested that coverage metrics can vary based on the project.
upvoted 0 times
...
Teri
2 months ago
I'm leaning towards B and E as the best choices here. No critical defects is a must, and static analysis can help catch some issues before we dive into component testing.
upvoted 0 times
...
Leonie
2 months ago
I'm a bit unsure about C and E. A test log seems more relevant for the overall testing process, and static analysis is good but may not cover everything we need to check at this stage.
upvoted 0 times
...
Elke
2 months ago
I think B and D are good options - no critical defects and a completed code review would help ensure the component is ready for more thorough testing.
upvoted 0 times
...
Earleen
2 months ago
I think A is important too, though.
upvoted 0 times
...
Deandrea
2 months ago
I think option B, "No critical outstanding defects," is definitely a good entry criterion. It makes sense to start testing only when the critical issues are resolved.
upvoted 0 times
...
Margot
3 months ago
B and E for sure. Gotta make sure the code is solid and the static analysis is clean. No point in testing a hot mess!
upvoted 0 times
...
Carri
3 months ago
B and D are definitely the way to go!
upvoted 0 times
...
Jennifer
3 months ago
Okay, let's see. I'm pretty sure 100% statement coverage is a bit too strict for just the component testing phase. That's more of a full system testing goal.
upvoted 0 times
...
Daniela
3 months ago
Hmm, this is a tricky one. I'll need to think carefully about the different options and which ones would be most appropriate for component testing entry criteria.
upvoted 0 times
...

Save Cancel