![]() The projects are complied with our Framework after all tests are passed, so even biniary Non Backward compatible changes could be extremely hard to solve. In the project I'm working in we are never allowed to introduce an Non Backward Compatible change, since different projects fetched our project automatically, and if the test don't pass it will not be uplifted to any other project and get verdict -1. We using groups in plenty places without specify them in a suite, and for regular unit tests we don't even have suites but still uses groups. this makes it extremely hard to do an uplift now. I'm surprised that a very nice feature is treated as a bug and removed. For what I know and understand, Annotations are meant to run in the class and no need for suits to be have been working hard for long time to get correction on master and PR merged and then I suddenly met this issue and adapt to other Non backward compatible changes. I totally agree It was a very useful feature and it's removed without introducing any useful alternatives. I don't think this was a bug correction, I think that removing a very useful feature from TestNg that simplifies test cases allot. As I understand now we must specify the groups in the suite, but that will not work for us. In many Test Cases we using groups to run different Before/After methods/class and we have test within the same test class with different groups and without groups. It will never be possible to adapt all of the Test and as I see it is not even a possible alternative to this change. We have over 500 Projects and thousands of test cases in different organizations and thousands developers. I think we also have phased this issue now when we Testing TestNg 7.5, we are using 6.14 at the moment and are working on uplifting to latest TestNg, but it seems not possible due to this change. Please find below two screenshots from both TestNG version from the surefire plugin execution (Both and from the same sample provided in the previous comment) ![]() It will however work as you said if I'm not using those annotations and only specifying the groups names for the test cases only Here I need to specify what groups to run via the xml file. ![]() If I uderstand this right, using the & annotations should be working when I run the test class from the IDE or with surefire plugin with the same behavior. In that case, the group mode won't be even mean the behavior is the same when I run from the IDE and the test class directly and when I run from the surefire plugin. Does this mean that you are using mvn clean test -Dtest= TestGroupsAnnotations ? If yes, then this wont work like that because you aren't specifying what groups to be run. ("Test After Groups Annotation - Looks like this is a problem with the TestNG eclipse plugin. ("Test Before Groups Annotation = "testGroup2") ![]() Public class TestGroupsAnnotations = "testGroup1")
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |