0 views collected around this technical thread.
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 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 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 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.
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.