Alternatives to TestNG logo

Alternatives to TestNG

JUnit, Cucumber, Selenium, Mockito, and NUnit are the most popular alternatives and competitors to TestNG.
180
137
+ 1
0

What is TestNG and what are its top alternatives?

It is a testing framework designed to simplify a broad range of testing needs, it covers all categories of tests: unit, functional, end-to-end, integration, etc.Run your tests in arbitrarily big thread pools with various policies available (all methods in their own thread, one thread per test class, etc.
TestNG is a tool in the Testing Frameworks category of a tech stack.
TestNG is an open source tool with 1.7K GitHub stars and 907 GitHub forks. Here’s a link to TestNG's open source repository on GitHub

Top Alternatives to TestNG

  • JUnit

    JUnit

    JUnit is a simple framework to write repeatable tests. It is an instance of the xUnit architecture for unit testing frameworks. ...

  • Cucumber

    Cucumber

    Cucumber is a tool that supports Behaviour-Driven Development (BDD) - a software development process that aims to enhance software quality and reduce maintenance costs. ...

  • Selenium

    Selenium

    Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well. ...

  • Mockito

    Mockito

    It is a mocking framework that tastes really good. It lets you write beautiful tests with a clean & simple API. It doesn’t give you hangover because the tests are very readable and they produce clean verification errors. ...

  • NUnit

    NUnit

    An evolving, open source framework designed for writing and running tests in Microsoft .NET programming languages.It is an aspect of test-driven development , which is part of a larger software design paradigm known as Extreme Programming ...

  • Apache Maven

    Apache Maven

    Maven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven, providing a uniform build system. Once you familiarize yourself with how one Maven project builds you automatically know how all Maven projects build saving you immense amounts of time when trying to navigate many projects. ...

  • pytest

    pytest

    A framework makes it easy to write small tests, yet scales to support complex functional testing for applications and libraries. It is a mature full-featured Python testing tool. ...

  • RSpec

    RSpec

    Behaviour Driven Development for Ruby. Making TDD Productive and Fun.

TestNG alternatives & related posts

JUnit logo

JUnit

1.9K
463
0
A programmer-oriented testing framework for Java
1.9K
463
+ 1
0
PROS OF JUNIT
    Be the first to leave a pro
    CONS OF JUNIT
      Be the first to leave a con

      related JUnit posts

      We are looking for a Testing Tool that can integrate with Java/ React/ Go/ Python/ Node.js. Which amongst the three tools JUnit, NUnit & Selenium would be the best for this use case?

      See more
      Joshua Dean Küpper
      CEO at Scrayos UG (haftungsbeschränkt) · | 1 upvote · 142.1K views

      We use JUnit for our Java Unit and Integration tests in Version 5. Combined with @JMockit2 and @truth (from Google) we perform all kinds of tests on our minecraft, standalone and microservice architecture.

      We prefer JUnit over TestNG because of the bigger community, better support and the generally more agile development. JUnit integrates nicely with most software, while TestNG support is a little more limited.

      See more
      Cucumber logo

      Cucumber

      762
      716
      25
      Simple, human collaboration.
      762
      716
      + 1
      25
      PROS OF CUCUMBER
      • 18
        Simple Syntax
      • 3
        Simple usage
      • 2
        Nice report
      • 2
        Huge community
      CONS OF CUCUMBER
        Be the first to leave a con

        related Cucumber posts

        Benjamin Poon
        QA Manager - Engineering at HBC Digital · | 8 upvotes · 751.8K views

        For our digital QA organization to support a complex hybrid monolith/microservice architecture, our team took on the lofty goal of building out a commonized UI test automation framework. One of the primary requisites included a technical minimalist threshold such that an engineer or analyst with fundamental knowledge of JavaScript could automate their tests with greater ease. Just to list a few: - Nightwatchjs - Selenium - Cucumber - GitHub - Go.CD - Docker - ExpressJS - React - PostgreSQL

        With this structure, we're able to combine the automation efforts of each team member into a centralized repository while also providing new relevant metrics to business owners.

        See more
        Sarah Elson
        Product Growth at LambdaTest · | 4 upvotes · 324K views

        @producthunt LambdaTest Selenium JavaScript Java Python PHP Cucumber TeamCity CircleCI With this new release of LambdaTest automation, you can run tests across an Online Selenium Grid of 2000+ browsers and OS combinations to perform cross browser testing. This saves you from the pain of maintaining the infrastructure and also saves you the licensing costs for browsers and operating systems. #testing #Seleniumgrid #Selenium #testautomation #automation #webdriver #producthunt hunted

        See more
        Selenium logo

        Selenium

        11K
        8.5K
        519
        Web Browser Automation
        11K
        8.5K
        + 1
        519
        PROS OF SELENIUM
        • 169
          Automates browsers
        • 154
          Testing
        • 101
          Essential tool for running test automation
        • 24
          Record-Playback
        • 24
          Remote Control
        • 8
          Data crawling
        • 7
          Supports end to end testing
        • 6
          Functional testing
        • 6
          Easy set up
        • 4
          The Most flexible monitoring system
        • 3
          Easy to integrate with build tools
        • 3
          End to End Testing
        • 2
          Integration Tests
        • 2
          Comparing the performance selenium is faster than jasm
        • 2
          Record and playback
        • 2
          Compatible with Python
        • 2
          Easy to scale
        • 0
          Integrated into Selenium-Jupiter framework
        CONS OF SELENIUM
        • 7
          Flaky tests
        • 2
          Slow as needs to make browser (even with no gui)

        related Selenium posts

        Kamil Kowalski
        Lead Architect at Fresha · | 27 upvotes · 1.2M views

        When you think about test automation, it’s crucial to make it everyone’s responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.

        See more
        Benjamin Poon
        QA Manager - Engineering at HBC Digital · | 8 upvotes · 751.8K views

        For our digital QA organization to support a complex hybrid monolith/microservice architecture, our team took on the lofty goal of building out a commonized UI test automation framework. One of the primary requisites included a technical minimalist threshold such that an engineer or analyst with fundamental knowledge of JavaScript could automate their tests with greater ease. Just to list a few: - Nightwatchjs - Selenium - Cucumber - GitHub - Go.CD - Docker - ExpressJS - React - PostgreSQL

        With this structure, we're able to combine the automation efforts of each team member into a centralized repository while also providing new relevant metrics to business owners.

        See more
        Mockito logo

        Mockito

        800
        120
        0
        Tasty mocking framework for unit tests in Java
        800
        120
        + 1
        0
        PROS OF MOCKITO
          Be the first to leave a pro
          CONS OF MOCKITO
            Be the first to leave a con

            related Mockito posts

            NUnit logo

            NUnit

            253
            89
            0
            An open-source unit testing framework
            253
            89
            + 1
            0
            PROS OF NUNIT
              Be the first to leave a pro
              CONS OF NUNIT
                Be the first to leave a con

                related NUnit posts

                We are looking for a Testing Tool that can integrate with Java/ React/ Go/ Python/ Node.js. Which amongst the three tools JUnit, NUnit & Selenium would be the best for this use case?

                See more
                Apache Maven logo

                Apache Maven

                2.2K
                1.4K
                414
                Apache build manager for Java projects.
                2.2K
                1.4K
                + 1
                414
                PROS OF APACHE MAVEN
                • 137
                  Dependency management
                • 71
                  Necessary evil
                • 60
                  I’d rather code my app, not my build
                • 48
                  Publishing packaged artifacts
                • 43
                  Convention over configuration
                • 18
                  Modularisation
                • 11
                  Consistency across builds
                • 6
                  Prevents overengineering using scripting
                • 4
                  Runs Tests
                • 4
                  Lot of cool plugins
                • 3
                  Extensible
                • 2
                  Hard to customize
                • 2
                  Runs on Linux
                • 1
                  Runs on OS X
                • 1
                  Slow incremental build
                • 1
                  Inconsistent buillds
                • 1
                  Undeterminisc
                • 1
                  Good IDE tooling
                CONS OF APACHE MAVEN
                • 6
                  Complex
                • 1
                  Inconsistent buillds
                • 0
                  Not many plugin-alternatives

                related Apache Maven posts

                Tymoteusz Paul
                Devops guy at X20X Development LTD · | 23 upvotes · 4.7M views

                Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

                It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

                I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

                We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

                If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

                The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

                Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

                See more
                Shared insights
                on
                Apache MavenApache MavenGradleGradle
                at

                We use Apache Maven because it is a standard. Gradle is very good alternative, but Gradle doesn't provide any advantage for our project. Gradle is slower (without running daemon), need more resources and a learning curve is quite big. Our project can not use a great flexibility of Gradle. On the other hand, Maven is well-know tool integrated in many IDEs, Dockers and so on.

                See more
                pytest logo

                pytest

                535
                205
                0
                A full-featured Python testing tool to help you write better programs
                535
                205
                + 1
                0
                PROS OF PYTEST
                  Be the first to leave a pro
                  CONS OF PYTEST
                    Be the first to leave a con

                    related pytest posts

                    RSpec logo

                    RSpec

                    639
                    163
                    0
                    Behaviour Driven Development for Ruby
                    639
                    163
                    + 1
                    0
                    PROS OF RSPEC
                      Be the first to leave a pro
                      CONS OF RSPEC
                        Be the first to leave a con

                        related RSpec posts

                        I'm working as one of the engineering leads in RunaHR. As our platform is a Saas, we thought It'd be good to have an API (We chose Ruby and Rails for this) and a SPA (built with React and Redux ) connected. We started the SPA with Create React App since It's pretty easy to start.

                        We use Jest as the testing framework and react-testing-library to test React components. In Rails we make tests using RSpec.

                        Our main database is PostgreSQL, but we also use MongoDB to store some type of data. We started to use Redis  for cache and other time sensitive operations.

                        We have a couple of extra projects: One is an Employee app built with React Native and the other is an internal back office dashboard built with Next.js for the client and Python in the backend side.

                        Since we have different frontend apps we have found useful to have Bit to document visual components and utils in JavaScript.

                        See more
                        Simon Bettison
                        Managing Director at Bettison.org Limited · | 7 upvotes · 293.6K views

                        In 2010 we made the very difficult decision to entirely re-engineer our existing monolithic LAMP application from the ground up in order to address some growing concerns about it's long term viability as a platform.

                        Full application re-write is almost always never the answer, because of the risks involved. However the situation warranted drastic action as it was clear that the existing product was going to face severe scaling issues. We felt it better address these sooner rather than later and also take the opportunity to improve the international architecture and also to refactor the database in. order that it better matched the changes in core functionality.

                        PostgreSQL was chosen for its reputation as being solid ACID compliant database backend, it was available as an offering AWS RDS service which reduced the management overhead of us having to configure it ourselves. In order to reduce read load on the primary database we implemented an Elasticsearch layer for fast and scalable search operations. Synchronisation of these indexes was to be achieved through the use of Sidekiq's Redis based background workers on Amazon ElastiCache. Again the AWS solution here looked to be an easy way to keep our involvement in managing this part of the platform at a minimum. Allowing us to focus on our core business.

                        Rails ls was chosen for its ability to quickly get core functionality up and running, its MVC architecture and also its focus on Test Driven Development using RSpec and Selenium with Travis CI providing continual integration. We also liked Ruby for its terse, clean and elegant syntax. Though YMMV on that one!

                        Unicorn was chosen for its continual deployment and reputation as a reliable application server, nginx for its reputation as a fast and stable reverse-proxy. We also took advantage of the Amazon CloudFront CDN here to further improve performance by caching static assets globally.

                        We tried to strike a balance between having control over management and configuration of our core application with the convenience of being able to leverage AWS hosted services for ancillary functions (Amazon SES , Amazon SQS Amazon Route 53 all hosted securely inside Amazon VPC of course!).

                        Whilst there is some compromise here with potential vendor lock in, the tasks being performed by these ancillary services are no particularly specialised which should mitigate this risk. Furthermore we have already containerised the stack in our development using Docker environment, and looking to how best to bring this into production - potentially using Amazon EC2 Container Service

                        See more