ZooKeeper
  1. ZooKeeper
  2. ZOOKEEPER-394

Converting JUnit tests into TestNG controlled environment

    Details

    • Type: Test Test
    • Status: Closed
    • Priority: Major Major
    • Resolution: Invalid
    • Affects Version/s: 3.1.1
    • Fix Version/s: 3.3.0
    • Component/s: tests
    • Labels:
      None

      Description

      TestNG is a powerful test harness, which provides a lot of useful features like parallel test execution, test parametrization, and such.
      ZooKeeper uses JUnit (v.4.4) environment instead which certainly should help to ease the conversion

      I'd suggest to convert ZooKeeper's Junit based test infrastructure into TestNG controller environment, which will allow to achieve higher level of test execution control in the long run.

      The same conversion has been already performed for Avro project (see https://issues.apache.org/jira/browse/AVRO-26)

        Activity

        Konstantin Boudnik created issue -
        Patrick Hunt made changes -
        Field Original Value New Value
        Assignee Konstantin Boudnik [ cos ]
        Hide
        Konstantin Boudnik added a comment -

        Here's few advantages of TestNG over JUnit:

        • tests parametrization
        • parallel execution of tests
        • dynamic tests grouping and lists combinations
        • TestCase inheritance isn't needed, e.g. more flexibility for tests developers
        • elaborate listeners APIs
        • data providers API is available for even more complex data and parameters preparation for test cases
        Show
        Konstantin Boudnik added a comment - Here's few advantages of TestNG over JUnit: tests parametrization parallel execution of tests dynamic tests grouping and lists combinations TestCase inheritance isn't needed, e.g. more flexibility for tests developers elaborate listeners APIs data providers API is available for even more complex data and parameters preparation for test cases
        Hide
        Patrick Hunt added a comment -

        not a blocker for 3.2, moving to 3.3

        Show
        Patrick Hunt added a comment - not a blocker for 3.2, moving to 3.3
        Patrick Hunt made changes -
        Fix Version/s 3.3.0 [ 12313976 ]
        Fix Version/s 3.2.0 [ 12313491 ]
        Hide
        Patrick Hunt added a comment -

        we will be staying with junit for the forseeable future. seems that not having "fork always" type functionality (which junit ant task has) was a blocker for hadoop at large (core/mr/hdfs/etc...)

        Show
        Patrick Hunt added a comment - we will be staying with junit for the forseeable future. seems that not having "fork always" type functionality (which junit ant task has) was a blocker for hadoop at large (core/mr/hdfs/etc...)
        Patrick Hunt made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Invalid [ 6 ]
        Patrick Hunt made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        130d 23h 57m 1 Patrick Hunt 16/Sep/09 19:30
        Resolved Resolved Closed Closed
        190d 22h 54m 1 Patrick Hunt 26/Mar/10 17:24

          People

          • Assignee:
            Konstantin Boudnik
            Reporter:
            Konstantin Boudnik
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development