The article explores how software testing teams can identify and implement both technical and process-oriented innovations—ranging from tool usability improvements and automation to standardization, templating, and cross‑domain borrowing—to enhance efficiency, quality, and overall value.
This article explains how Qunar's Qunit testing framework was enhanced with automatic baseline generation and new tags—dataMode, dataHolder, dataAssert, and dbAssert—to simplify test case creation, maintenance, and verification while reducing reliance on external data services.
The article examines the growing crisis in the software testing industry, highlighting external stagnation, internal role changes at Huawei, the impact of DevOps and cloud technologies, and proposes how testers can adapt by expanding skills, embracing automation, and positioning themselves as quality guardians.
This article explains the fundamentals of unit testing, compares it with integration testing and TDD, describes characteristics of good unit tests, shows a practical .NET example using XUnit, FluentAssertions and Moq, and offers architectural tips for writing test‑friendly code.
With increasing emphasis on user experience, this article introduces five widely used web performance testing tools—HP LoadRunner, Apache JMeter, Load UI, Httperf, and Siege—detailing their capabilities for load simulation, functional testing, and performance analysis to help developers and testers optimize application reliability and speed.
This article examines the common pain points of integration testing in distributed systems, including weak cross‑coupling coverage, lack of clear standards, chaotic composite scenarios, and insufficient risk assessment, and discusses current mitigation approaches and open questions for future exploration.
This article outlines common compatibility testing challenges across software components, online upgrades, driver interactions, and operating system variations, and provides practical testing strategies to detect and mitigate issues such as version mismatches, file ordering, and security software conflicts.
This article presents a collection of fifteen C programming quiz questions, each accompanied by the original code, multiple‑choice options, the correct answer, and in‑depth explanations covering topics such as setjmp/longjmp, pointer casting, recursion, sizeof, function pointers, variadic functions, and static variables.
The 2005 Mizuho Securities “fat‑finger” incident, caused by a trader’s input error and a hidden bug in the Tokyo Stock Exchange’s Fujitsu‑built trading system, led to a ¥400 billion loss, sparking extensive litigation that highlighted responsibilities for software bugs, system testing, and operational risk management.
A 2005 fat‑finger error by a Mizuho trader triggered a ¥400 billion loss, leading to a landmark court case that clarified liability for software bugs in financial systems and highlighted the need for rigorous testing and evidence preservation.
This article introduces the concept of basic quality within a product competitiveness model, outlines key evaluation dimensions such as functionality, performance, compatibility, and security, and provides step-by-step guidance on defining metrics, selecting testing methods, and quantifying results, especially for mobile applications.
This guide explains why vague "error" messages frustrate developers, outlines the essential role of non‑technical staff in quality assurance, and provides a step‑by‑step template for creating clear, actionable bug reports that help engineers resolve issues faster.
This article provides a comprehensive checklist for code reviewers, covering formatting, design, readability, functionality, security, testing, performance, and resource usage, while explaining why many of these aspects can be automated and how to balance manual inspection with tooling.
The article explains how Docker’s lightweight container technology speeds up test environment setup, reduces resource consumption, supports blue/green deployments, and simplifies production orchestration, making it an essential tool for modern development teams seeking efficient, reliable software delivery.
The article examines Quora's engineering practices—including static analysis, post‑commit code review, automated testing, and systematic legacy code cleanup—that enable the company to maintain high code quality while sustaining fast development cycles.
