Arquillian vs react-testing-library

Need advice about which tool to choose?Ask the StackShare community!

Arquillian

32
48
+ 1
0
react-testing-library

265
155
+ 1
4
Add tool

react-testing-library vs Arquillian: What are the differences?

react-testing-library: A lightweight solution for testing React components. It is a simple and complete React DOM testing utility that encourage good testing practices. It provides light utility functions on top of react-dom and react-dom/test-utils, in a way that encourages better testing practices; Arquillian: An Innovative Testing Platform for the JVM. 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.

react-testing-library and Arquillian can be categorized as "Testing Frameworks" tools.

Some of the features offered by react-testing-library are:

  • light-weight solution for testing
  • React DOM testing utilities
  • works with any environment that provides DOM APIs

On the other hand, Arquillian provides the following key features:

  • Real Tests
  • IDE Friendly
  • Test Enrichment

react-testing-library is an open source tool with 8.63K GitHub stars and 478 GitHub forks. Here's a link to react-testing-library's open source repository on GitHub.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Arquillian
Pros of react-testing-library
    Be the first to leave a pro
    • 3
      We can test behavior
    • 1
      Good documentation

    Sign up to add or upvote prosMake informed product decisions

    What is Arquillian?

    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.

    What is react-testing-library?

    It is a simple and complete React DOM testing utility that encourage good testing practices. It provides light utility functions on top of react-dom and react-dom/test-utils, in a way that encourages better testing practices.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Arquillian?
    What companies use react-testing-library?
    See which teams inside your own company are using Arquillian or react-testing-library.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Arquillian?
    What tools integrate with react-testing-library?
    What are some alternatives to Arquillian and react-testing-library?
    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 is a simple framework to write repeatable tests. It is an instance of the xUnit architecture for unit testing frameworks.
    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 is a tool that supports Behaviour-Driven Development (BDD) - a software development process that aims to enhance software quality and reduce maintenance costs.
    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.
    See all alternatives