Search Results for "open dynamics engine" - Page 2

This project is intended for ISVs, SIs and software developers who need to integrate load generation engine into their applications. For enterprise load and performance testing initiatives, RadView offers WebLOAD Professional, a complete solution for creating, executing and analyzing the performance of web applications under load.

AFTER is a configurable test engine written in Ruby. Libraries can be added to facilitate testing against any application type. It also allows for test scripts to be written in any format provided there is an associated script reader for that format.

A small database stress tool written in Java. Emulates a given number of concurrent users querying the engine. Reports timing information for each test. Currently supports MySQL engine only.

An implementation of the Model-View-Controller (MVC) design pattern based on the Jakarta Struts Framework. Includes a core library (Horizon), a servlet container (Stratus), and a Server Pages Engine (Phase). Resembles the J2EE web container environment.

Servlet debugging support: Introspects the content of request, session and servlet context, appends a HTML representations of the data to the HTML pages served by the engine. Strategies used for introspection and visualization purpose are plugable.

The Open Log Engine is a powerful tool for advanced logging in games or programs. It easily allows you to make logging outputs in your program and analyse them afterwards with the Open Log Viewer, which provides you a powerful filtering system.

jECMAUnit is an ECMA (Javascript) unit testing framework that uses the underlying javascript engine and JUnit to perform the tests in java, allowing browser-less unit testing of javascript code

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.

Experior doesn't care what language your test program is written in. All it cares about is that each test's output begins and ends with a simple line of JSON. Your test program can validate its own output, in which case Experior just acts as a report engine. Alternatively -- or additionally -- you can write validation functions in JavaScript, and Experior will run them against the test output. Finally, Experior can compare your current test output against a copy of previous test output and...