New TestNG-Annotations project

[cpjust]

Hi all,
I'd like to invite everyone to check out my testng-annotations project.
You can import the dependency from Maven Central: https://central.sonatype.com/artifact/io.github.cpjust/testng-annotations/overview

It currently has annotations for:

• IncludeOnEnv and ExcludeOnEnv to allow different tests to be included or excluded on different environments.

As well as the following JUnit-like annotations:

• EmptySource
• NullSource
• NullAndEmptySource
• ValueSource

Coming soon:

• CsvSource
• EnumSource

Other annotations I'm considering adding are:

• DisableBetweenDates - Set dates when a test shouldn't run.
• DisableBetweenTimes - Set times of the day when a test shouldn't run.
• IgnoreUntil - Ignores a test until a certain date.
• ReRunOnRetry - Specify methods to re-run on retry (like a BeforeClass)...
• TestMutex - Specify test classes or groups that shouldn't run in parallel.
• TestClassOrder - Like test priority, but for classes.
• TestMetaData (similar to @CustomAttribute) - Add extra meta-data to tests, to make available to tests.
• ParallelMethod - Run test methods in parallel (if you have the default set to run classes in parallel for other tests).
• TestGroup - Add groups at class-level (mostly to fix a bug I found when adding @Test(groups = ...) at class and method level).

If anyone has any preferences about which new annotations they'd like to see first, let me know.

Also, I could use more people that are willing to do code reviews, since that's the biggest bottleneck I'm running into now. So if you have time to do reviews, let me know.

And for the TestNG maintainers, feel free to add any of my annotations directly into the main TestNG project (or maybe as a separate add-on dependency).

[juherr]

Thanks for your message.

Regarding the following point:

And for the TestNG maintainers, feel free to add any of my annotations directly into the main TestNG project (or maybe as a separate add-on dependency).

At this stage, we are not planning to add new features directly into TestNG itself. One of the main challenges is the limited availability of contributors with enough time to maintain core and additional functionality over the long term.

On the contrary, our current direction is to move features into dedicated modules whenever possible, leveraging the existing code model rather than increasing the scope of the core project.

Your approach with an external project aligns well with this strategy. We therefore recommend keeping it as a separate extension and adding it to the list of third-party extensions here:
https://github.com/testng-team/testng/wiki/3rd-party-extensions