Software Testing and QA Fundamentals

QA must log off during software deployments because their active testing sessions can delay the deployment process (impacting upgrade timelines) and they risk testing outdated code once the deployment completes. Option B captures both critical reasons: time impact and version correctness.

Deciding when to stop testing depends on the specific risks, budget, and quality standards of the system under test. Running all planned tests or fixing all faults is often unrealistic or insufficient, and running out of time is a constraint rather than a logical stopping criterion.

Beta testing is performed by real customers at their own site after alpha testing is complete. This helps identify issues in real-world environments that might not appear in controlled testing conditions. Option A correctly defines beta testing as testing performed by customers at their own site, distinguishing it from alpha testing (at developer's site) and other testing types.

Acceptance testing evaluates whether the system meets business requirements and is ready for deployment. It's conducted from a business perspective rather than a purely technical fault-finding perspective. Option C is correct because acceptance testing focuses on business needs, while option A describes technical testing and option B is too broad.