Open Source Software Testing Tools

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.

The web has evolved. Finally, testing has too. Fast, easy and reliable testing for anything that runs in a browser. Installing Cypress is simple. No dependencies, extra downloads, or changes to your code required. Write tests easily and quickly, and watch them execute in real time as you build your web application. Debugging your tests in CI is as easy as running tests locally. With built in parallelization and load balancing. Record CI test results, screenshots and video, and view aggregated, next-level insights in your dashboard. Build up a suite of CI tests, record their results and gain powerful insights. Install the Cypress Test Runner and write tests locally. Cypress has been made specifically for developers and QA engineers, to help them get more done. Cypress is based on a completely new architecture. No more Selenium. Lots more power.

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.

Deepchecks is the leading tool for testing and for validating your machine learning models and data, and it enables doing so with minimal effort. Deepchecks accompany you through various validation and testing needs such as verifying your data’s integrity, inspecting its distributions, validating data splits, evaluating your model and comparing between different models. While you’re in the research phase, and want to validate your data, find potential methodological problems, and/or validate your model and evaluate it. To run a specific single check, all you need to do is import it and then to run it with the required (check-dependent) input parameters. More details about the existing checks and the parameters they can receive can be found in our API Reference. An ordered collection of checks, that can have conditions added to them. The Suite enables displaying a concluding report for all of the Checks that ran.

Most continuous integration platforms limit the number of threads one can use. If you have more than one test suite running puppeteer chances are that your test will timeout. This is because jest will try to run puppeteer in parallel and the CI platform won't be able to handle all the parallel jobs in time. A fix to this is to run your test serially when in a CI environment. Users have discovered that running test serially in such environments can render up to 50% of performance gains. Writing integration test can be done using Puppeteer API but it can be complicated and hard because API is not designed for testing. Debugging tests can be hard sometimes and it is very useful to be able to pause tests in order to inspect the browser. Jest Puppeteer exposes a method jestPuppeteer.debug() that suspends test execution and gives you the opportunity to see what's going on in the browser.

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.

What we introduce in Growth is just a series of practices, and the actual combat of Growth will lead readers to implement these practices. You will see how to develop a web application (blog). How to write tests - unit tests, functional tests, automated UI tests. Build and use continuous integration. Added SEO support - Sitemap, Webmaster Tools and Google Analytics. Create API, make AutoComplete. Develop the corresponding APP and its API - view articles, user login, publish articles. Make a Single Page Application. Configurable management.

Xinc is a free open source continuous integration server written in PHP 5. The builder of choice is Phing and it comes with builtin SVN support. Currently Xinc 2.0 is under heavy development. A final version of Xinc 2.0 will be released until middle of f

AHrg is a development tool that combines the automation of Continuous Integration with Testing and Metrics capabilities.

The C'it (Continuous Integration and Testing) project (say "see it!") is a set of services to increase the perception of the evolving software, letting you easily implement continuous integration at its best.

A VM containing a turn-key solution for continuous integration with source code control, build management, automated testing, security analysis, defect tracking, and project management, all using open source tools.

High velocity native mobile development requires us to adopt continuous integration workflows, which means our reliance on manual QA has to drop significantly. Detox tests your mobile app while it's running in a real device/simulator, interacting with it just like a real user. The most difficult part of automated testing on mobile is the tip of the testing pyramid - E2E. The core problem with E2E tests is flakiness, tests are usually not deterministic. We believe the only way to tackle flakiness head on is by moving from black box testing to gray box testing. That's where Detox comes into play. Detox is built from the ground up to support React Native projects as well as pure native ones. Read the Getting Started Guide to get Detox running on your app in less than 10 minutes. We believe that the only way to address the core difficulties with mobile end-to-end testing is by rethinking some of the principles of the entire approach.

MSTestCoverage2XML is intended to be a set of tools to work in Continuous Integration environment different than MS Team Server. It includes a command line tool to generate coverage xml reports from data.coverage files