Skip to content

Stack traces for timed out lifecycle hooks point to the test runner #100

@Derpius

Description

@Derpius

Context

  • If a lifecycle hook (e.g. beforeEach) times out, the traceback will point to the runHooks function in the test runner, not the line that timed out (or even the beforeEach etc. that timed out)
  • This may also occur from timeouts in tests, this should be checked and fixed as part of this ticket if it does
    • We additionally need to make sure that this doesn’t error the entire runtime, and instead just marks the test as failed
  • This is most likely an issue with our timed function util

Scope

todo: scope this

Acceptance criteria

  • Timeout errors thrown from lifecycle hooks point to the line that timed out, or if that is not possible, then the line where the lifecycle hook was registered (i.e. beforeEach(function())

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingjira ticketThis issue was created from a Jira ticket during the migration to GitHub issuesscope - test runner

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions