What is Mockito and what are its top alternatives?
Top Alternatives to Mockito
JUnit is a simple framework to write repeatable tests. It is an instance of the xUnit architecture for unit testing frameworks. ...
Appium is an open source test automation framework for use with native, hybrid, and mobile web apps. It drives iOS and Android apps using the WebDriver protocol. Appium is sponsored by Sauce Labs and a thriving community of open source developers. ...
It is a framework that brings fast and reliable unit tests to Android. Tests run inside the JVM on your workstation in seconds. Test drive your Android application with robolectric ...
It is an open-source library focused on making mocking in Kotlin great. It is a library with the possibility of mocking default arguments, final classes, varargs, coroutines and extension methods. ...
Cucumber is a tool that supports Behaviour-Driven Development (BDD) - a software development process that aims to enhance software quality and reduce maintenance costs. ...
Behaviour Driven Development for Ruby. Making TDD Productive and Fun.
PHPUnit is a programmer-oriented testing framework for PHP. It is an instance of the xUnit architecture for unit testing frameworks. ...
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. ...
Mockito alternatives & related posts
related JUnit posts
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.
Automated tests are hard to create, often fragile and incomplete, we at retest decided to support a different testing paradigm.
Therefore, we created recheck - an open source API / CLI. The testing module recheck uses Golden Master, where each webpage can be checked thus defining individual specifications is unnecessary. Test automation is made more robust and the number of false positives are reduced. This means if a test fails with recheck, it was meant to fail.
Review - our efficient and intuitive GUI application accepts or ignores changes easily and seamlessly. It also allows users to reduce their workload and learning curve with a patented 1-click mechanism. And since review is not a SaaS tool this removes the detested test maintenance.
Our API/CLI will be an open source software testing tool. While our GUI is a paid fully functioning offline license.
JUnit Selenium Java GitHub JIRA
related Appium posts
I chose WebdriverIO and Appium to implement a E2E tests solution on a native mobile app. WebdriverIO goes well beyond just implementing the Selenium / Appium protocol and allows to run tests in parallel out of the box. Appium has the big advantage of supporting iOS and Android platforms, so the test codebase and tools are exactly the same, which greatly reduces the learning curve and implementation time.
related Cucumber posts
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.
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.
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