The Xianyu team built an automated pipeline that scans pre‑release exception logs, extracts stack‑trace details with regex, maps them to Git file paths and commit authors, and instantly distributes precise bug tickets to the responsible developers, dramatically cutting debugging cost and time.
This article explains how systematic test case creation, clear verification steps, and disciplined bug tracking improve testing efficiency, ensure comprehensive coverage of core system logic and data flows, and help teams identify root causes to continuously raise software quality despite limited resources.
This article outlines the hard and soft competencies required for game functional testing, including test case creation, bug tracking, risk awareness, communication, proactive work habits, learning ability, and innovation, while offering practical strategies to improve testing efficiency and product quality.
This article explores horizontal management—coordinating with developers, designers, and product staff—through four concrete stories, highlighting communication pitfalls, bug‑tracking challenges, and practical steps to improve cross‑functional teamwork and project quality.
This article shares practical experiences and advice from a newcomer functional tester in game development, covering senior guidance, communication bottlenecks, unclear requirements, the need to question design, avoiding cascading bugs, comprehensive test‑case coverage, effective learning, and common automation pitfalls.
This comprehensive guide explains what bug tracking is, outlines effective workflows, lists essential features, compares top bug‑tracking tools—including BugHerd, Bugzilla, MantisBT, Jira, and more—while highlighting each tool's advantages, disadvantages, integrations, and pricing to help teams choose the right solution.
This article explains what bug tracking is, outlines a typical bug‑tracking workflow, describes the elements of a good bug report, lists criteria for choosing a bug‑tracking tool, and reviews twelve popular tools with their features, integrations, pricing, advantages and disadvantages, concluding with recommendations for teams of all sizes.
This article defines bug tracking, outlines effective workflows, describes the components of a good bug report, explains what bug‑tracking software should provide, lists key selection criteria, and reviews twelve popular tools with their features, integrations, pricing, pros and cons to help teams choose the right solution.
This article defines bug tracking, outlines essential workflow steps and report contents, and evaluates a range of bug tracking tools—including BugHerd, Bugzilla, MantisBT, DebugMe, Donedone, Marker.io, Jira, Bughost, Zoho, Backlog, and Redmine—highlighting their features, integrations, pricing, advantages, and drawbacks to help teams choose the right solution.
The article recounts a five‑day transition from student to test intern in Beijing, detailing the tools, platforms, testing processes, project workflow, and personal insights gained over two months of hands‑on QA work.
This article outlines a systematic, step‑by‑step approach for testers to gather evidence, reproduce, and diagnose production bugs on mobile and web platforms, emphasizing thorough data collection, environment checks, and collaborative debugging to improve response speed and reliability.
This article provides a comprehensive testing guideline covering test planning, test design, bug submission and tracking, regression testing scope determination, and internal communication practices to improve software quality and testing efficiency.
This article describes the challenges of traditional case and bug workflows in fast‑moving development, proposes automated solutions such as self‑checking test standards, checklist‑to‑case conversion, and reject‑rule enforcement, and details the architecture and user‑experience improvements of the Todolist platform integrated with Jira.
This article introduces the basic concepts of software testing, covering defect management tools, bug reproduction prerequisites, JIRA issue types, classification methods, severity and priority levels, status lifecycle, and the complete bug handling workflow.
All Debian 9 live images suffer from a critical installation bug caused by absolute package paths, leading to missing libzlo2‑2‑udeb files, and developers have opened a Grave‑severity bug report (#865015) with a fix currently being tested for a full rebuild.
This article introduces seven high-quality open‑source bug tracking tools—Bugzilla, Redmine, Trac, Mantis, Fossil, Phabricator, and WebIssues—detailing their origins, main features, and why they can boost project development and issue management for software teams.
This article chronicles a developer’s detailed workday, documenting the discovery, analysis, and resolution of numerous JavaScript bugs in IE7, the communication with teammates, and the systematic debugging process that ultimately led to fixing a critical comma‑induced error in the code.
The article examines why distinguishing bugs from feature requests is often futile, using a Visual Studio default‑font issue as a case study, and argues for focusing on constructive feedback rather than semantic arguments in software development.
