Search Results for "open dynamics engine"

Karate is the only open-source tool to combine API test-automation, mocks, performance-testing and even UI automation into a single, unified framework. The BDD syntax popularized by Cucumber is language-neutral, and easy for even non-programmers. Assertions and HTML reports are built-in, and you can run tests in parallel for speed. There’s also a cross-platform stand-alone executable for teams not comfortable with Java. You don’t have to compile code. Just write tests in a simple, readable...

Python bindings for the Chromium Embedded Framework (CEF). CEF Python is an open source project founded by Czarek Tomczak in 2012 to provide Python bindings for the Chromium Embedded Framework (CEF). The Chromium project focuses mainly on Google Chrome application development while CEF focuses on facilitating embedded browser use cases in third-party applications. Lots of applications use CEF control, there are more than 100 million CEF instances installed around the world.

...Just write a test that uses the component you need to test for threading issues and assign load of threads to the test. Thanks to my employer (Nokia) for letting me publish the initial version of this tool as open-source!

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.

The uranium is a system for test automation. It uses a prolog language for high-level modelling of business process in software and system of drivers which allows use any channel for manage the program (web, db connection etc).

A very Flexible and Plugin-able Test Automation Engine. It fully supports the Standardized Test Tool Interfaces as described in http://www.testtoolinterfaces.com/

Tesbo is an open source AI-powered test case management software built for QA teams. Tesbo's Context Engine reads your actual project requirements from Jira and Linear, existing test cases, product documentation, and defect history before generating a single test case. Every draft cites exactly which requirement, document, and defect shaped it. Nothing enters your repository without a QA engineer approving it first.