You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error Handling in Fixtures...
Check if there is proper error handling within your fixture code. If an exception occurs within a fixture, it might prevent subsequent code, including screenshot from being executed. Ensure that exceptions are caught, logged, or handled appropriately.
Screenshot Triggering Mechanism...
Verify the logic that triggers automatic screenshot capture. Ensure that it is appropriately placed and invoked in case of errors within fixtures. It could be part of a global error-handling mechanism or specific to fixture failures
Version
1.41.2
Steps to reproduce
npm install
npm run test
Expected behavior
As test failed, I expect automatic screenshot to appear in the report.
Actual behavior
There is no screenshot in the report:
Additional context
If error is thrown before call of
use()
, screenshot correctly appears in the report:Report:
Environment
The text was updated successfully, but these errors were encountered: