Search Results for "web based system" - Page 4

Jdptool is a debug and profiler tool which based on JPDA; It provide both swing based and browser based GUI. It has sophisticated debugger without user interfere. It also provide profiler to memory usage and threads with numerous new feature

Digital User Stories is a web-based tool for eXtreme Programming teams. It is used to help XP teams with Iteration planning and User Stories management.

BugEye is an XML-based unit test creation framework. Being XML-based, it can be easily translated to almost any language. The current translations are C#, Java, JavaScript, and Visual Basic. Future translations include C++, Python, Perl, and PHP.

AjaxTestRunner is a web-based JUnit test runner for in-container testing with a cool AJAX interface.

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.

php todolist is a more advanced approach for simple todo lists. It is an ajax/sql-based multi user todolist, with priority, status and categories. You can use it as a bug track / feature request and task manager system within a group of developers.

ConSense is a singular "jack of all trades" web development console intended to ease all your bugtracking, testing and page architecture tasks. Its siblings, RedSand and SimpleClasses form a sound, dynamic, object oriented JavaScript/DHTML framework.

Testpilot is a browser based unit testing framework for testing websites. With it you can record the keystrokes and mouse events for a session and play them back automatically. You can include assertions for values in inputs DIVs or JavaScript variables.

A database and frontends to store testcases, track progress of test passes, and execute automated test cases.

jsAssertUnit is a unit testing framework based on assertions, helping JavaScript developers to test their code. Failing assertions about the program state are tracked in a Reporter window of a DOM compliant browser : IE5+, Mozilla, Netscape 6+, etc.

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.

Defects/Tasks/Documentation Tracking system using Ruby On Rails and multiple DB engines (MySQL, Postgresql, Oracle).

A simple and direct web based arduino programming suite. Development will start soon.

Lio is a javascript logger. There is only one file to solute any thing about log.

QAWIKI is a wiki for QA engineers. It is a wiki which also supports an Integrated Test Environment (ITE) which allows a QA engineer to create a test case on a portal and execute/schedule it on a remote box, then collect the logs and disp them in reports.

The easy path to Fitnesse.

Quantum replicates the functionalities of QC. Quantum will have the requirements, test cases, test runs, defects, RTM, TCM just as QC and will also implement custom fields. It is being developed on *AMP platform and is platform independent

The Simple Test Result Tool will show Test Results in a simple listing in your browser, provided that the test results are stored in the XML format as defined on www.testtoolinterfaces.com (i.e. the TestResult Interface).

Lastest.cloud is a free, open-source verification of development, self-hosted visual regression and end-to-end testing platform for web applications. An AI agent records you clicking through your running app and generates Playwright tests with multi-selector fallback. Replays are deterministic and token-free, so your CI/CD bill doesn't scale with your test suite. Lastest ships three diff engines side-by-side — pixel (pixelmatch), structural (SSIM), and perceptual (Butteraugli) — so...

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. The engine learns from every approval, edit, and rejection, so generated...