Skip to content

Conversation

@bambamboole
Copy link
Contributor

Hey, thanks for merging the other PRs. We are now able to use the qase reporter in our project.
While setitng it up, I came across a few things we would like to configure.
I made here a POC on what we are doing. Would be cool to get your opinion on this.

  • Make QaseReporter private methods protected. It is way easier to extend and change behaviour by being able to call existing methods.
  • Reset $this->currentKey after test was completed. This supports other methods checking of currentKey is actually set.
  • Add new PhpUnitConfig class with factory to create from phpunit.xml parameters.
  • config value which enables to only report tests which actually have a test suite. For us its important to not get these arbitary test suite names in qase.io we only want to sync the one which are also marked in phpunit.
  • Add config value to change how a missing test case title is made.

@bambamboole bambamboole marked this pull request as draft August 16, 2025 23:52
@bambamboole
Copy link
Contributor Author

Converted it to draft. so that we can first get the config injected in the php-commons package. then we can leverage this here

@stale
Copy link

stale bot commented Nov 15, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Nov 15, 2025
@stale stale bot closed this Nov 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wontfix This will not be worked on

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant