Applying White-Box Testing in Agile Hotel Projects: Process, Cases, and Results

Background: With the acceleration of agile project cycles, testing teams face higher skill demands; the hotel testing group adopted white‑box testing to maintain quality while keeping up with release speed.

Common functional testing problems include extensive regression needs after code changes, incomplete impact analysis, urgent hot‑fixes, hidden runtime exceptions, lack of design insight, environment issues, and difficulty locating bugs.

Exploration process: Starting in 2016, the team introduced code‑review practices, gradually expanding from .NET to Java, achieving full QA participation by Q3 2017 and enabling most testers to conduct code reviews by Q4 2017.

Static code scanning was introduced later in 2017 using FindBugs and PMD, establishing scanning rules and requiring developers to resolve identified issues before committing code.

Case studies: Three typical bugs were uncovered—(1) performance‑related design flaw found via code review, (2) functional logic error detected during review, and (3) a potential null‑pointer issue revealed by static analysis—each with reproduction steps and expected outcomes.

Results: After a quarter of white‑box testing, bug detection share rose from 2.9% to 11.2% and remained stable; hidden costs dropped, testers gained deeper code understanding, and test leakage stayed at zero.

Promotion advice: Preconditions include basic coding knowledge, system architecture awareness, and access to API definitions; intervene after developers submit code for review, and apply static scanning once code stabilizes. The approach suits backend testing, especially for urgent releases, framework changes, or critical projects.