Software testing bug tracking tutorials and videos

Open Source Bug Tracking Tools

Software Testing Magazine — Wed, 16 Jul 2025 14:00:39 +0000

Bugs, issue, defect, there are many names to define the problems you have with software, either during the code development phase or when the application is already in production. Bug tracking tools are an integrated part of a software quality and software testing strategy and there are many open source tools available. Depending on your needs, you don’t need however to spend a lot of money to use a bug tracking system as there are many open source bug trackers that have many features, a good reputation and a long history. This article lists the main open source bug tracking tools available today. Use our contact form to make us aware of some open source defect tracking software that we should add to this list. Here are some features that you could find in open source bug tracking tool: Is it a web-based or a local bug tracking tool that you can install on a local computer Can you define and manage your own bug workflow Can you add to the bug data some custom fields for bug triage Is there a system to notify people concerned by a bug about its life-cycle What reports and statistics are available Can you take screenshots of the application when you report a bug What are the file attachment and sharing capabilities * Updates July 16 2025 Added: BugTrackly, Debugsy, Ticket Tracker February 2 2024: Added: git-bug, lavagna Renamed: The Bug Genie renamed Pachno BugTracker.NET BugTracker.NET is a free, open-source, web-based bug or customer support [...]

The post Open Source Bug Tracking Tools first appeared on Software Testing Magazine.

Suptask Review – Slack Ticketing Software

Software Testing Magazine — Thu, 22 Feb 2024 16:53:27 +0000

Are you considering if Suptask is the right ticketing tool for your Slack workspace? This 2024 task review scrutinizes its capabilities, compatibility with other systems, and advertised performance. Uncover whether Suptask streamlines collaboration among your team members and compare it to alternative ticketing solutions. Suptask: Revolutionizing Ticketing Systems Suptask distinguishes itself as a robust ticketing system, seamlessly integrated within your Slack workspace, enabling you to accomplish the following: Initiate, accept, and handle tickets directly on the platform Collaborate in a communal channel or via Direct Messages (DM) with users Streamline your overall experience with managing tickets For teams that must handle sensitive information carefully, Suptask delivers several key security features: Private ticket options: Maintains privacy of confidential data while still allowing collaboration among agents for effective resolution. Customizable forms and fields for tickets: Adapt the system’s functionality to meet unique organizational requirements. Insightful dashboard analytics featuring KPI metrics: Tracks support team performance through critical data insights. As such, Suptask serves as a Slack help desk integration that places a high emphasis on both security measures and efficiency. It incorporates tracking systems designed to ensure peak operational effectiveness. What it means to be next-generation AI in ticket management solutions is how Suptask furnishes overviews of ongoing tickets within Slack, including specialized web views based on custom settings or preferences. Coupled with integrations into platforms like Gitlab, Github, JIRA, and Zendesk—Suptask elevates above typical issue-tracking frameworks by offering customers a multifaceted approach to handling support-related inquiries. Integration with Slack Workspace Suptask’s key [...]

The post Suptask Review – Slack Ticketing Software first appeared on Software Testing Magazine.

The Role of Attachments in Bugs Reports

Software Testing Magazine — Wed, 08 Jan 2020 17:51:14 +0000

When the software quality assurance people and the software developers are member of two different teams, bug discovery and reporting could often be a source of conflict caused by misunderstanding. This article explains how the quality of a bug report’s attachments can help to improve the communication between software testers and developers. Author: Nataliia Syvynska, TestMatick, https://testmatick.com/ The software testing company faces the challenge to correctly explain to a software developer the detected bug and make it as clear as possible. There is no doubt that the best option for this is an illustrative example or attachments that are considered as one of the main parts of the bug report. This is why you should attach all that you found to your bug report. Let’s see what are attachments: they are the files that describe bugs and are attached to bug reports. Types of attachments There are three types of attachments: Video file; Logs; Screenshots. A video file is a recording of the screen that has all the developer’s bugs. It would be better to attach the video in file formats such as «.avi», «.mp4» and «.mkv» because they are played by almost every modern media player. Besides, they are accepted by the Mantis Bug Tracker . You can upload the video of the bug in the Upload files section. But it is worth remembering that there are limits to the video file size (up to 5 000 KB). Logs (log files) are the text files that record the activity and describe the performance of the service and the computer in general. During software testing, people use logs when the bug cannot be displayed [...]

The post The Role of Attachments in Bugs Reports first appeared on Software Testing Magazine.

Bug Metrics and Incident Management

Software Testing Magazine — Mon, 11 Dec 2017 14:16:19 +0000

The main result of software testing activities is finding bugs that are also called defects or incidents. Besides correcting them, what could you do with the information that they provide? In this extract from her book “Guide to Advanced Software Testing”, Anne Mette Hass discusses how you can define and use metrics from your bug tracking activities to better understand your software testing efforts and software development process. There is no reason to collect information about incidents or defects if it is not going to be used for anything. On the other hand, information that can be extracted from incident reports is essential for a number of people in the organization, including test management, project management, project participants, process improvement people, and organizational management. If you are involved in the definition of incident reports, then ask these people what they need to know—and inspire them, if they do not yet have any wishes. The primary areas for which incident report information can be used are: * Estimation and progress; * Incident distribution; * Effectiveness of quality assurance activities; * Ideas for process improvement. Bugzilla screen. Source: https://wiki.mozilla.org/BMO/How_to_Use_Bugzilla Direct measures may be interesting, but it gets even more interesting when we use them for calculation of more complex measurements. We don’t learn much if we are told that testing has found 543 faults. But if we know that we had estimated finding approximately 200, we have gained some food for thought. Some of the direct measures we can extract from incident [...]

The post Bug Metrics and Incident Management first appeared on Software Testing Magazine.