GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Unalbe to upload failure stacktraces from the phpunit framework · Issue #105 · allure-framework/allure-phpunit

Unalbe to upload failure stacktraces from the phpunit framework #105

New issue
Copy link
New issue
Copy link
Open
Open
Unalbe to upload failure stacktraces from the phpunit framework#105
Copy link
Labels
type:bug

Description

@cheshi-mantu
cheshi-mantu
opened on Aug 15, 2024
Issue body actions

Describe the bug
Unalbe to upload failure stacktraces from the phpunit framework

We have PHPUnit integration setup according to the instructions, however stack traces are missing from the report. According to the code of the allure library, it only includes a message, without a stack trace.

To Reproduce
fail a test

Expected behavior
A clear and concise description of what you expected to happen.

when a test failed, then the stacktrace is included into the test result.

Screenshots

NA

Desktop (please complete the following information):
NA

Smartphone (please complete the following information):

NA

Additional context
Add any other context about the problem here.

Reacted by dima-makarenko and rlqd

Activity

  1. cheshi-mantu
    added
    type:bug
    on Aug 15, 2024
  2. rlqd commented on Jan 7, 2025

    @rlqd
    rlqd
    on Jan 7, 2025
    More actions

    I figured it out.
    ExceptionDetailsTrait is supposed to be used for that. However, it's broken because onNotSuccessfulTest is called at the very end of a test run after the testErrored event has been emitted.
    So setLastException is happening after the test status was recorded and as a result, the details are missing in the report.

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

    type:bug

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.