Search Results for "web based system"

ZenTao is an open source Scrum tool for application development projects with features including Backlog Management✓ Sprint and task✓ bug tracking✓ Scrum✓ Waterfall✓ Roadmap✓ Burndown✓ Kanban✓ SaaS✓ Self Hosting✓

TestLink is a web based Test Management tool. The application provides Test specification, Test plans and execution, Reporting, Requirements specification and collaborate with well-known bug trackers. Repository: https://github.com/TestLinkOpenSourceTRMS

... * Fastest helps automate all the necessary, but difficult test automation tasks like 'Mapping the test case execution with test plan document, updating centralized test management database, reporting, setup of automated nightly regressions in Continuous Integration (CI) environments, Running code / commands on remote hosts, Interacting with Web services, browser based automation using Selenium, SSH access, Sending Email notifications

Testa Online Test Management System is a powerful web-based application to take online multiple choice tests written in PHP. Create a quiz and hold it and see the statistics as easy as possible...

Simple test management interface for Selenium. It stores all tests in a database, removing the need for testers to access the webserver directly to edit or create tests and allows templating parts of tests, reducing test maintainence on app changes.

Open Test Manager aims to be a simple tool for managing test cases using a central database. It is written in java and uses a web-based user interface and an embedded database.

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

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...