.expect assertions do not terminate or throw an error for individual cases where the assertion fails.

[anupamtomar]

I've encountered an issue with .expect assertions in my test cases. If a test case has three different .expect assertions and the first assertion fails, the test case does not fail and terminate at the point of the failed assertion. Instead, the test case passes through all the next steps or .expect assertions without actually executing them.

Additionally, I have implemented an afterEach hook as follows:

afterEach: async function (browser) {
    await browser.end();
}

The issue arises when a test case fails at an assertion. In such cases, the afterEach hook does not execute the browser.end() command, and the browser session is not closed. Consequently, the same browser session is used for the next test case. However, if the test case passes successfully, the afterEach hook functions correctly, closing the browser and opening a new browser session for the next test case within the same file.

Despite these issues, after all test cases in the same file are completed, the console correctly displays the errors indicating where the issues occurred.

Steps to Reproduce:

1. Create a test case with multiple .expect assertions.
2. Ensure that the first or any middle assertion fails.
3. Implement an afterEach hook to close the browser session.
4. Observe that the test case does not terminate at the failed assertion and passes through all subsequent steps or assertions without executing them.
5. Note that the afterEach hook is passed through without executing the browser.end() command if the test case fails.
6. Confirm that the next test case runs in the same browser session if the previous one fails.
7. Verify that errors are displayed in the console after all test cases are completed.

Expected Behavior:

1. The test case should terminate and fail immediately upon encountering a failed .expect assertion.
2. The afterEach hook should execute the browser.end() command and close the browser session regardless of whether the test case passes or fails.
3. Each test case should start with a new browser session, ensuring isolation between test cases.

Actual Behavior:

1. The test case passes through all the next steps or assertions without actually executing them when an assertion fails.
2. The afterEach hook is passed through without executing the browser.end() command if a test case fails.
3. The next test case runs in the same browser session if the previous one fails.
4. Errors are displayed in the console only after all test cases are completed.

Environment
Nightwatch.js version: v3.6.3
Node.js version: v19.9.0

Note: I have checked and got to know that in such conditions, the .assert method works fine. However, I prefer and would like to use .expect over .assert.

This behaviour impacts the reliability of test results and the isolation of test cases. It would be helpful if the .expect assertions could terminate the test case immediately upon failure and ensure that the afterEach hook is executed correctly regardless of the test case outcome.