Alternatives to Arquillian logo

Alternatives to Arquillian

Selenium, JUnit, Mockito, Cucumber, and TestNG are the most popular alternatives and competitors to Arquillian.
28
42
+ 1
0

What is Arquillian and what are its top alternatives?

It is an integration and functional testing platform that can be used for Java middleware testing. With the main goal of making integration (and functional) tests as simple to write as unit tests, it brings the tests to the runtime environment, freeing developers from managing the runtime from within the test.
Arquillian is a tool in the Testing Frameworks category of a tech stack.
Arquillian is an open source tool with GitHub stars and GitHub forks. Here’s a link to Arquillian's open source repository on GitHub

Top Alternatives to Arquillian

  • 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. ...

  • JUnit
    JUnit

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

  • 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. ...

  • 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. ...

  • TestNG
    TestNG

    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. ...

  • Testcontainers
    Testcontainers

    It is a Java library that supports JUnit tests, providing lightweight, throwaway instances of common databases, Selenium web browsers, or anything else that can run in a Docker container. ...

  • RSpec
    RSpec

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

  • 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. ...

Arquillian alternatives & related posts

Selenium logo

Selenium

12.3K
9.6K
518
Web Browser Automation
12.3K
9.6K
+ 1
518
PROS OF SELENIUM
  • 170
    Automates browsers
  • 153
    Testing
  • 101
    Essential tool for running test automation
  • 24
    Record-Playback
  • 23
    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
  • 8
    Flaky tests
  • 3
    Slow as needs to make browser (even with no gui)

related Selenium posts

Kamil Kowalski
Lead Architect at Fresha · | 28 upvotes · 1.4M 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 · 834.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
JUnit logo

JUnit

2.7K
498
0
A programmer-oriented testing framework for Java
2.7K
498
+ 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 · 165.7K 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
      Mockito logo

      Mockito

      1.2K
      143
      0
      Tasty mocking framework for unit tests in Java
      1.2K
      143
      + 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

          Cucumber logo

          Cucumber

          894
          785
          33
          Simple, human collaboration.
          894
          785
          + 1
          33
          PROS OF CUCUMBER
          • 20
            Simple Syntax
          • 6
            Simple usage
          • 4
            Huge community
          • 3
            Nice report
          CONS OF CUCUMBER
            Be the first to leave a con

            related Cucumber posts

            Benjamin Poon
            QA Manager - Engineering at HBC Digital · | 8 upvotes · 834.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 · 366K 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
            TestNG logo

            TestNG

            416
            152
            0
            A testing framework inspired from JUnit and NUnit
            416
            152
            + 1
            0
            PROS OF TESTNG
              Be the first to leave a pro
              CONS OF TESTNG
                Be the first to leave a con

                related TestNG posts

                Joshua Dean Küpper
                CEO at Scrayos UG (haftungsbeschränkt) · | 1 upvote · 165.7K 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
                Testcontainers logo

                Testcontainers

                54
                47
                0
                A library that integrates Docker with testing libs - for databases, Selenium web browsers, or anything else that...
                54
                47
                + 1
                0
                PROS OF TESTCONTAINERS
                  Be the first to leave a pro
                  CONS OF TESTCONTAINERS
                    Be the first to leave a con

                    related Testcontainers posts

                    Joshua Dean Küpper
                    CEO at Scrayos UG (haftungsbeschränkt) · | 12 upvotes · 33.1K views

                    We've already been monitoring Agones for a few years now, but we only adapted Kubernetes in mid 2021, so we could never use it until then. Transitioning to Kubernetes has overall been a blast. There's definitely a steep learning curve associated with it, but for us, it was certainly worth it. And Agones plays definitely a part in it.

                    We previously scheduled our game servers with Docker Compose and Docker Swarm, but that always felt a little brittle and like a really "manual" process, even though everything was already dockerized. For matchmaking, we didn't have any solution yet.

                    After we did tons of local testing, we deployed our first production-ready Kubernetes cluster with #kubespray and deployed Agones (with Helm) on it. The installation was very easy and the official chart had just the right amount of knobs for us!

                    The aspect, that we were the most stunned about, is how seamless Agones integrates into the Kubernetes infrastructure. It reuses existing mechanisms like the Health Pings and extends them with more resource states and other properties that are unique to game servers. But you're still free to use it however you like: One GameServer per Game-Session, one GameServer for multiple Game-Sessions (in parallel or reusing existing servers), custom allocation mechanisms, webhook-based scaling, ... we didn't run into any dead ends yet.

                    One thing, that I was a little worried about in the beginning, was the SDK integration, as there was no official one for Minecraft/Java. And the two available inofficial ones didn't satisfy our requirements for the SDK. Therefore, we went and developed our own SDK and ... it was super easy! Agones does publish their Protobuf files and so we could generate the stubs with #Protoc. The existing documentation regarding Client-SDKs from Agones was a great help in writing our own documentation for the interface methods.

                    And they even have excellent tooling for testing your own SDK implementations. With the use of Testcontainers we could just spin up the local SDK testing image for each of the integration tests and could confirm that our SDK is working fine. We discovered a very small inconsistency for one of the interface methods, submitted an issue and a corresponding PR and it was merged within less than 24 hours.

                    We've now been using Agones for a few months and it has proven to be very reliable, easy to manage and just a great tool in general.

                    See more
                    RSpec logo

                    RSpec

                    1K
                    171
                    0
                    Behaviour Driven Development for Ruby
                    1K
                    171
                    + 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 · 306.3K 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
                        pytest logo

                        pytest

                        875
                        224
                        0
                        A full-featured Python testing tool to help you write better programs
                        875
                        224
                        + 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