Azure Test Plans vs JTrac

Azure Test Plans gives teams tools to plan, run, and track manual and exploratory testing for apps. For scripted tests, teams can track actionable defects and connect test cases and suites to user stories, features, or requirements. Exploratory sessions let testers design and run tests at the same time. During manual tests, Test Runner can capture screenshots, image action logs, and screen recordings. Reports, dashboard widgets, and customizable Power BI reports show plan progress and trends. The service integrates with Azure Pipelines for CI/CD testing and offers REST APIs and an extension contribution model. Manual testing is available in the web portal through supported browsers on major platforms; a free Test & Feedback extension supports exploratory testing in Chrome and Microsoft Edge. The free Stakeholders plan does not allow users to create or manage Test Plans. Basic is free for the first five users, then $6 per user per month; Basic + Test Plans costs $52 a month, billed at $52 per user per month. A 30-day trial is listed. Azure DevOps cloud-based load testing is deprecated; Microsoft points users to Azure Load Testing for managed load testing.

JTrac is a free, open-source issue-tracking web application written in Java and licensed under Apache Software License 2.0. It tracks bugs, action items, and tasks using project-specific fields and workflows. Administrators can set project roles, workflow states, and field-level permissions. Each project space supports up to 10 dropdown fields, 5 free-text fields, 3 numeric fields, and 3 date/time fields. Work tools include item history, file attachments, full-text search, custom-field filtering, dashboards, and Excel export. Status changes trigger email notifications by default, with SMTP configured by an administrator. Authentication options include LDAP, Active Directory, and CAS single sign-on; LDAP handles authentication only, so administrators must also create users and assign them to project spaces. JTrac requires Java 8 or higher, and a JRE is sufficient. It can use its embedded web server and database or be deployed as a WAR in a servlet 3.1 compliant container. The project lists developers, end users, IT, and quality engineers as its intended audience.