Issues

Issues

• Remove abandoned doctrine/annotations dependency in next major release

  allure-framework/allure-phpunit#121 · opened on Dec 8, 2025

• Ability to write report only on explicit demand

  allure-framework/allure-phpunit#111 · opened on Nov 27, 2024
  1

• Allure PHPUnit extension is not recognising the parameter path if the phpunit.xml.dist is placed in a different directory than root.

  allure-framework/allure-phpunit#106 · opened on Oct 8, 2024

• Unalbe to upload failure stacktraces from the phpunit framework

  allure-framework/allure-phpunit#105 · opened on Aug 15, 2024
  1

• If a test has markTestSkipped() method in setUp() method, it's not appearing in allure report

  allure-framework/allure-phpunit#104 · opened on May 15, 2024
  3

• Add support for selective test run with a test plan

  allure-framework/allure-phpunit#100 · opened on Feb 12, 2024

• If a test has dataProvider, the report doesn't have the name of the test.

  allure-framework/allure-phpunit#88 · opened on Jan 9, 2023
  1

• After updating the allure-framework / allure-phpunit:^2.0, No option is available for whether to delete previous results on rerun

  allure-framework/allure-phpunit#78 · opened on Sep 14, 2022
  2

• [v2] Use external config instead of arguments in phpunit.xml

  allure-framework/allure-phpunit#66 · opened on Nov 17, 2021
  5

• [v2] Test errors are displayed as failed tests

  allure-framework/allure-phpunit#62 · opened on Oct 12, 2021
  1

• Include @group annotations in the report

  allure-framework/allure-phpunit#46 · opened on Dec 19, 2019