Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISTQB Exam ISTQB-CTFL Topic 2 Question 27 Discussion

Actual exam question for ISTQB's ISTQB-CTFL exam
Question #: 27
Topic #: 2
[All ISTQB-CTFL Questions]

Which review type, also known as a ''buddy check'', is commonly used in Agile development?

Show Suggested Answer Hide Answer
Suggested Answer: C

Test Management tools are designed to support the planning, execution, and monitoring of the testing process. They provide features for managing test cases, test runs, tracking defects, and reporting on testing activities. However, the statement in option C describes Test Management tools as monitoring and reporting on the system's behavior during testing activities, which is not accurate. Test Management tools focus on the testing process itself rather than on the behavior of the system under test.

Test data preparation tools (A) indeed create and manage test data for use during test execution.

Test execution tools (B) automate the execution of test cases and the comparison of actual outcomes against expected results.

Test comparators (D) are tools that compare actual outcomes with expected outcomes, highlighting discrepancies.

Therefore, option C is the correct answer as it inaccurately describes the function of Test Management tools.


Contribute your Thoughts:

Gretchen
1 months ago
Informal review, for sure. Agile is all about being quick and nimble, not stuffy old 'inspections'.
upvoted 0 times
Una
1 days ago
Technical reviews can be helpful for ensuring code quality in Agile projects.
upvoted 0 times
...
Lenna
2 days ago
I think walkthroughs are also important for collaboration and communication in Agile.
upvoted 0 times
...
Wynell
1 months ago
I agree, informal reviews are definitely more in line with Agile principles.
upvoted 0 times
...
...
Tamie
1 months ago
Hmm, 'buddy check'... I'm going with D, Informal review. Sounds like something Agile folks would do.
upvoted 0 times
...
Ryan
2 months ago
It's got to be Technical review. Agile is all about the technical side, right? This is the one.
upvoted 0 times
Laila
1 days ago
I'm going with Technical review as well. It seems to fit the Agile development process.
upvoted 0 times
...
Casie
4 days ago
I'm not sure, but I think Walkthrough is also a review type used in Agile.
upvoted 0 times
...
Reyes
29 days ago
No, I believe it's actually Inspection. That's the one commonly used in Agile development.
upvoted 0 times
...
Sang
1 months ago
I think it's Technical review too. It's all about the technical details in Agile.
upvoted 0 times
...
...
Jamal
2 months ago
Definitely Walkthrough. Agile teams love to get together and walk through the code, don't they?
upvoted 0 times
Marvel
23 days ago
Absolutely! It's a great way for team members to collaborate and provide feedback on the code.
upvoted 0 times
...
Angella
29 days ago
Yes, you're right! Walkthroughs are a common practice in Agile development.
upvoted 0 times
...
...
Sarina
2 months ago
I think it's Informal review. Agile teams often do quick, informal check-ins with each other to catch issues early.
upvoted 0 times
...
Wilda
2 months ago
I'm not sure, but I think it might be C) Technical review because it involves technical details.
upvoted 0 times
...
Joseph
2 months ago
I agree with Kaitlyn, Walkthrough makes sense for Agile development.
upvoted 0 times
...
Kaitlyn
2 months ago
I think the answer is B) Walkthrough.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77