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

targetCreatedHandler triggers UnhandledPromiseRejectionWarning

Open
#3,037 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Run the CI tests with minimal console output using the shown Playwright configuration, then inspect targetCreatedHandler and the Playwright.js stack location around line 2643. Done means the tests still pass without the UnhandledPromiseRejectionWarning.

Written by the indexing model from the issue text.

Description

bug playwright
What are you trying to achieve?

Running tests on the CI with minimum text output to the console

What do you get instead?

Though the tests pass the UnhandledPromiseRejectionWarning message creates redundant text output.

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

(node:21420) UnhandledPromiseRejectionWarning: frame.frameElement: Frame has been detached.
    at C:\Users\...\..\...\node_modules\codeceptjs\lib\helper\Playwright.js:2643:46
(node:21420) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)

photo_2021-09-11_14-31-21

Provide test source code if related

// paste test
Details
  • CodeceptJS version: 3.1.2
  • NodeJS Version: 14.17.5
  • Operating System: Windows and Linux
  • puppeteer || webdriverio || protractor || testcafe version (if related)
  • Configuration file:
//unrelated data omitted with "..."
exports.config = {
  tests: './test/steps/*_test.js',
  "translation": "ru-RU",
  output: './output',
  helpers: {
    Playwright: {
      url: 'someurl',
      show: false,
      browser: 'chromium'
    },
    GraphQL: {
      endpoint: '...',
    },
    ChaiWrapper : {
      "require": "codeceptjs-chai"
    },
    CustomPlaywrightHelper: {
      require: '.../customPlaywright_helper.js',
    },
    DateHelper: {
      require: '.../date_helper.js',
    },
    REST: {
    }
  },
  include: {
    I: './test/steps_file.js',
    pages: '...',
  },
  bootstrap: null,
  mocha: {
    "reporterOptions": {
      "reportDir": "output"
    }
  },
  name: 'foo',
  plugins: {
    pauseOnFail: {},
    retryFailedStep: {
      enabled: true
    },
    tryTo: {
      enabled: true
    },
    screenshotOnFail: {
      enabled: true
    },
    "allure": {
      "enabled": true
    }
  }
}
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.