Innovating in Software Testing: Strategies and Methods

At first the author was reluctant to discuss the topic because it seemed too broad and vague, but later decided to summarize the innovation patterns in the testing field, correcting the misconception that innovation must be a huge, never‑done‑before breakthrough; any improvement, big or small, counts as innovation.

The discussion is divided into two parts: how to discover innovation points and concrete methods to apply those points, illustrated with a mind‑map image.

How to discover innovation points

The testing domain can be split into technical aspects and process‑management aspects, and the author suggests mining innovation from both.

Technical aspects

Consider improving test efficiency and performance, such as finding more convenient ways to collect data (e.g., using scripts instead of manual Excel work) and automating repetitive tasks. Evaluate tool usability and identify painful steps that can be streamlined. An example given is an online monitoring system that automatically checks the deployment status of hosts across many servers.

Process‑management aspects

The author proposes a "three‑ization" approach: standardization, templating, and toolization.

Standardization includes strict separation of responsibilities in the bug‑lifecycle and enforcing detailed defect reports, similar to code‑style guidelines. Templating involves creating reusable checklists, such as a release‑inspection template to avoid omissions. Toolization means building dedicated tools, like a weekly‑report system, to replace ad‑hoc email reports.

Specific innovation methods

Once an innovation point is identified, it should be acted upon immediately. The author lists several practical methods:

Horizontal comparison : Compare similar products to spot missing features. For example, after evaluating existing mock tools that required code changes, the team built a custom online mock service with configurable URLs.

Vertical comparison : Borrow ideas from different domains. Inspired by news aggregators, the team created a web portal to collect testing articles, named the "Three‑Swordsmen News" subsystem.

Cross‑domain borrowing : Leverage open‑source tools and ideas from other fields. The author describes using STF and Sikuli to automate mobile‑browser first‑paint measurements, turning a manual, time‑consuming process into a hundred‑fold efficiency gain.

Participating in industry salons, monitoring foreign trends, and applying development‑mindset techniques—such as crawling a site to detect dead links or scraping data for test inputs—are also recommended.

Critical thinking

A mindset of questioning the status quo is essential. Test engineers should constantly ask whether a problem has a solution, whether it can be further optimized, and maintain a skeptical, inquisitive attitude to turn pain points into innovation.

In conclusion, innovation is a means, not an end; the ultimate goal is to solve real business problems. Teams should focus on actual needs rather than chasing automation for its own sake, avoiding the trap of "automation for automation's sake".

QTest Testing Way