Skip to content

TestNG support #132

Description

@bsideup

Sub-task of #87

Activity

  1. modified the milestone: 2.0 on Jan 14, 2017
  2. laurikimmel commented on Apr 8, 2018

    @laurikimmel

    The second birthday is almost there!
    Any news on this one?

  3. bsideup commented on Apr 9, 2018

    @bsideup
    MemberAuthor

    @laurikimmel actually yes :)
    We're working on the unified, framework-agnostic API as part of JUnit 5:
    #636

    The reason why TestNG didn't receive enough attention is because you can already use TC with TestNG by calling .start()/.stop(). And since there is no such thing as rule in TestNG, there is not much we can do

  4. stale commented on Oct 28, 2018

    @stale

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.

  5. olyv commented on Feb 17, 2020

    @olyv

    @kiview did you by any chance try to run tests in parallel using TestNG?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions