Skip to main content

ISTQB CTFL Mock Test - Set 2

ISTQB CTFL Interactive Mock Test - Set 2 Ready to ace your ISTQB Certified Tester Foundation Level (CTFL) exam? Practice is paramount! While studying the official syllabus and glossary is essential, testing your knowledge with mock exams is the best way to prepare for the actual exam format, question types, and time pressure.

This blog post brings you a 40-question mock test designed to mirror the structure and difficulty of the real ISTQB CTFL exam. Take your time, answer each question to the best of your ability, and then use the provided answer key to check your performance. Aim to complete these 40 questions within 60 minutes, just like the actual exam.

Important Note on Interactivity: While it would be fantastic to offer a fully interactive quiz here with real-time scoring and highlighting, this blog post format primarily delivers text. To experience an interactive version with automated scoring and feedback (like showing marks and highlighting wrong answers in red), you would typically need a dedicated online quiz platform or custom web development using HTML, CSS, and JavaScript.

ISTQB CTFL Mock Test - Set 2

1. Which of the following statements best describes the purpose of testing?

2. Which of the following is NOT a principle of software testing?

3. What is the primary benefit of early testing (Shift-Left)?

4. Which of the following activities is part of the Test Analysis phase?

5. What is the main difference between a defect, an error, and a failure?

6. Which test level typically involves testing the entire system to verify that it meets the specified requirements?

7. Which of the following is a characteristic of a good test?

8. What is the main objective of regression testing?

9. Which of the following is a type of static testing?

10. What is the primary purpose of a test plan?

11. Which of the following is an example of a project risk?

12. Which test design technique divides the input domain into partitions from which test cases are derived?

13. For a numeric input field accepting values from 1 to 10, using Boundary Value Analysis (BVA), which test values would typically be chosen?

14. Which of the following is a White-Box test technique?

15. What is the primary purpose of a test report?

16. Which of the following is a benefit of using test tools?

17. What is the main purpose of a walkthrough review?

18. Which of the following describes the 'Pesticide Paradox' principle?

19. What is the primary goal of Acceptance Testing?

20. Which of the following is a characteristic of a good defect report?

21. What is the purpose of traceability in testing?

22. Which of the following is an example of a functional test type?

23. What is the role of a test environment?

24. Which of the following is a characteristic of a well-defined test case?

25. What is the primary goal of a test closure activity?

26. Which of the following is a risk of using test automation tools?

27. What is the purpose of a test strategy?

28. Which of the following describes a 'test basis'?

29. What is the primary purpose of a test harness?

30. Which of the following is a key characteristic of an effective test management tool?

31. Which of the following is an example of a non-functional test type?

32. What is the main benefit of using a checklist-based testing technique?

33. Which of the following is a characteristic of a successful review?

34. In a V-model, when does system testing typically occur?

35. Which of the following is a typical task of a Test Manager?

36. What is the main purpose of a test suite?

37. Which of the following is a benefit of independent testing?

38. What is the definition of 'testware'?

39. Which of the following is a characteristic of a 'risk-based' approach to testing?

40. What is the purpose of a 'test closure' activity?

Your Score: 0 / 40

Comments

Popular posts from this blog

How to Inspect Disappearing Elements Using "Emulate a Focused Page" in Chrome DevTools

As web developers, we often encounter frustrating scenarios where elements like dropdowns, tooltips, or custom select menus vanish the moment we try to inspect them in Chrome DevTools. This happens because these elements are often designed to disappear when they lose focus or the mouse moves away. Fortunately, Chrome DevTools provides a powerful feature called "Emulate a focused page" that lets you freeze the page's focus state, making it much easier to debug these elusive elements. The Challenge of Disappearing Elements 👻 Imagine you're styling a complex navigation menu with sub-menus that appear on hover. When you try to right-click and "Inspect" one of these sub-menus, it vanishes! This is a classic example of an element losing its active state because DevTools gains focus, causing the element's blur or focusout event to trigger its disappearance. Traditional methods like trying to quickly click and inspect often fail, leading to wasted time and f...

Ace Your Interview: Top Playwright Interview Questions (with Real-Time Scenarios)

   Playwright Interview Questions Playwright has rapidly become a favorite among automation engineers for its speed, reliability, and powerful feature set. If you're eyeing a role in test automation, particularly one that leverages Playwright, being prepared for a range of questions is crucial. This blog post provides a comprehensive list of Playwright interview questions, from fundamental concepts to more advanced topics and real-world problem-solving scenarios, designed to help you showcase your expertise. Foundational Playwright Concepts These questions assess your basic understanding of Playwright's architecture, key components, and core functionalities. What is Playwright, and how does it fundamentally differ from Selenium? Hint: Discuss architecture (WebDriver protocol vs. direct browser interaction), auto-waiting, browser support, isolated contexts, multi-language support. Explain the relationship between Browser , BrowserContext , and Page in Playwright. Hint: Hiera...

Mastering Waits in Playwright: The Art of Synchronizing Your Automation

Web applications are rarely static. Data loads asynchronously, elements animate in and out, and pages navigate. This dynamic nature means your automation script needs to be smart enough to wait for the application to be ready before interacting with it. Without proper waiting strategies, your tests will consistently break with "element not found," "element not clickable," or "timeout" errors. Playwright offers a sophisticated suite of waiting capabilities, ranging from intelligent auto-waiting for actions to explicit waits for specific network events, page loads, or custom conditions. Understanding and utilizing these waits effectively is fundamental to writing reliable and robust Playwright tests. Playwright's Core Philosophy: Intelligent Auto-Waiting The most significant departure Playwright makes from older automation tools is its built-in auto-waiting mechanism. For nearly all actions (like click() , fill() , check() , selectOption() , etc.), Play...