BrowserStack's non-SDK reporting guide distinguishes session execution from explicit test outcome reporting. A BrowserStack integration should mark assertions passed or failed through the appropriate supported path.
Include an intentionally failing test. An apparently completed session must not make the pipeline look successful when its expected behavior failed.