Protractor test run does not abort after first failure when failFast is enabled with directConnect
When using Protractor’s failFast option to halt execution after the first spec failure, teams expect the runner to stop immediately and skip remaining specs. However, the interaction between failFast (set via configuration or the --failFast CLI flag) and the directConnect mode is not fully documented for recent releases, leaving uncertainty about whether the