1 views collected around this technical thread.
This guide walks you through setting up a FastAPI testing environment, creating a project structure, writing both unit and integration tests using pytest, httpx, and FastAPI's TestClient, and running the tests to ensure reliable, maintainable applications.
This article explains how to implement API association wrapping in Pytest, covering environment setup, test file creation, dependency imports, detailed test case definitions with sample code for login, user creation, retrieval and update, execution of the suite, result verification, and advanced project structuring for complex scenarios.
This article explains the definitions, goals, and real‑world applications of unit testing, integration testing, and system testing, illustrating each type with clear Python code examples that demonstrate how to verify functionality, interfaces, and overall system behavior in software projects.
The article details how a Java SDK for a CIM instant‑messaging system was redesigned using Java 8+ features and the Builder pattern, introduced a lightweight proxy resembling RPC frameworks with dynamic‑URL support, and added comprehensive integration tests that verify automatic client reconnection and reliable message delivery across clustered servers.
This article explores how large‑scale agile projects can effectively conduct System Integration Testing (SIT) through layered testing strategies, organized team structures, phased integration rhythms, test planning, case design, branch management, interface change handling, and evolving QA responsibilities.
The article presents a millisecond‑startup integration‑testing framework that replaces costly Spring beans and database access with a mock container and mock DAO layer, enabling tests to launch in 3‑10 seconds, use real‑world data safely, and maintain fast, isolated, high‑quality test suites.
The article explains that unit, integration, and functional testing should be fully automated and managed by CI/CD platforms to boost release confidence, avoid regressions, and prevent manual testing from slowing down deployment cycles.
The article explains Facebook’s autonomous integration testing infrastructure, detailing how it abstracts services, employs fuzzing, mock services, and record‑and‑playback techniques to enable scalable, isolated testing of backend microservices while minimizing friction and ensuring reliable software delivery.
The article examines why end‑to‑end testing strategies frequently break in practice, illustrates common pitfalls through a realistic scenario, and proposes a more reliable testing pyramid that emphasizes fast, reliable, isolated unit and integration tests while establishing quick feedback loops for developers.
This article explains what microservices are, defines microservice testing, outlines automated testing levels such as unit, contract, integration, and UI testing, and presents strategies, best practices, and tool recommendations for implementing effective automated testing in microservice architectures.
The article explains how Facebook built a stable, abstracted integration‑testing infrastructure for backend services, combining automated testing, fuzzing, record‑and‑playback, and isolation techniques to enable rapid prototyping while avoiding side effects and improving bug detection.
While end-to-end tests seem appealing by mimicking real user scenarios, they often become unreliable, slow, and costly, leading teams to miss bugs, waste time, and struggle with feedback loops; a balanced testing strategy that emphasizes fast, reliable unit and integration tests, following the test pyramid, yields better quality and faster releases.
The article explains the classic test pyramid concept, clarifies the confusing term integration testing, and details three common anti‑patterns—Ice Cream Cone, Cupcake, and Hourglass—showing why they hinder continuous testing and how teams can move toward a proper testing strategy.
Part 5 of Airbnb’s Android testing series details the custom IntegrationTestActivity architecture that drives fragment‑based screenshots and interactions, explains how idle state is detected by polling Looper queues, and describes a global exception handler that adds contextual test information to aid rapid debugging.
The article explains that the primary goal of unit, integration, and functional testing is to increase confidence in each new release, advocating fully automated test suites managed by CI/CD pipelines that run on every deployment and pull request, while discouraging manual test execution.
This article explains how to determine the right amount of testing for a software product by providing evaluation criteria, a step‑by‑step testing strategy—including recording processes, unit, integration and end‑to‑end tests—coverage types, tools, and how to incorporate field feedback for continuous improvement.
Baidu Testing Middleware is an Envoy‑based sidecar proxy that combines a data‑plane and control‑plane to intercept, inspect, modify, and route traffic, providing recording, replay, fault injection and rate‑limiting capabilities that support functional, system, integration, sandbox and chaos testing at massive scale.
The article explains various integration testing approaches—including Big Bang, Incremental, Bottom‑up, Top‑down, and Hybrid—and outlines practical best‑practice guidelines such as test ordering, separating test suites, thorough logging, and creating shared test plans for developers.
This article explains how to write integration tests for Spring services that call external APIs by using WireMock to mock HTTP responses, handle dynamic ports, simulate error and timeout scenarios, and adjust exception handling in RestTemplate calls.
This article explains how to configure the JaCoCo Maven plugin to generate separate code coverage reports for unit and integration tests, including plugin setup in the POM, execution configurations, and integration with Maven Surefire and Failsafe plugins, plus Maven commands to produce the reports.