Skip to Content
Home └International Software Qualification Test Board └Quiz

International Software Qualification Test Board

0 %

Completed

Course content

Quiz

10 XP
Prev Next
Fullscreen Share

ISTQB

The International Software Testing Qualifications Board (ISTQB) is a globally recognized organization that provides certification for software testers. It was established to create a standardized and professional approach to software testing across the world.

ISTQB certifications help individuals understand software testing concepts, improve testing skills, and build a strong career in the software testing field.

Rating
0 0

There are no comments for now.

Join this Course
to be the first to leave a comment.

1. In a sequential SDLC such as waterfall, what is the MAIN impact on dynamic testing?
It can start as soon as user stories are drafted It usually starts only after most coding is complete It must be done before any design is finalized It is replaced by static testing only
2. Which statement BEST describes how the SDLC model influences testing
Testing is independent of the SDLC and remains identical The SDLC influences timing, scope, and documentation of testing Only the number of test cases depends on the SDLC Only non‑functional tests depend on the SDLC
3. In iterative or incremental SDLC models, which testing characteristic is MOST typical?
Only one large system test at the end Static testing only, dynamic testing later Repeated cycles of static and dynamic testing in each iteration No need for regression testing
4. Why does frequent delivery of increments in iterative models increase the importance of regression testing?
Each increment removes the need for earlier tests Defects cannot occur in later increments Existing functionality can be broken by new changes Documentation becomes unnecessary
5. In Agile projects, which aspect MOST supports extensive automated regression testing?
Heavy upfront design documentation Stable requirements with no changes Short iterations and frequent integration of code Prohibition of static testing
6. Which testing practice is COMMON to all SDLC models?
Testing only after deployment Completely eliminating static testing Having corresponding test activities for development activities Using only manual exploratory testing
7. Which SDLC model MOST strongly assumes that each iteration delivers a working product increment?
Waterfall V‑model Iterative or incremental models Big‑bang model
8. In a V‑model, how are test levels typically related to development phases?
Test levels are unrelated to development phases Each development phase has a corresponding test level Testing occurs only at component level Testing occurs only at acceptance level
9. Which factor is MOST affected when testing is not aligned with the chosen SDLC?
Number of developers required Effectiveness of test levels and test types Programming language used Hardware platform selection
10. In any SDLC, when should test analysis and test design ideally start for a test level?
Only after all coding is completed At the end of the project During the corresponding development phase for that test level Only after deployment
11. Which statement BEST explains why Agile projects favor lightweight documentation in testing?
Agile forbids any written documentation Requirements never change in Agile Change is expected, so lighter documentation helps adapt tests Agile eliminates the need for testing
12. In Agile contexts, which test techniques are MOST commonly used for manual testing?
Only white‑box techniques Only non‑functional techniques Experience‑based techniques such as exploratory testing No techniques are required
13. In DevOps, which practice directly supports fast feedback on code quality?
Big‑bang integration Manual deployment only Continuous integration with automated tests Eliminating test environments
14. From a testing perspective, what is a key benefit of continuous delivery (CD) in a DevOps pipeline?
It removes the need for regression testing It automates build, test, and deploy steps for faster releases It restricts testing to production only It replaces static analysis
15. Which of the following is a RISK of adopting DevOps for testing?
No need to define a delivery pipeline Manual testing becomes impossible Test automation must be established and maintained Regression testing is no longer required
16. How does DevOps typically influence non‑functional testing?
It prevents non‑functional testing It improves visibility of performance and reliability characteristics It limits testing to usability only It eliminates security testing
17. Which of the following BEST describes "shift left" in testing?
Testing is moved to the end of the SDLC Only non‑functional tests are executed earlier Testing activities are performed earlier in the SDLC Testing is done only at system level
18. Which example BEST illustrates shift‑left testing?
Executing only production monitoring scripts Reviewing requirements for defects soon after drafting Running acceptance tests after deployment Stress‑testing only in production
19. Which activity MOST clearly applies shift‑left to non‑functional testing?
Only performance testing in production Running performance checks at component level where feasible Skipping performance tests to save time Doing security testing only in system testing
20. Which statement about shift‑left is TRUE?
It means testing late test levels can be skipped It suggests testing earlier but not neglecting later testing It applies only to white‑box testing It is only relevant to Agile projects
21. Why might shift‑left require additional effort early in the SDLC?
Stakeholders must avoid static testing More training and early defect detection activities are needed Test automation is forbidden More production incidents must occur
22. Which of the following is a GOOD testing practice common across SDLCs?
Starting test design only after coding Having test levels with distinct objectives to avoid overlap Using only regression testing at all levels Writing tests only for new features
23. How does the "test‑first" approach mainly support early testing?
Tests are derived only after integration Tests are created before code, guiding development Tests are written only for non‑functional requirements Tests are created only by operations staff
24. In Test‑Driven Development (TDD), which sequence is followed?
Design → Code → Test → Refactor Test → Code → Refactor Code → Test → Design Code → Refactor → Test
25. What is the MAIN idea of Acceptance Test‑Driven Development (ATDD)?
Writing unit tests after coding Using acceptance criteria to derive tests before implementation Performing only non‑functional tests Testing only after deployment
26. What is a key characteristic of Behavior‑Driven Development (BDD)?
Writing tests only in programming languages Using natural‑language scenarios, often Given/When/Then Eliminating acceptance criteria Focusing only on structural coverage
27. How do test‑first approaches (TDD, ATDD, BDD) support regression testing?
They forbid automation Their tests can be kept as automated regression tests They are deleted after initial execution They apply only to manual execution
28. Which statement BEST describes DevOps from an organizational perspective?
It separates development and operations completely It aligns development (including testing) and operations toward common goals It removes operations from the lifecycle It focuses only on release automation
29. Which of the following is a key LIMITATION of static testing for non‑functional characteristics?
It cannot evaluate maintainability It cannot measure runtime performance efficiency It cannot detect security vulnerabilities It cannot assess readability
30. Which statement BEST explains why reviews are considered static testing?
They use dynamic tools They do not involve code execution and examine work products directly They run automated test suites They are performed only in production
31. Which role is MOST suited to mediate conflicts during a review meeting?
Author Moderator Scribe Manager who is not present
32. Which activity is MOST likely to identify gaps in test basis coverage?
System testing Review of test cases against requirements Load testing in production Exploratory testing only
33. Which statement BEST compares formal and informal reviews?
Both ignore objectives Formal reviews use defined processes and roles; informal reviews are flexible with minimal documentation Informal reviews require metrics; formal reviews do not Only informal reviews can find defects
34. How can static testing contribute directly to security?
Only via penetration tests Through static analysis detecting insecure coding patterns By running vulnerability scanners in production only By executing stress tests
35. Which characteristic is MOST strongly associated with a successful inspection?
No preparation time Strict adherence to roles, checklists, and metrics collection Having the author lead and scribe Avoiding exit criteria
36. During a test execution cycle, a tester observes that the system hangs when a certain button is clicked. Later, the root cause is traced to a missing null check in code. In this context, what is the hang?
Anomaly Failure Defect in requirements Static analysis result
37. Your company has been working in a waterfall lifecycle model. They have now decided to implement DevOps and will be using CI/CD. Which of the following is a change that will be required from the testing team?
No change is required. The current approach will still be applicable. There will be additional emphasis on test automation to supply continuous testing. Additional time will be needed to analyze the requirements and design test cases. There will be a need for less technical testers because the developers will handle all the technical testing.
38. Which of the following is an example of shift-right testing?
Static code analysis Usability testing before release A/B testing in production Unit testing
39. What is the main difference between verification and validation?
Verification ensures that the software behaves as expected in real-world scenarios, while validation checks for coding standards Verification involves dynamic testing, while validation is purely documentation-based. Verification checks whether the product is being built correctly, while validation checks whether the right product is being built. There is no difference; both terms refer to executing the code to find defects.
40. Which statement about verification and validation is correct?
Both are only performed during testing phases. Verification confirms the software meets design specifications, Validation confirms the software fitness for use Validation is part of design; verification is part of acceptance testing Verification is always automated, while validation is always manual.