The article analyzes how AI agents are shifting from merely usable to trustworthy, outlines three testing paradigms, presents two detailed real‑world case studies in finance and healthcare, and proposes the TAME framework for sustainable, robust agent testing.
The article explains how adversarial testing shifts from a user‑centric to an attacker‑centric paradigm, illustrates real‑world cases in finance, autonomous driving and AI, outlines perturbation layers, evaluation metrics, automation pipelines, and three counter‑intuitive principles for effective deployment, highlighting its advantages over conventional testing.
The article reinterprets James A. Whittaker's global exploratory testing by classifying testers into roles such as traveler, student, and official, and maps each role to specific roaming scenarios—shopping, landmark, overnight, dangerous, personalized, etc.—with concrete exploratory techniques and practical examples for software testing.
This article introduces the Heuristic Test Strategy Model (HTSM), explains its four focus areas—test technology, project environment, product elements, and quality standards—compares it with the 2W1H method, and provides detailed guidance on applying HTSM steps such as project environment analysis, product element definition, quality standard selection, and test technique implementation.
This article presents a comprehensive evaluation framework for OPPO's XiaoBu AI assistant, covering evaluation concepts, objectives, five key elements, sampling methods, dimension selection, annotation scoring, report generation, and a detailed Q&A that illustrates practical metrics and processes for voice and search services.
This article explains how systematic unit testing boosts R&D efficiency, outlines its origins, methods, tools, and evaluation standards, and shares practical insights from JD Retail specialists on implementing effective unit tests in real‑world projects.
The article explains the distinction between a test specification (technical‑focused test scheme) and a test plan (project‑focused schedule), describes when each should be created during a project lifecycle, and provides templates, methods, and reporting formats for effective software testing.
The article examines why manual testing remains essential despite automation and AI trends, highlighting common weaknesses such as insufficient test scenarios, over‑focus on functionality, reliance on test cases, preset thinking, and the need for innovative, user‑centric testing approaches.
This article presents a concise collection of practical techniques for crafting effective test cases, covering domain knowledge, modular design, preconditions, data handling, organization, naming conventions, client focus, verification coverage, reusability, grouping, clarity, documentation, and ongoing maintenance to improve testing productivity.
Exploratory testing, a flexible, unscripted approach integral to agile development, enables rapid discovery of defects, improves user experience, and complements automated regression testing, while its various types, benefits, challenges, and common myths are examined to guide teams in effective implementation.
This article presents a comprehensive data quality model derived from ISO 9126, maps its characteristics to data testing, outlines practical testing methods and tool requirements, and demonstrates how to integrate quality checks into the data development lifecycle for reliable, efficient big‑data pipelines.
This article reviews a training session on bug reporting that introduces a four‑step approach—four Ws plus screenshot and clear preconditions/results—to help testers write precise, understandable bugs and improve collaboration between developers and QA teams.
This article explains why modern software projects must shorten client acceptance cycles and outlines six practical methods—defining acceptance criteria, managing test data, providing alpha versions, setting tester boundaries, clarifying stage scopes, and ensuring transparent test case management—to achieve rapid, high‑quality releases.
This article explains what usability testing is, outlines its purpose, describes the typical workflow—including preparation, task design, pilot testing, user recruitment, execution, data analysis, and reporting—and highlights the benefits of applying rapid usability testing in product development.
This article explains what product evaluation is, why it matters, and outlines a step‑by‑step process—including defining goals, setting standards, selecting methods, executing tests, analyzing results, and presenting findings—to ensure both functional and experiential quality of products.
