fix: set exit code when tests fail

The mocha.run() callback receives a 'failures' count parameter that indicates how many tests failed, but this was not being used to set process.exitCode. This caused the process to exit with code 0 even when tests failed, making CI pipelines incorrectly report success.

Changes:
- Accept failures parameter in mocha.run() callback
- Pass failures to done() function
- Set process.exitCode = 1 when failures > 0
- Ensures CI pipelines correctly fail when tests fail

Author: kobenguyent

lib/codecept.js

@@ -269,17 +269,21 @@ class Codecept {
         })
       }
 
-      const done = async () => {
+      const done = async (failures) => {
         event.emit(event.all.result, container.result())
         event.emit(event.all.after, this)
         // Wait for any recorder tasks added by event.all.after handlers
         await recorder.promise()
+        // Set exit code based on test failures
+        if (failures) {
+          process.exitCode = 1
+        }
         resolve()
       }
 
       try {
         event.emit(event.all.before, this)
-        mocha.run(async () => await done())
+        mocha.run(async (failures) => await done(failures))
       } catch (e) {
         output.error(e.stack)
         reject(e)