Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

For an assertion failures for the steps I.see or I.dontSee methods assertion error messages are not able to capture as it's not available in test object in hook method _failure(test)

Open
#4,464 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, node.js, playwright
Domain
testing

Research direction

Start by tracing CodeceptJS's hook method _failure(test) for I.see and I.dontSee assertion failures under the Playwright setup. Verify where the assertion message is stored and whether the Allure report receives it; done means the failure message is available to the hook and appears in the report.

Written by the indexing model from the issue text.

Description

stale
What are you trying to achieve?

For an assertion failures for the steps I.see or I.dontSee methods assertion error messages should be able to capture

What do you get instead?

Not able to capture the error message as the same is not available in test object in hook method _failure(test).
Screenshot 2024-08-21 at 11 27 11 AM

Hence not able to capture assertion failure message in Allure report:
Screenshot 2024-08-21 at 11 30 13 AM

Provide console output if related. Use --verbose mode for more details.

# paste output here

Provide test source code if related

// paste test
Details
  • CodeceptJS version: 3.6.4
  • NodeJS Version: 20
  • Operating System: MacOS
  • Playwright
  • Configuration file:
# paste config here
Dominant language
JavaScript
Stars
4.2k
Forks
756
Avg merge
2d 9h
Merged PRs (30d)
16

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from codeceptjs/CodeceptJS

All issues in codeceptjs/CodeceptJS

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.