StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Testing Frameworks
  4. Testing Frameworks
  5. Arquillian vs Mockito

Arquillian vs Mockito

OverviewComparisonAlternatives

Overview

Mockito
Mockito
Stacks3.6K
Followers180
Votes0
GitHub Stars15.3K
Forks2.6K
Arquillian
Arquillian
Stacks32
Followers48
Votes0

Arquillian vs Mockito: What are the differences?

<Write Introduction here>

1. **Integration vs Unit Testing**: Arquillian is primarily used for integration testing, where the focus is on testing the interactions between multiple components in a real container environment. On the other hand, Mockito is a mocking framework used for unit testing, which involves isolating and testing individual components in isolation.
2. **Deployment**: Arquillian allows developers to deploy test archives to various containers at runtime, enabling the testing of code in a real-world environment. Mockito does not deal with deployment as it focuses on mocking behavior of objects and testing them in isolation without the need for a container.
3. **Real vs Mocked Objects**: When using Arquillian, developers work with real objects that are deployed in a container environment, allowing for end-to-end testing of the application. In contrast, Mockito creates mock objects that simulate the behavior of real objects, making it easier to focus on specific parts of the code.
4. **Scope of Testing**: Arquillian's scope extends to testing interactions between components, containers, and deployments, making it suitable for comprehensive integration testing scenarios. On the other hand, Mockito is mostly used for testing the behavior of individual units or components in isolation, making it more suitable for unit testing.
5. **Dependency on External Components**: Arquillian relies on actual containers and external resources to perform integration testing, which may require additional setup and configuration. Mockito, being a mocking framework, does not have dependencies on external components, making it easier to set up and run unit tests quickly.
6. **Purpose**: Arquillian is designed for developers who need to test the integration of various components in a real container environment, ensuring that the application behaves correctly in a deployed setup. Mockito, on the other hand, caters to developers who primarily focus on unit testing and mocking behaviors of objects to isolate and test specific parts of the code.

In Summary, Arquillian is focused on integration testing in real container environments, while Mockito is geared towards unit testing and mocking behaviors of objects in isolation.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

Mockito
Mockito
Arquillian
Arquillian

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.

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.

-
Real Tests; IDE Friendly; Test Enrichment; Classpath Control; Drive the Browser; Debug the Server
Statistics
GitHub Stars
15.3K
GitHub Stars
-
GitHub Forks
2.6K
GitHub Forks
-
Stacks
3.6K
Stacks
32
Followers
180
Followers
48
Votes
0
Votes
0
Integrations
No integrations available
Java
Java
Karate DSL
Karate DSL
Selenium
Selenium
Robolectric
Robolectric

What are some alternatives to Mockito, Arquillian?

Robot Framework

Robot Framework

It is a generic test automation framework for acceptance testing and acceptance test-driven development. It has easy-to-use tabular test data syntax and it utilizes the keyword-driven testing approach. Its testing capabilities can be extended by test libraries implemented either with Python or Java, and users can create new higher-level keywords from existing ones using the same syntax that is used for creating test cases.

Karate DSL

Karate DSL

Combines API test-automation, mocks and performance-testing into a single, unified framework. The BDD syntax popularized by Cucumber is language-neutral, and easy for even non-programmers. Besides powerful JSON & XML assertions, you can run tests in parallel for speed - which is critical for HTTP API testing.

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.

TestCafe

TestCafe

It is a pure node.js end-to-end solution for testing web apps. It takes care of all the stages: starting browsers, running tests, gathering test results and generating reports.

Spock Framework

Spock Framework

It is a testing and specification framework for Java and Groovy applications. What makes it stand out from the crowd is its beautiful and highly expressive specification language. It is compatible with most IDEs, build tools, and continuous integration servers.

Selenide

Selenide

It is a library for writing concise, readable, boilerplate-free tests in Java using Selenium WebDriver.

Capybara

Capybara

Capybara helps you test web applications by simulating how a real user would interact with your app. It is agnostic about the driver running your tests and comes with Rack::Test and Selenium support built in. WebKit is supported through an external gem.

PHPUnit

PHPUnit

PHPUnit is a programmer-oriented testing framework for PHP. It is an instance of the xUnit architecture for unit testing frameworks.

Detox

Detox

High velocity native mobile development requires us to adopt continuous integration workflows, which means our reliance on manual QA has to drop significantly. It tests your mobile app while it's running in a real device/simulator, interacting with it just like a real user.

Imagium

Imagium

Imagium provides AI based visual testing solution for various forms of testing. It makes the job easier for QA Automation, Mobile Testers, DevOps and Compliance teams. Imagium is easy to integrate with any programing language

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana