Skip to content

make integration_tests pass for node releases and master #4062

Closed

Description

@AnnaMag

Do you want to request a feature or report a bug?
bug
What is the current behavior?
Two Jest integration tests do not pass for node official releases and current master:
integration_tests/__tests__/show_config.test.js and
integration_tests/__tests__/stack_trace_no_captureStackTrace.js.

If the current behavior is a bug, please provide the steps to reproduce and either a repl.it demo through https://repl.it/languages/jest or a minimal repository on GitHub that we can yarn install and yarn test.
set PATH to node
yarn (or yarn --ignore-engines for local build) and yarn test from within the Jest dir
What is the expected behavior?
Tests passing
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.
Jest: master e9a6f71
node: master c3cb0ed (same happens for release branches, tested for 6+)
yarn: 0.27.5
macOS Sierra

What fixed the problem for me:

  • update snapshot for show_config.test.js
  • replace
    expect(stderr).toMatch(/\s+at\sJestAssertionError\s.*/);
    with the call
    expect(stderr).toMatch( /\s+at\s(?:.+?)\s\(__tests__\/runtime_error.test\.js/, );
    in stack_trace_no_captureStackTrace.js. RunJest does not
    seem to return at JestAssertionError string, afaiu (might be wrong :)).

Activity

  1. changed the title [-]make integration_tests/__tests__/* pass for node releases/master[/-] [+]make integration_tests pass for node releases and master[/+] on Jul 18, 2017
  2. cpojer commented on Jul 18, 2017

    @cpojer
    Member

    Sorry about that. Those two should be fixed on master now ( 009c065 ). Mind confirming that this works properly?

  3. AnnaMag commented on Jul 18, 2017

    @AnnaMag
    Author

    @cpojer, confirmed 👍

  4. github-actions commented on May 13, 2021

    @github-actions

    This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
    Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

  5. locked as resolved and limited conversation to collaborators on May 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions