PCET™ – Certified Entry-Level Tester with Python Free Sample Questions

Software testing is the process of proving the absolute absence of all defects in the source code.

Software testing is the process of verifying that software meets its intended requirements and detecting defects.

Software testing is the automated process of fixing syntax errors and resolving deployment pipeline issues.

Software testing is the phase where the architectural framework and database schemas are designed.

The defect clustering principle, which states that bugs are always distributed evenly across all modules.

The pesticide paradox, which proves that writing new tests will inevitably introduce new bugs.

The absence-of-defects fallacy, which states that testing can show the presence of defects, but cannot prove their absolute absence.

The Shift-Right testing methodology, which delays defect discovery until user acceptance testing.

Defect -> Error -> Failure

Failure -> Error -> Defect

Bug -> Failure -> Error

Error -> Defect -> Failure

A user clicks the 'Submit' button on a form and the application crashes with a 500 Internal Server Error.

A programmer accidentally types '==' instead of '=' when assigning a variable in the authentication module.

A product owner forgets to include a critical business rule regarding discounts in the acceptance criteria.

A static analysis linter reveals that a newly written function is missing a required docstring.

Defects are caught earlier in the process, significantly reducing the cost and effort required to fix them.

Testing is delayed until the end of the SDLC to ensure all features are fully developed before validation begins.

Testers collaborate closely with developers and designers during the requirements and design phases to prevent defects.

Automated end-to-end tests completely replace the need for unit tests, speeding up the release cycle.

The responsibility of finding functional bugs is shifted entirely to the end-users in the production environment.

Agile testing only involves system testing, while Waterfall includes unit, integration, and acceptance testing.

Agile emphasizes continuous testing throughout development sprints, whereas Waterfall typically isolates testing to a specific late stage.

Agile relies exclusively on manual exploratory testing, while Waterfall requires full test automation.

Agile eliminates the need for test planning and documentation, whereas Waterfall requires rigid test plans.