Open Source Linux Software Testing Tools
Sort By:
Software Testing Tools for Linux
View 42 business solutionsBrowse free open source Software Testing tools and projects for Linux below. Use the toggles on the left to filter open source Software Testing tools by OS, license, language, programming language, and project status.
-
Paessler - Monitor Your Whole Network in MinutesWaiting weeks for a monitoring rollout isn't an option when infrastructure doesn't stop running. PRTG's auto-discovery scans your network and suggests from over 200 pre-configured sensor types, so you're watching servers, applications and devices within minutes, not after a multi-week deployment. Enterprise-strength monitoring, without the enterprise complexity. Start your free trial today.
-
MongoDB Atlas runs apps anywhereMongoDB Atlas gives you the freedom to build and run modern applications anywhere—across AWS, Azure, and Google Cloud. With global availability in over 115 regions, Atlas lets you deploy close to your users, meet compliance needs, and scale with confidence across any geography.
-
1
JUnit 5
Programmer-friendly testing framework for Java and the JVM
The 5th major version of the programmer-friendly testing framework for Java and the JVM. JUnit 5 is the next generation of JUnit. The goal is to create an up-to-date foundation for developer-side testing on the JVM. This includes focusing on Java 8 and above, as well as enabling many different styles of testing. Official CI build server for JUnit 5. Used to perform quick checks on submitted pull requests and for build matrices including the latest released OpenJDK and early access builds of the next OpenJDK. The JUnit Platform serves as a foundation for launching testing frameworks on the JVM. It also defines the TestEngine API for developing a testing framework that runs on the platform. Furthermore, the platform provides a Console Launcher to launch the platform from the command line and the JUnit Platform Suite Engine for running a custom test suite using one or more test engines on the platform. First-class support for the JUnit Platform also exists in popular IDEs. -
2
Ginkgo
BDD testing framework for Go
Ginkgo is a Go testing framework built to help you efficiently write expressive and comprehensive tests using Behavior-Driven Development (“BDD”) style. It is best paired with the Gomega matcher library but is designed to be matcher-agnostic. These docs are written assuming you’ll be using Gomega with Ginkgo. They also assume you know your way around Go and have a good mental model for how Go organizes packages under $GOPATH. Ginkgo is tested against Go v1.6 and newer To install Go, follow the installation instructions. An empty test suite is not very interesting. While you can start to add tests directly into books_suite_test.go you’ll probably prefer to separate your tests into separate files (especially for packages with multiple files). Ginkgo builds on Go's testing package, allowing expressive Behavior-Driven Development ("BDD") style tests. It is typically (and optionally) paired with the Gomega matcher library. -
3
GoogleTest
Google Testing and Mocking Framework
GoogleTest is Google's C++ mocking and test framework. It's used by many internal projects at Google, as well as a number of notable projects such as The Chromium projects, the OpenCV computer vision library, and the LLVM compiler. This GoogleTest project is actually a union of what used to be two separate projects: the old GoogleTest and GoogleMock, an extension of GoogleTest for writing and using C++ mock classes. Since they were so closely related, they were merged to create an even better GoogleTest. GoogleTest features an xUnit test framework, a rich set of assertions, user-defined assertions, death tests, among many others. It's been used on a variety of platforms, including Cygwin, Symbian, MinGW and PlatformIO. -
4
FORTRAN Unit Test Framework (FRUIT)
FORTRAN Unit Test Framework FRUIT - TDD in FORTRAN
FORTRAN Unit Test Framework, written in FORTRAN 95. So that all FORTRAN features can be tested. FRUIT has assertion, fixture, setup, teardown, report, spec, driver generation. Rake used as build tool. Tutorials at http://fortranxunit.wiki.sourceforge.net The core testing part is in FORTRAN, this part can be used independent of the Ruby codes. The Ruby code is to make fixtures and reports easier. Rake is to build the project elegantly. This project also demonstrate a new way to build mixed language code in an alternative way than Make. Most of the FORTRAN are important in nature, used in nuclear and aerospace codes, etc, and maintained and written actively. Please help to bring TDD practices to the FORTRAN community. The change could be very hard, personally, I quit, since I could not make the change. I hope your organization will be successful. Enjoy a cup of fruit while maintaining FORTRAN ! Andrew Hang Chen and other maintainers who feel importance of TDD in cr -
Host LLMs in Production With On-Demand GPUsDeploy your model, get an endpoint, pay only for compute time. No GPU provisioning or infrastructure management required.
-
5
JUnit 4
A programmer-oriented testing framework for Java
JUnit is a simple framework to write repeatable tests. It is an instance of the xUnit architecture for unit testing frameworks. You need to have a JDK installed and a text editor. (In general it is recommended to use a build tool for building your software and running the tests.). JUnit features include assertions for testing expected results, test fixtures for sharing common test data, test runners for running tests. JUnit was originally written by Erich Gamma and Kent Beck. JUnit is Open Source Software, released under the Eclipse Public License Version 1.0. JUnit celebrates programmers testing their own software. In this spirit, bugs, patches, and feature requests that include JUnit tests have a better chance of being addressed than those without. -
6
Mockito
Most popular Mocking framework for unit tests written in Java
Mockito downloads and instructions for setting up Maven, Gradle and other build systems are available from the Central Repository and Bintray. Mockito 3.x requires Java 8, but otherwise doesn’t introduce any breaking changes compared to the 2.x series. Mockito 2.25.0 had an important feature added for anyone using mockito-inline. In particular anyone using Kotlin (which demands using mockito-inline) and PowerMock (which exacerbates the problem even more) will want to add this to all of their test classes to avoid a large memory leak. Fancy getting world-wide visibility and building up an eternal fame of an OSS contributor? Use the latest version! Hack and experiment. Speak up at the mailing list. Mockito is a mocking framework that tastes really good. It lets you write beautiful tests with a clean & simple API. Mockito doesn’t give you hangover because the tests are very readable and they produce clean verification errors. -
7
Catch2
A modern, C++-native, test framework for unit-tests, TDD and BDD
A modern, C++-native, test framework for unit-tests, TDD and BDD - using C++14, C++17 and later (C++11 support is in v2.x branch, and C++03 on the Catch1.x branch). Catch2 is mainly a unit testing framework for C++, but it also provides basic micro-benchmarking features and simple BDD macros. Catch2's main advantage is that using it is both simple and natural. Test names do not have to be valid identifiers, assertions look like normal C++ boolean expressions, and sections provide a nice and local way to share set-up and tear-down code in tests. You are on the devel branch, where the v3 version is being developed. v3 brings a bunch of significant changes, the big one being that Catch2 is no longer a single-header library. Catch2 now behaves as a normal library, with multiple headers and separately compiled implementation. -
8
Terratest
Go library that makes it easier to write automated tests
Terratest is a Go library that provides patterns and helper functions for testing infrastructure, with 1st-class support for Terraform, Packer, Docker, Kubernetes, AWS, GCP, and more. Create a file ending in _test.go and run tests with the go test command. E.g., go test my_test.go. Use Terratest to execute your real IaC tools (e.g., Terraform, Packer, etc.) to deploy real infrastructure (e.g., servers) in a real environment (e.g., AWS). Use the tools built into Terratest to validate that the infrastructure works correctly in that environment by making HTTP requests, API calls, SSH connections, etc. Undeploy everything at the end of the test. Write automated tests for infrastructure code, including the code you write for use with tools such as Terraform, Kubernetes, Docker, and Packer. This code is released under the Apache 2.0 License. -
9
The Software Testing Automation Framework (STAF) is a framework designed to improve the level of reuse and automation in test cases and test environments. The goal of STAF is to provide a complete end-to-end automation solution for testers.
-
Custom VMs From 1 to 96 vCPUs With 99.95% UptimeLive migration and automatic failover keep workloads online through maintenance. One free e2-micro VM every month.
-
10
Laravel Dusk
Laravel Dusk provides simple end-to-end testing and browser automation
Laravel Dusk provides an expressive, easy-to-use browser automation and testing API. By default, Dusk does not require you to install JDK or Selenium on your machine. Instead, Dusk uses a standalone Chromedriver. However, you are free to utilize any other Selenium driver you wish. -
11
NUnit 3 Framework
NUnit 3 Framework
NUnit is a unit-testing framework for all .Net languages. Initially ported from JUnit, the current production release, version 3, has been completely rewritten with many new features and support for a wide range of .NET platforms. NUnit is intended to be extensible. We can't do everything for everybody but we want to make it reasonably easy to extend NUnit. In many cases, users will be able to implement a special feature outside of our scope by simply creating a new attribute that embeds the required logic. In other cases, particularly in extending the engine, we rely on a plugin architecture. When running tests in a separate process, the console and gui runners make use of the NUnit Agent program, nunit-agent.exe. Although not directly run by users, nunit-agent does load and execute tests and users need to be aware of it, especially when debugging is involved. -
12
Qooxdoo JavaScript Framework
qooxdoo - Universal JavaScript Framework
qooxdoo is a universal JavaScript framework that enables you to create applications for a wide range of platforms. With its object-oriented programming model, you build rich, interactive applications (RIAs), native-like apps for mobile devices, light-weight traditional web applications or even applications to run outside the browser. You leverage its integrated tool chain to develop and deploy applications of any scale while taking advantage of modern web technologies like HTML5 and CSS3, its comprehensive feature set, and a state-of-the-art GUI toolkit. qooxdoo is open source under liberal licenses, led by a dedicated developer team, with a vibrant community. Qooxdoo offers a wide range of widgets and UI components, plus powerful server I/O communication. Built-in unit testing framework with unit tests across the API and User Interface testing. -
13
Buildbot
Python-based continuous integration testing framework
Buildbot is an open-source framework for automating software build, test, and release processes. At its core, Buildbot is a job scheduling system: it queues jobs, executes the jobs when the required resources are available, and reports the results. Your Buildbot installation has one or more masters and a collection of workers. The masters monitor source-code repositories for changes, coordinate the activities of the workers, and report results to users and developers. Workers run on a variety of operating systems. You configure Buildbot by providing a Python configuration script to the master. This script can be very simple, configuring built-in components, but the full expressive power of Python is available. This allows dynamic generation of configuration, customized components, and anything else you can devise. The framework itself is implemented in Twisted Python, and compatible with all major operating systems. -
14
Pacu
The AWS exploitation framework, designed for testing security
Pacu (named after a type of Piranha in the Amazon) is a comprehensive AWS security-testing toolkit designed for offensive security practitioners. While several AWS security scanners currently serve as the proverbial “Nessus” of the cloud, Pacu is designed to be the Metasploit equivalent. Written in Python 3 with a modular architecture, Pacu has tools for every step of the pen testing process, covering the full cyber kill chain. Pacu is the aggregation of all of the exploitation experience and research from our countless prior AWS red team engagements. Automating components of the assessment not only improves efficiency but also allows our assessment team to be much more thorough in large environments. What used to take days to manually enumerate can be now be achieved in minutes. There are currently over 35 modules that range from reconnaissance, persistence, privilege escalation, enumeration, data exfiltration, log manipulation, and miscellaneous general exploitation. -
15
Criterion
A cross-platform C and C++ unit testing framework for the 21st century
Most test frameworks for C require a lot of boilerplate code to set up tests and test suites -- you need to create a main, then register new test suites, then register the tests within these suites, and finally call the right functions. This gives the user great control, at the unfortunate cost of simplicity. Criterion follows the KISS principle, while keeping the control the user would have with other frameworks. Supports parameterized tests and theories. Progress and statistics can be followed in real time with report hooks. TAP output format can be enabled with an option. Runs on Linux, FreeBSD, macOS, and Windows (Compiling with MinGW GCC and Visual Studio 2015+). If you'd like to see Criterion included in your favorite distribution, please reach out to their package maintainers team. A default entry point is provided, no need to declare a main unless you want to do special handling. -
16
Zerocode
API automation and load testing framework
A community-developed, free, open source, microservices API automation and load testing framework built using JUnit core runners for Http REST, SOAP, Security, Database, Kafka and much more. Zerocode Open Source enables you to create, change, orchestrate and maintain your automated test cases declaratively with absolute ease. Zerocode makes it easy to create and maintain automated tests with absolute minimum overhead for REST,SOAP, Kafka Real Time Data Streams and much more. It has the best of best ideas and practices from the community to keep it super simple, and the adoption is rapidly growing among the developer/tester community. Zerocode is a modern lightweight, simple and extensible open-source framework for writing test intentions in simple JSON or YAML format that facilitates both declarative configuration and automation. Put simply, Zerocode alleviates pain and brings simplicity to modern API automation. -
17
chai
BDD / TDD assertion framework for node.js
Chai is a BDD / TDD assertion library for node and the browser that can be delightfully paired with any javascript testing framework. Chai has several interfaces that allow the developer to choose the most comfortable. The chain-capable BDD styles provide an expressive language & readable style, while the TDD assert style provides a more classical feel. Plugins extend Chai's assertions to new contexts such as vendor integration & object construction. Developers can build their own plugins to share with community or use the plugin pattern to DRY up existing tests. You can also use it within the browser; install via npm and use the chai.js file found within the download. Browse our growing directory of custom plugins & vendor integrations to find the best tool for your needs. Chai has an extensive utility belt for plugin developers. Learn how to build your plugins & share. -
18
doctest
Fastest feature-rich C++11/14/17/20 single-header testing framework
doctest is a new C++ testing framework but is by far the fastest both in compile times (by orders of magnitude) and runtime compared to other feature-rich alternatives. It brings the ability of compiled languages such as D / Rust / Nim to have tests written directly in the production code thanks to a fast, transparent and flexible test runner with a clean interface. The framework is and will stay free but needs your support to sustain its development. There are lots of new features and maintenance to do. There are many C++ testing frameworks - Catch, Boost.Test, UnitTest++, cpputest, googletest and others. The key differences between it and other testing frameworks are that it is light and unintrusive. Ultra light on compile times both in terms of including the header and writing thousands of asserts. Doesn't produce any warnings even on the most aggressive warning levels for MSVC/GCC/Clang. -
19
Beego
Open source framework to build & develop applications in the Go way
Beego is an open source, high-performance web framework for building and developing applications in Go. Beego offers plenty of superb features, including RESTful support, MVC architecture, powerful built-in modules, intelligent routing and monitoring, plus Go-specific features like interfaces and struct embedding. Beego is very easy to use. Features like code hot compile, automated testing, as well as automated packing and deploying allow you to build your applications in a snap. Beego can be used for the rapid development of RESTful APIs, web apps and backend services that are written in Go. -
20
Protractor
E2E test framework for Angular apps
Protractor is an end-to-end test framework for Angular and AngularJS applications. Protractor runs tests against your application running in a real browser, interacting with it as a user would. Protractor is built on top of WebDriverJS, which uses native events and browser-specific drivers to interact with your application as a user would. Protractor supports Angular-specific locator strategies, which allows you to test Angular-specific elements without any setup effort on your part. You no longer need to add waits and sleeps to your test. Protractor can automatically execute the next step in your test the moment the webpage finishes pending tasks, so you don’t have to worry about waiting for your test and webpage to sync. Protractor needs two files to run, a spec file and a configuration file. Open a new command line or terminal window and create a clean folder for testing. -
21
FitLibrary provides general-purpose fixtures (and runners) for storytests with Fit and FitNesse. DoFixture provides an elegant way of organising storytests and expressing workflow.
-
22
pFUnit
Unit testing framework for Fortran with MPI extensions
pFUnit is now hosted and developed on GitHub. And will be completely removed from sourceforge on January 01, 2020 Please use: https://github.com/Goddard-Fortran-Ecosystem/pFUnit GitHub has been the primary host for some time now, but with the release of pFUnit 4.0 earlier in 2019, the sourceforge site is very out of date. -
23
Keploy
Testing for Developers. Toolkit that creates test-cases and data mocks
Keploy is a functional testing toolkit for developers. It generates E2E tests for APIs (KTests) along with mocks or stubs(KMocks) by recording real API calls. KTests can be imported as mocks for consumers and vice-versa. Merge KTests with unit testing libraries(like Go-Test, JUnit..) to track combined test coverage. KMocks can also be referenced in existing tests or use anywhere (including any testing framework). KMocks can also be used as tests for the server. Keploy is added as a middleware to your application that captures and replays all network interaction served to the application from any source. Keploy has native interoperability as it integrates with popular testing libraries like go-test, junit. Code coverage will be reported with existing plus KTests. It'll also be integrated in CI pipelines/infrastructure automatically if you already have go-test, junit integrated. -
24
RSpec Rails
RSpec for Rails 5+
RSpec Rails brings the RSpec testing framework to Ruby on Rails as a drop-in alternative to its default testing framework, Minitest. In RSpec, tests are not just scripts that verify your application code. They’re also specifications (or specs, for short): detailed explanations of how the application is supposed to behave, expressed in plain English. RSpec follows semantic versioning, which means that “major version” upgrades (e.g., 2.x → 3.x) come with breaking changes. If you’re upgrading from version 2.x or below, read the rspec-rails upgrade notes to find out what to watch out for. In RSpec, assertions are called expectations, and every expectation is built around a matcher. When you expect(a).to eq(b), you’re using the eq matcher. RSpec Rails defines ten different types of specs for testing different parts of a typical Rails application. Each one inherits from one of Rails’ built-in TestCase classes, meaning the helper methods provided by default in Rails tests are available. -
25
gomock
GoMock is a mocking framework for the Go programming language
gomock is a mocking framework for the Go programming language. It integrates well with Go's built-in testing package, but can be used in other contexts too. Once you have installed Go, install the mockgen tool. If you have not done so already be sure to add $GOPATH/bin to your PATH. If you use mockgen in your CI pipeline, it may be more appropriate to fixate on a specific mockgen version. Source mode generates mock interfaces from a source file. It is enabled by using the -source flag. Other flags that may be useful in this mode are -imports and -aux_files. Reflect mode generates mock interfaces by building a program that uses reflection to understand interfaces. It is enabled by passing two non-flag arguments, an import path, and a comma-separated list of symbols. The mockgen command is used to generate source code for a mock class given a Go source file containing interfaces to be mocked.
