Feature Request about test item id

[hknerts]

TestNG Version

7.0.0

Expected behavior

an "id" variables can be added to Test annotation class as default

Actual behavior

There is no "id" variables in Test Annotation class.

• It must be default variable because it could be easy to track the jira item id and test item id.
• Custom plugins can be develop for auto transform the test execution suite between custom tools (Jira) and our test repository.

Is the issue reproductible on runner?

• [x] Gradle
• [x] Maven
• [ ] Shell
• [ ] Ant
• [ ] Eclipse
• [ ] IntelliJ
• [ ] NetBeans

Test case sample

Please, share the test case (as small as possible) which shows the issue

[krmahadevan]

@hknerts - Can you please help elaborate as to why do you think that this changeset should be within TestNG?

You can very well build this as a custom annotation that can be used by an individual project to track this information no ?

[krmahadevan]

ping @juherr - Thoughts ?

[hknerts]

@krmahadevan @juherr We are considering developing plugins for integration with test management tools (like Xray-Jira). we will have to match the test ids and the platform ids.

if we do this with custom annotation classes, we will have to tell users to develop this constant class. this will adversely affect the integration process.

if this variable is in testng, we'll just ask users to assign this test id variable value, in easy way.

[hknerts]

@krmahadevan @juherr After that, i want to implement a common listener class to TestNG. It is about reporting test result to Jira-Xray and other management tools. I think ,it will very useful for huge projects and orgs

[juherr]

Like @krmahadevan, I think a custom annotation is a better solution and you can provide an external jar with the annotation for your customers. Another option is using the description attribute and uses it as an id attribute.

[krmahadevan]

@hknerts - Just to elaborate.

You can create a new project that contains the following two components:

1. A custom annotation that can be used on top of @Test annotated test methods, which captures the TCMS (Test case management system) specific data such as ID, project etc.,
2. A TestNG listener that implements say IInvokedMethodListener wherein in its afterInvocation you basically retrieve the custom annotation and using its values, you interact with the TCMS system.

For this you dont need the changes to reside in TestNG. They can very well reside outside of TestNG as 1 project which your users would add up as a dependency and work with it.

[hknerts]

ok, thanks for your response.