Issue with custom TestNG annotations processing in reporting module
Reported by Michael Weber | May 7th, 2026 @ 05:26 AM
While testing the integration between our current framework and the reporting dashboard, we noticed some inconsistencies in how suite-level hooks are being captured.
Specifically, we need to ensure that the lifecycle defined by testng annotations is fully mapped to the test management side. Without proper support for @BeforeGroups and @AfterGroups, the report lacks historical data for specific execution clusters.
Could you please check if the current parser follows the hierarchy described in this guide? Using the standard testomat.io logic for these annotations would solve our synchronization issues.
No comments found
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
new seo
Michael Weber