Testing & Debugging Flashcards
7 cards from real CAD practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Testing & Debugging flashcards as text
What is user acceptance testing (UAT)?
Answer: Testing performed by end users to validate the system meets their requirements
UAT is conducted by end users or clients to confirm the system meets their defined requirements before formal acceptance and release.
What does a NullPointerException (or null reference error) typically indicate when debugging?
Answer: Code is attempting to use a reference variable that has not been initialized
A NullPointerException occurs when code dereferences a variable that points to null rather than a valid object instance.
Which testing approach evaluates how a system behaves when pushed beyond its normal operational capacity?
Answer: Stress testing
Stress testing deliberately pushes a system beyond its designed load limits to observe failure behavior and identify breaking points.
What is the primary purpose of static code analysis?
Answer: Examining source code without executing it to identify potential bugs and violations
Static code analysis inspects source code without running it, identifying potential bugs, security vulnerabilities, and style violations automatically.
What is a 'smoke test' in the software development lifecycle?
Answer: A quick preliminary test to verify basic functionality before deeper testing begins
A smoke test is a shallow, rapid check of critical functionality to confirm a build is stable enough for more thorough testing.
What does 'test isolation' mean in unit testing best practices?
Answer: Ensuring each test runs independently without depending on the outcome of other tests
Test isolation ensures each unit test is self-contained and produces the same result regardless of the order tests are run or what other tests have executed.
Which category of software defect is typically the most difficult to reproduce and debug?
Answer: Heisenbugs such as race conditions that change behavior when observed
Heisenbugs, such as race conditions or timing-dependent bugs, are notoriously hard to debug because their behavior changes or disappears when instrumentation is added to observe them.