7

I'm using Spring Test with TestNG to test our DAOs, and I wanted to run a specific text fixture script before certain methods, allowing the modifications to be rolled back after every method so that the tests are free to do anything with the fixture data.

Initially I thought that 'groups' would be fit for it, but I already realized they're not intended for that (see this question: TestNG BeforeMethod with groups ).

Is there any way to configure a @BeforeMethod method to run only before specific @Tests? The only ways I see are workarounds:

  • Define an ordinary setup method and call at the beginning of every @Test method;
  • Move the @BeforeMethod method to a new class (top level or inner class), along with all methods that depend on it.

Neither is ideal, I'd like to keep my tests naturally grouped and clean, not split due to lack of alternatives.

Community
  • 1
  • 1
user2479523
  • 103
  • 1
  • 1
  • 5
  • Why didn't the solution mentioned in the thread work for you? If you run by groups, doesn't it help? – niharika_neo Dec 18 '13 at 02:26
  • 2
    groups should be working fine here. You give the BeforeTest, Test and AfterTest the same group. I know the post is old, but just for the record. It is also possible to give each method different groups. – patrik Dec 05 '17 at 07:32

2 Answers2

12

You could add a parameter your @BeforeMethod with the type 'java.lang.reflect.Method'. TestNG will then inject the reflection information for the current test method including the method name, which you could use for switching.

If you add another 'Object' parameter, you will also get the invocation parameters of the test method.

You'all find all on possible parameters for TestNG-annotated methods in chapter 5.18.1 of the TestNG documentation.

jabbrwcky
  • 598
  • 5
  • 6
3

Tests are simply not designed to do this. Technically speaking, a single tests is supposed to handle being idempotent for itself meaning it sets up, tests, and takes down. That is a single test. However, a lot of tests sometimes have the same set-up and take down method, whereas other tests need one set-up before they all run. This is the purpose of the @Before type tags. If you don't like set-up and tear-down inside your test, your more then welcome to architect your own system, but technically speaking, if certain methods require specific set-ups or tear-downs, then that really should be embodied IN the test, since it is a requirement for test to pass. It is ok to call a set-up method, but ultimately, it should be OBVIOUS that a test needs a specific set-up in order to pass. After all, if your using specific set-ups, aren’t you actually testing states rather than code?

Nick Humrich
  • 14,905
  • 8
  • 62
  • 85