What distinguishes a hard assert from a soft assert in testing?

• A. Hard assert allows the test to continue after failure
• B. Soft assert immediately stops the execution of the test
• C. Hard assert fails and moves to the next test immediately
• D. Soft assert collects errors during a single test

Answer: (C)

A hard assert is characterized by its immediate failure behavior—once a hard assert is executed and the condition it checks does not hold true, the test fails immediately, ceasing any further execution within that test case. This means the script will typically not proceed to any subsequent lines of code, including subsequent tests.

In contrast, a soft assert allows the test to continue running even after encountering a failure. This means that while a soft assert captures failure conditions, it does so without stopping the flow of the test case. As a result, soft asserts can report multiple failures at the end of the test execution.

Thus, the main distinguishing feature of hard asserts is that they cause an immediate stop to the execution of that test upon a failure and do not move to the next test unless they are resolved or the entire testing suite is rerun. This behavior is crucial when a definitive outcome is needed, and further testing would be moot if a critical assert fails.