Testing Layers and Automated Unit Testing Practices in DevOps

In DevOps, the mainstream testing hierarchy consists of unit testing, interface testing, and UI testing, with Google’s rule suggesting 70% small, 20% medium, and 10% large tests, though the exact ratio varies by project.

Unit testing is the finest granularity, low external dependencies, and helps developers quickly locate errors to ensure code quality and exception handling.

Interface testing has lower cost than UI testing, runs in standard development environments, and offers high efficiency.

UI testing is the most intuitive but costly, with many external dependencies, making it the most difficult to implement.

Testing tasks are divided into mandatory and recommended tests. Mandatory tests cover module interfaces, local data structures, and error handling. Recommended tests include path testing, third‑party services, data‑access layer testing, and timeout testing.

Module interface testing checks data flow through the tested module.

Local data structure testing verifies type definitions, initialization, and default values.

Error handling testing ensures proper handling of errors.

Path testing validates execution paths and loops, aiming for full statement coverage.

Timeout testing checks whether production code exceeds acceptable execution time.

Data‑access layer testing validates the correctness of data‑access frameworks and SQL statements.

Third‑party testing confirms successful invocation of external services.

Automated unit testing comprises four key parts: configuration management via version control, dependency management through build tools, test frameworks for writing and batch‑executing test cases, and feedback platforms for viewing test results.

A practical example from a Java project shows unit tests, packaging, and deployment managed by Maven’s lifecycle, test cases following JUnit conventions, builds triggered by code commits or scheduled runs, and test history and coverage displayed in TFS.

The article concludes by inviting readers to follow upcoming shares on automated interface and UI testing.