# Mocking

A software testing technique that replaces real dependencies with simulated components, or test doubles, to isolate and evaluate parts of an application.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## 🍔🧠 AWS built a fake cloud to test real code

DevFeed: [🍔🧠 AWS built a fake cloud to test real code](<https://devfeed.tech/articles/aws-built-a-fake-cloud-to-test-real-code-136057.md>)

Original publisher: [Read original article](<https://hungrymindsdev.substack.com/p/aws-built-a-fake-cloud-to-test-real>)

Author: Alexandre Zajac

Published: 2026-11-16T16:31:11Z

Content type: article

Language: en

Sources: [Hungry Minds](<https://devfeed.tech/sources/hungry-minds.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [Spec Driven Development](<https://devfeed.tech/topics/spec-driven-development.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>)

Tags: [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-teammates](<https://devfeed.tech/tags/ai-teammates.md>), [ai-trends](<https://devfeed.tech/tags/ai-trends.md>), [alex](<https://devfeed.tech/tags/alex.md>), [also](<https://devfeed.tech/tags/also.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [aws](<https://devfeed.tech/tags/aws.md>), [code](<https://devfeed.tech/tags/code.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [http](<https://devfeed.tech/tags/http.md>), [meta](<https://devfeed.tech/tags/meta.md>), [redis](<https://devfeed.tech/tags/redis.md>), [spec](<https://devfeed.tech/tags/spec.md>), [test](<https://devfeed.tech/tags/test.md>)

### AI overview

AWS Emulator uses public service API models and customer scenarios to approximate more than 200 AWS services locally. Agents build fidelity tests, check them against real AWS, then develop the emulator to pass those same tests; an SQS scenario, for example, checks whether a received message stays hidden until its visibility timeout expires. AWS reports the emulator covers more than 400 API models and runs offline, with automated merge checks that include security review agents. The approach makes local testing possible at broad service scale, but does not establish that the emulator captures every production failure. The Alf lock-service experience found different problems in simulation and on real servers, underscoring the need to validate models against reality and continue real-system testing.

### Source excerpt

PLUS: Shopify drops Redis 🫨, Meta tunes GPU kernels 🧬, and GraphQL gets an HTTP spec ⚡

## Beyond Test Cards: A Fake Payment Provider for Testing at Scale

DevFeed: [Beyond Test Cards: A Fake Payment Provider for Testing at Scale](<https://devfeed.tech/articles/beyond-test-cards-a-fake-payment-provider-for-testing-at-scale-129328.md>)

Original publisher: [Read original article](<https://eng.lyft.com/beyond-test-cards-a-fake-payment-provider-for-testing-at-scale-c69dddadb115?source=rss----25cd379abb8---4>)

Author: Jay Patel

Published: 2026-11-10T20:55:40Z

Content type: article

Language: en

Sources: [Lyft Engineering](<https://devfeed.tech/sources/lyft-engineering-medium.md>)

Topics: [Mocking](<https://devfeed.tech/topics/mocking.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [staging](<https://devfeed.tech/topics/staging.md>), [Benchmark](<https://devfeed.tech/topics/benchmark.md>)

Tags: [fake](<https://devfeed.tech/tags/fake.md>), [fallback](<https://devfeed.tech/tags/fallback.md>), [fintech](<https://devfeed.tech/tags/fintech.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [load](<https://devfeed.tech/tags/load.md>), [load-testing](<https://devfeed.tech/tags/load-testing.md>), [payment](<https://devfeed.tech/tags/payment.md>), [payments](<https://devfeed.tech/tags/payments.md>), [processor](<https://devfeed.tech/tags/processor.md>), [production](<https://devfeed.tech/tags/production.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [rideshare](<https://devfeed.tech/tags/rideshare.md>), [scale](<https://devfeed.tech/tags/scale.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [systems](<https://devfeed.tech/tags/systems.md>), [test](<https://devfeed.tech/tags/test.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tests](<https://devfeed.tech/tags/tests.md>), [third-party](<https://devfeed.tech/tags/third-party.md>)

### AI overview

Lyft's fake payment provider lets teams test payment outcomes that processor test cards cannot represent, such as a capture failing before a retry succeeds, refunds failing independently, pending responses, timeouts, and intermittent failures. It implements Lyft's shared provider interface and returns the platform's internal response format, so it exercises real payment code but not the processor-specific request, response, and error-mapping paths; those still depend on processor sandboxes, with record and replay planned. Scenarios are stored in the payment token and defined as per-action specifications, including delays, errors, and attempt-specific retry behavior. Access is fenced to simulated users through fake tokens and service checks. In staging, teams can assign scenarios to simulated riders; in production, those riders can load test payment services and exercise new workflows without real cards or charges. A resource manager maintains reusable test-user pools, with configurable fake-success defaults. The excerpt reports that load tests increased payment-service load and that scaling kept pace in the described flows. Scenarios currently live as library code across multiple

### Source excerpt

Image generated with Google Gemini, 2026 Written by Savelii Kolesnikov, Jay Patel, and Ivanna Sivak Background Lyft processes billions in payments annually, and that volume continues to grow. Agentic coding has drastically accelerated feature development, but it raises the stakes for the one phase that cannot be rushed: ensuring the highest standards of reliability and correctness in critical payment systems. Every payment platform eventually hits the same wall. Unit tests cover business rules, integration tests validate boundaries, and load tests push upstream limits, but standard testing stops the moment a request reaches a third-party processor. Processor test cards are built for simple flows: a card either passes every payment action, from authorization to capture to refund, or fails them all. Real payment flows often have one step fail while the others succeed. In this post, we'll explain why test cards break down and how we built our own fake payment provider to simulate any processor behavior on demand. Unlike a typical mock, it runs safely in production, so we can load test our payment stack and trial new workflows on simulated riders before real ones. Test cards don't get you there with rideshare Unlike paying for a product on an e-commerce website or your favorite streaming platform, Lyft, as a rideshare company, has a unique set of challenges with payments. While we can put a hold on the card on a ride request, the final charge does not always match the original hold amount on the card. We can use test cards provided by processors; however, they either succeed with all charge actions (authorization, increment, capture, direct charge, refund, etc.) or fail them all. We hit a wall if we want to test the following scenarios: A card that succeeds auth, fails capture, and then succeeds on the direct charge fallback A card that succeeds every charge flow but fails on refund A card that succeeds auth and increment, fails capture at the incremented amount, and su

## Executable but Unfaithful: Mock Object, Stub, and Assertion Generation by LLMs and Coding Agents

DevFeed: [Executable but Unfaithful: Mock Object, Stub, and Assertion Generation by LLMs and Coding Agents](<https://devfeed.tech/articles/executable-but-unfaithful-mock-object-stub-and-assertion-generation-by-llms-and-coding-agents-120788.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.14629>)

Author: Hao Ning, Jiahui Dong, Zhen Yang, Guanda Yan, Yichen Sun, Xuanyu Zhu, Zheng Shen, Yifei Pei, Jacky Keung, Jie M. Zhang

Published: 2026-11-06T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Mocking](<https://devfeed.tech/topics/mocking.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>)

Tags: [benchmark](<https://devfeed.tech/tags/benchmark.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [detection](<https://devfeed.tech/tags/detection.md>), [generation](<https://devfeed.tech/tags/generation.md>), [java](<https://devfeed.tech/tags/java.md>), [language-models](<https://devfeed.tech/tags/language-models.md>), [llms](<https://devfeed.tech/tags/llms.md>), [mock](<https://devfeed.tech/tags/mock.md>), [mocking](<https://devfeed.tech/tags/mocking.md>), [object](<https://devfeed.tech/tags/object.md>), [source-code](<https://devfeed.tech/tags/source-code.md>), [study](<https://devfeed.tech/tags/study.md>), [tasks](<https://devfeed.tech/tags/tasks.md>), [test](<https://devfeed.tech/tags/test.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

MockBench evaluates generation of mock objects, stubs, and mock assertions across 165 tasks from real-world Java and Python projects, using six LLMs and three coding agents. It measures executability, behavior fidelity, and interaction-fault detection. Coding agents substantially improve executability over LLMs, but that advantage does not consistently yield more faithful behavior or better fault detection. Analysis of 660 failures identifies ten error types and shows how generated artifacts can pass tests while still deviating from intended behavior. The abstract contrasts these approaches with capture-and-replay methods, which require recorded dependency behavior, and StubCoder, which uses predefined symbol pools.

### Source excerpt

arXiv:2610.14629v2 Announce Type: replace Abstract: Mocking is a foundational practice in unit testing, enabling developers to isolate the code under test by replacing real dependencies with simulated alternatives. Automating the generation of mock objects, stubs, and mock assertions has been a long-standing research goal. However, capture-and-replay approaches rely on recording the runtime behavior of actual dependencies. Evolutionary approaches such as StubCoder overcome this requirement but constrain generation to predefined symbol pools. Large language models (LLMs) and coding agents offer an alternative by generating mocking artifacts from source code without requiring recorded dependency executions or fixed symbol pools. Yet, no systematic study has evaluated their capabilities across all three artifact types. To address this gap, we construct MockBench, a benchmark comprising 165 mock artifact generation tasks from real-world Java and Python projects, with validated reference mock objects, stubs, and mock assertions. We evaluate six LLMs and three coding agents in terms of executability, behavior fidelity, and interaction-fault detection capability, complemented by comparisons with existing tools and sensitivity analysis. Experimental results show that LLMs and coding agents indeed have been the state-of-the-art techniques in mock-based testing. More specifically, compared with LLMs, coding agents substantially improve executability, while these gains do not consistently translate into higher behavior fidelity or better interaction-fault detection. Furthermore, we analyze 660 failures from LLMs and coding agents, and identify ten error types across the three artifact categories, revealing behavioral deviations that passing tests can conceal. Our findings highlight the challenges of mock artifact generation and provide practical guidance for both developers and researchers.

## Towards Effective Fuzzing of EDK2 Components

DevFeed: [Towards Effective Fuzzing of EDK2 Components](<https://devfeed.tech/articles/towards-effective-fuzzing-of-edk2-components-116135.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.03854>)

Author: Datta Manikanta Sri Hari Danduri, Connor Everett Glosner, Aravind Machiry

Published: 2026-11-04T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [Fuzzing/Fuzz testing](<https://devfeed.tech/topics/fuzzing.md>), [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>)

Tags: [bootloader](<https://devfeed.tech/tags/bootloader.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [drivers](<https://devfeed.tech/tags/drivers.md>), [firmware](<https://devfeed.tech/tags/firmware.md>), [framework](<https://devfeed.tech/tags/framework.md>), [fuzzing](<https://devfeed.tech/tags/fuzzing.md>), [hybrid](<https://devfeed.tech/tags/hybrid.md>), [large-language-model](<https://devfeed.tech/tags/large-language-model.md>), [llm](<https://devfeed.tech/tags/llm.md>), [protocols](<https://devfeed.tech/tags/protocols.md>), [static-analysis](<https://devfeed.tech/tags/static-analysis.md>), [tianocore](<https://devfeed.tech/tags/tianocore.md>), [uefi](<https://devfeed.tech/tags/uefi.md>), [user](<https://devfeed.tech/tags/user.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Metis fuzzes edk2 boot-time protocols by rehosting them as user-space applications and injecting inputs through both protocol interfaces and their dependencies. It uses Direct-dependency Component Rehosting to create semantically meaningful dependency mocks, with static analysis and LLM-guided synthesis to generate and refine harnesses. Implemented on HBFA, it was evaluated on 60 drivers covering 162 protocols, achieving 73.1% coverage--about 1.7 times FuzzUEr's--and finding 137 previously unknown bugs. The authors report 26 to vendors, including 12 remotely triggerable bugs; vendors acknowledged all 26 reported vulnerabilities.

### Source excerpt

arXiv:2611.03854v1 Announce Type: new Abstract: Securing bootloaders is critical to establishing the trusted computing base of modern systems. TianoCore's edk2, the de facto UEFI-based bootloader, is widely deployed but has recently been shown to contain numerous high-severity vulnerabilities. Existing approaches either focus on post-boot interfaces or rely on heavyweight simulation, limiting their scalability, throughput, and coverage of boot-time components. We present Metis, an automated technique for fuzzing edk2 protocols (i.e., boot-time interfaces) by rehosting them as user-space applications. Our key insight is that effective fuzzing must exercise not only protocol interfaces but also their dependency interactions, which serve as additional input channels. Metis employs a Direct-dependency Component Rehosting (DCR)-based strategy to construct semantically meaningful mocks for dependencies, enabling controlled input injection across all channels. It further leverages a hybrid approach combining static analysis and Large Language Model (LLM)-guided synthesis to generate and refine fuzzing harnesses. We implement Metis on the Host Based Firmware Analyzer (HBFA) framework and evaluate it on 60 drivers covering 162 protocols. Metis achieves 73.1% coverage, approximately 1.7 times higher than FuzzUEr, the state-of-the-art edk2 fuzzing technique, and discovers 137 previously unknown bugs. We have already reported 26 of them, including 12 that are remotely triggerable, and all reported vulnerabilities have been acknowledged by the vendors.

## Mocking Dependencies for Local Development

DevFeed: [Mocking Dependencies for Local Development](<https://devfeed.tech/articles/mocking-dependencies-for-local-development-107479.md>)

Original publisher: [Read original article](<https://blog.postman.com/mocking-dependencies-for-local-development/>)

Author: Talia Kohan

Published: 2026-10-29T15:00:06Z

Content type: tutorial

Language: en

Sources: [Postman](<https://devfeed.tech/sources/postman-blog.md>)

Topics: [mock api](<https://devfeed.tech/topics/mock-api.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [developer setup](<https://devfeed.tech/topics/developer-setup.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [api-discovery](<https://devfeed.tech/tags/api-discovery.md>), [api-mocking](<https://devfeed.tech/tags/api-mocking.md>), [api-testing](<https://devfeed.tech/tags/api-testing.md>), [calendar](<https://devfeed.tech/tags/calendar.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [collections](<https://devfeed.tech/tags/collections.md>), [context-graph](<https://devfeed.tech/tags/context-graph.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [development](<https://devfeed.tech/tags/development.md>), [general](<https://devfeed.tech/tags/general.md>), [local](<https://devfeed.tech/tags/local.md>), [local-development](<https://devfeed.tech/tags/local-development.md>), [mock](<https://devfeed.tech/tags/mock.md>), [mock-servers](<https://devfeed.tech/tags/mock-servers.md>), [mocking](<https://devfeed.tech/tags/mocking.md>), [postman](<https://devfeed.tech/tags/postman.md>), [repo](<https://devfeed.tech/tags/repo.md>)

### AI overview

The walkthrough shows how Postman's Context Graph and Claude Code plugin can set up local mocks across a service dependency chain. The api-discovery skill finds integrations, endpoints and schemas, including a service in another repository that a local code search would miss. The api-mocking skill creates Git-backed Local Mock Servers under `postman/mocks/`, with scenario configuration and JavaScript handlers; environment variables point each service to the mock's localhost port without gateway code changes. The api-testing skill checks responses and failure scenarios such as 401, 404 and 422. Discovery expanded the setup from five gateway integrations to seven mocks covering two additional services' call patterns. Committing the mock files and environment wiring makes the setup reproducible across clones and repositories. The article cautions that local mocks do not replace testing against real services before release.

### Source excerpt

Mock every dependency a service calls, even ones outside your repo, using Postman's Context Graph and Local Mock Servers. The post Mocking Dependencies for Local Development appeared first on Postman Blog.

## Mastering Laravel Testing: A Video Course on Laravel Tests

DevFeed: [Mastering Laravel Testing: A Video Course on Laravel Tests](<https://devfeed.tech/articles/mastering-laravel-testing-a-video-course-on-laravel-tests-101640.md>)

Original publisher: [Read original article](<https://laravel-news.com/mastering-laravel-testing-course>)

Author: Eric L. Barnes

Published: 2026-10-26T14:17:48Z

Content type: release

Language: en

Sources: [Laravel](<https://devfeed.tech/sources/laravel.md>)

Topics: [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Laravel](<https://devfeed.tech/topics/laravel.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [Livewire](<https://devfeed.tech/topics/livewire.md>)

Tags: [course](<https://devfeed.tech/tags/course.md>), [feature](<https://devfeed.tech/tags/feature.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [sponsor](<https://devfeed.tech/tags/sponsor.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tests](<https://devfeed.tech/tags/tests.md>), [video](<https://devfeed.tech/tags/video.md>)

### AI overview

Joel Clermont's Mastering Laravel Testing course teaches testing through a realistic Laravel app that starts with almost no tests, with learners applying each short lesson to their own projects. It includes 52 lessons across seven parts: 39 were available at publication and 13 were due mid-November. Topics range from feature tests, authentication, policies, forms, mocks, and validation to jobs, API resources, and Livewire. Examples use PHPUnit and, according to the article, translate to Pest. The community option adds Slack access for course questions. The excerpt lists presale prices of $149 for the course or $299 with community access, each with lifetime access and a 30-day refund guarantee; the presale deadline was November 20 at midnight Central.

### Source excerpt

Mastering Laravel Testing is a video course from Joel Clermont on feature tests, mocks, policies, and form validation. Presale pricing ends November 20. The post Mastering Laravel Testing: A Video Course on Laravel Tests appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

## Multi-tenant GPU Kubernetes on simulated hardware with Kamaji and HAMi

DevFeed: [Multi-tenant GPU Kubernetes on simulated hardware with Kamaji and HAMi](<https://devfeed.tech/articles/multi-tenant-gpu-kubernetes-on-simulated-hardware-with-kamaji-and-hami-97497.md>)

Original publisher: [Read original article](<https://www.cncf.io/blog/2026/10/23/multi-tenant-gpu-kubernetes-on-simulated-hardware-with-kamaji-and-hami/>)

Author: By Anish Bista | CNCF Golden Kubestronaut

Published: 2026-10-23T11:30:00Z

Content type: tutorial

Language: en

Sources: [Cloud Native Computing Foundation](<https://devfeed.tech/sources/cloud-native-computing-foundation.md>)

Topics: [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [Helm charts](<https://devfeed.tech/topics/helm-charts.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-cluster](<https://devfeed.tech/tags/kubernetes-cluster.md>), [team](<https://devfeed.tech/tags/team.md>), [teams](<https://devfeed.tech/tags/teams.md>)

### AI overview

A single kind management cluster hosted two Kamaji tenant control planes, each with a separate worker and HAMi mock GPUs. The mock device plugin registered GPU capacity from hand-written node annotations, enabling tests without physical GPUs. HAMi scheduled three pods requesting 20 GB and 30% compute each onto one simulated 80 GB card, while rejecting an additional pod for insufficient compute and a 90 GB request for insufficient memory. Each tenant saw only its own worker, pods and GPU capacity. The lab also verified that tenant API servers could reach HAMi's webhook through Kamaji's Konnectivity tunnel. The eight tests demonstrate wiring and scheduling decisions, not runtime GPU isolation or performance: no CUDA workloads ran, and mock allocation and lock release required manual steps. The worker setup uses kindest/node containers, while the text identifies kubeadm on real machines or Cluster API as Kamaji's supported worker route.

### Source excerpt

GPU teams usually face a bad trade-off. Give every team its own Kubernetes cluster and you pay for a control plane per team. Put everyone in one shared cluster and you get weak isolation. Either way,...

## How to Mock AWS SDK v3 in Vitest Without Extra Dependencies

DevFeed: [How to Mock AWS SDK v3 in Vitest Without Extra Dependencies](<https://devfeed.tech/articles/how-to-mock-aws-sdk-v3-in-vitest-without-extra-dependencies-92541.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-to-mock-aws-sdk-v3-in-vitest-without-extra-dependencies?source=rss>)

Author: Lucas Tonelli

Published: 2026-10-21T08:16:43Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Mocking](<https://devfeed.tech/topics/mocking.md>), [mock api](<https://devfeed.tech/topics/mock-api.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [SDK](<https://devfeed.tech/topics/sdk.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [approach](<https://devfeed.tech/tags/approach.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-sdk](<https://devfeed.tech/tags/aws-sdk.md>), [aws-sdk-client-mock](<https://devfeed.tech/tags/aws-sdk-client-mock.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [client](<https://devfeed.tech/tags/client.md>), [clients](<https://devfeed.tech/tags/clients.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [extra](<https://devfeed.tech/tags/extra.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [mock](<https://devfeed.tech/tags/mock.md>), [mocking-aws-clients](<https://devfeed.tech/tags/mocking-aws-clients.md>), [need](<https://devfeed.tech/tags/need.md>), [nodejs](<https://devfeed.tech/tags/nodejs.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [tests](<https://devfeed.tech/tags/tests.md>), [typescript-unit-testing](<https://devfeed.tech/tags/typescript-unit-testing.md>), [unit-testing](<https://devfeed.tech/tags/unit-testing.md>), [v3](<https://devfeed.tech/tags/v3.md>), [vitest-interceptors](<https://devfeed.tech/tags/vitest-interceptors.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The excerpt shows how to mock AWS SDK v3 clients using Vitest without an extra mocking package: replace a service client's constructor with a fake that exposes a `send` method backed by `vi.fn()`, while retaining the SDK's real exports so commands remain genuine. Put the `vi.mock` setup in Vitest `setupFiles` when clients are constructed at module scope. Tests can queue responses with one shot resolved or rejected values, or use service specific helpers for defaults and overrides, then assert both request input and command class. Reset the send mock between tests, using Vitest cleanup settings where suitable. Give each AWS service its own mock to avoid response collisions. The excerpt describes `aws-sdk-client-mock` as offering a compact command oriented API, while requiring its own mock/reset approach and extra matchers for command assertions.

### Source excerpt

You need to mock AWS SDK clients in your tests, but the traditional approach with aws-sdk-client-mock requires special treatment and can be cumbersome.

## Testing AI-Generated Code: Lint the Pattern, Test the Decision

DevFeed: [Testing AI-Generated Code: Lint the Pattern, Test the Decision](<https://devfeed.tech/articles/testing-ai-generated-code-lint-the-pattern-test-the-decision-92573.md>)

Original publisher: [Read original article](<https://www.robinwieruch.de/testing-ai-generated-code/>)

Author: Robin Wieruch

Published: 2026-10-21T06:50:46Z

Content type: article

Language: en

Sources: [Robin Wieruch](<https://devfeed.tech/sources/robin-wieruch.md>)

Topics: [Unit testing](<https://devfeed.tech/topics/unit-testing.md>), [lint](<https://devfeed.tech/topics/lint.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [coding patterns](<https://devfeed.tech/topics/coding-patterns.md>)

Tags: [agentic-engineering](<https://devfeed.tech/tags/agentic-engineering.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-engineer](<https://devfeed.tech/tags/ai-engineer.md>), [ai-generated-tests](<https://devfeed.tech/tags/ai-generated-tests.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [lint](<https://devfeed.tech/tags/lint.md>), [lint-rules-for-ai-agents](<https://devfeed.tech/tags/lint-rules-for-ai-agents.md>), [pattern](<https://devfeed.tech/tags/pattern.md>), [software-factory](<https://devfeed.tech/tags/software-factory.md>), [test](<https://devfeed.tech/tags/test.md>), [testing](<https://devfeed.tech/tags/testing.md>), [testing-ai-generated-code](<https://devfeed.tech/tags/testing-ai-generated-code.md>)

### AI overview

The article's approach is to enforce each file type's documented skeleton with lint, centralize test setup in a shared harness, and test only files that make decisions beyond that pattern. For handlers, lint checks session-first ordering, service calls inside try/catch, error mapping, and safe input flow; it covers every handler and makes tests for those invariants redundant. A shared harness fakes external effects and uses the real generated backend client over an in-memory transport, with safeguards for unserved methods, fake crashes, and production request limits. Tests focus on requests, results, side effects, branches, security choices, and failure behavior. The approach also applies to forms and comboboxes, while some file types need no harness or individual tests. It targets useful unit and integration coverage, not a fully tested codebase; end-to-end testing is outside the article's scope.

### Source excerpt

Testing AI-generated code without the noise: lint the patterns coding agents follow, share one test harness, and add tests only where a file leaves its pattern.

## An honest review of Matt Pocock's Skills framework

DevFeed: [An honest review of Matt Pocock's Skills framework](<https://devfeed.tech/articles/an-honest-review-of-matt-pocock-s-skills-framework-90821.md>)

Original publisher: [Read original article](<https://blog.scottlogic.com/2026/10/19/an-honest-review-of-matt-pococks-skills.html>)

Author: Colin Eberhardt

Published: 2026-10-19T00:00:00Z

Content type: opinion

Language: en

Sources: [Scott Logic](<https://devfeed.tech/sources/scott-logic.md>)

Topics: [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-skills](<https://devfeed.tech/tags/agent-skills.md>), [app](<https://devfeed.tech/tags/app.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [but](<https://devfeed.tech/tags/but.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [framework](<https://devfeed.tech/tags/framework.md>), [i](<https://devfeed.tech/tags/i.md>), [popular](<https://devfeed.tech/tags/popular.md>), [practices](<https://devfeed.tech/tags/practices.md>), [promote](<https://devfeed.tech/tags/promote.md>), [review](<https://devfeed.tech/tags/review.md>), [rituals](<https://devfeed.tech/tags/rituals.md>), [simple](<https://devfeed.tech/tags/simple.md>), [skills](<https://devfeed.tech/tags/skills.md>), [software](<https://devfeed.tech/tags/software.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [sound](<https://devfeed.tech/tags/sound.md>), [test](<https://devfeed.tech/tags/test.md>), [times](<https://devfeed.tech/tags/times.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Matt Pocock's Skills framework is lightweight, adaptable and composable, and the author found its iterative implementation and code-review loop useful when rebuilding a modest KartLog app. Grilling produced useful project context and an architecture decision; the implementation loop caught bugs against both project standards and the specification. But the specification's repetitive user stories and tests that repeatedly covered a small shared adapter felt more like process rituals than sound engineering judgment. The `/wizard` setup script also failed when Supabase's interface differed from its assumptions, with no way to recover within the script. The author's mixed verdict is that the Skills teach and support disciplined engineering, but need tailoring and human judgment; the experiment was a greenfield app, and the Skills were not adapted.

### Source excerpt

I put Matt Pocock's popular agent Skills framework to the test by rebuilding a real app from scratch, with decidedly mixed results. The Skills are refreshingly simple and promote sound engineering practices, but at times they simulate the rituals of software engineering without the judgement that makes them valuable.

## Mailbox for Laravel: Preview and Test Rendered Email

DevFeed: [Mailbox for Laravel: Preview and Test Rendered Email](<https://devfeed.tech/articles/mailbox-for-laravel-preview-and-test-rendered-email-62431.md>)

Original publisher: [Read original article](<https://laravel-news.com/mailbox-for-laravel>)

Author: Yannick Lyn Fatt

Published: 2026-09-30T02:43:35Z

Content type: tutorial

Language: en

Sources: [Laravel](<https://devfeed.tech/sources/laravel.md>)

Topics: [Laravel](<https://devfeed.tech/topics/laravel.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [articles](<https://devfeed.tech/tags/articles.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [database](<https://devfeed.tech/tags/database.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [laravel-packages](<https://devfeed.tech/tags/laravel-packages.md>), [test](<https://devfeed.tech/tags/test.md>)

### AI overview

Mailbox for Laravel captures outgoing mail in a local inbox and provides assertions for testing rendered messages, including HTML, recipients, and attachments. The article describes installation, storage and delivery options, staging access controls, and message retention settings.

### Source excerpt

Mailbox for Laravel captures outgoing mail in a local dashboard and lets you test rendered HTML, recipients, and attachments with fluent assertions. The post Mailbox for Laravel: Preview and Test Rendered Email appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

## API Mocking and Testing With Microcks

DevFeed: [API Mocking and Testing With Microcks](<https://devfeed.tech/articles/api-mocking-and-testing-with-microcks-4497.md>)

Original publisher: [Read original article](<https://www.baeldung.com/java-microks-api-mocking-testing>)

Author: Andrei Branza

Published: 2026-08-22T23:20:24Z

Content type: tutorial

Language: en

Sources: [Baeldung](<https://devfeed.tech/sources/baeldung.md>)

Topics: [Mocking](<https://devfeed.tech/topics/mocking.md>), [Testcontainers](<https://devfeed.tech/topics/testcontainers.md>), [API](<https://devfeed.tech/topics/api.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [Microservices](<https://devfeed.tech/topics/microservices.md>), [Docker Compose](<https://devfeed.tech/topics/docker-compose.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [Amazon Simple Queue Service (SQS)](<https://devfeed.tech/topics/amazon-simple-queue-service-sqs.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [gRPC](<https://devfeed.tech/topics/grpc.md>), [Jenkins](<https://devfeed.tech/topics/jenkins.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [compose](<https://devfeed.tech/tags/compose.md>), [docker](<https://devfeed.tech/tags/docker.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [mocking](<https://devfeed.tech/tags/mocking.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [popular](<https://devfeed.tech/tags/popular.md>), [testcontainers](<https://devfeed.tech/tags/testcontainers.md>), [testing](<https://devfeed.tech/tags/testing.md>), [testing-popular-testcontainers](<https://devfeed.tech/tags/testing-popular-testcontainers.md>)

### AI overview

This tutorial explains how to use Microcks with Testcontainers to generate API mocks from contracts and run conformance tests against real implementations. It covers importing an OpenAPI contract, starting Microcks in a JUnit 5 test, calling generated mock endpoints, and integrating mocking and testing into delivery workflows.

### Source excerpt

Learn how to use Testcontainers integration to spin up Microcks inside a JUnit5 test. The post API Mocking and Testing With Microcks first appeared on Baeldung.

## How to test agent skills without hitting real APIs

DevFeed: [How to test agent skills without hitting real APIs](<https://devfeed.tech/articles/how-to-test-agent-skills-without-hitting-real-apis-23831.md>)

Original publisher: [Read original article](<https://devblogs.microsoft.com/blog/how-to-test-agent-skills-without-hitting-real-apis/>)

Author: Waldek Mastykarz

Published: 2026-07-17T09:27:50Z

Content type: article

Language: en

Sources: [Developer Blogs](<https://devfeed.tech/sources/developer-blogs.md>)

Topics: [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [mock api](<https://devfeed.tech/topics/mock-api.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-experience](<https://devfeed.tech/tags/agent-experience.md>), [agent-skill](<https://devfeed.tech/tags/agent-skill.md>), [agent-skills](<https://devfeed.tech/tags/agent-skills.md>), [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [ax](<https://devfeed.tech/tags/ax.md>), [costs](<https://devfeed.tech/tags/costs.md>), [data](<https://devfeed.tech/tags/data.md>), [developers](<https://devfeed.tech/tags/developers.md>), [effect](<https://devfeed.tech/tags/effect.md>), [evals](<https://devfeed.tech/tags/evals.md>), [for-developers](<https://devfeed.tech/tags/for-developers.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [learn-how-to](<https://devfeed.tech/tags/learn-how-to.md>), [microsoft-for-developers](<https://devfeed.tech/tags/microsoft-for-developers.md>), [mock](<https://devfeed.tech/tags/mock.md>), [money](<https://devfeed.tech/tags/money.md>), [production](<https://devfeed.tech/tags/production.md>), [run](<https://devfeed.tech/tags/run.md>), [skills](<https://devfeed.tech/tags/skills.md>), [test](<https://devfeed.tech/tags/test.md>)

### AI overview

Evaluating API-calling agent skills against real services can incur call costs, mutate live data, and produce inconsistent results when outside changes affect shared state. The excerpt contrasts manually maintained mock servers, which need realistic endpoint behavior and can drift from the API, with Dev Proxy, configured through JSON to intercept the skill's unchanged real URLs and return seeded local data with relevant HTTP semantics. Its data resets between runs, avoiding production writes and API costs. The excerpt presents proxy emulation as a lighter option, while noting the choice depends on the situation; it does not cover the full setup.

### Source excerpt

Your agent skill calls an API. The moment you start evaluating it, every run either costs money or mutates production data. Learn how to mock APIs transparently so you can run evals without changing your skill or hitting real endpoints. The post How to test agent skills without hitting real APIs appeared first on Microsoft for Developers.

## How AI-Assisted Development Uses Reviewed Design Documents and Extensive Testing

DevFeed: [How AI-Assisted Development Uses Reviewed Design Documents and Extensive Testing](<https://devfeed.tech/articles/i-stopped-writing-code-and-started-doing-this-32369.md>)

Original publisher: [Read original article](<https://brianjenney.substack.com/p/i-stopped-writing-code-and-started>)

Author: Brian Jenney

Published: 2026-05-30T17:42:50Z

Content type: article

Language: en

Sources: [Brian Jenney](<https://devfeed.tech/sources/brian-jenney.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Code](<https://devfeed.tech/topics/code.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>), [GitHub API](<https://devfeed.tech/topics/github-api.md>), [Figma](<https://devfeed.tech/topics/figma.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [boilerplate](<https://devfeed.tech/tags/boilerplate.md>), [code](<https://devfeed.tech/tags/code.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [figma](<https://devfeed.tech/tags/figma.md>), [github](<https://devfeed.tech/tags/github.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [mocking](<https://devfeed.tech/tags/mocking.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The author describes an AI-assisted development workflow in which reviewed, versioned design documents provide context for coding agents. Agents handle implementation and testing boilerplate, while developers decide expected behavior and test coverage. The author connects this process with frequent deployments and confidence in changes.

### Source excerpt

AI writes basically all of my code now.

## How to use Jest mocks

DevFeed: [How to use Jest mocks](<https://devfeed.tech/articles/how-to-use-jest-mocks-38398.md>)

Original publisher: [Read original article](<https://blog.danlew.net/2026/05/28/how-to-use-jest-mocks/>)

Author: Dan Lew

Published: 2026-05-28T13:10:16Z

Content type: tutorial

Language: en

Sources: [Dan Lew Blog](<https://devfeed.tech/sources/dan-lew-blog.md>)

Topics: [Jest](<https://devfeed.tech/topics/jest.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Dependency injection](<https://devfeed.tech/topics/dependency-injection.md>)

Tags: [dependency-injection](<https://devfeed.tech/tags/dependency-injection.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [jest](<https://devfeed.tech/tags/jest.md>), [mocking](<https://devfeed.tech/tags/mocking.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

A practical introduction to Jest mocks covering module mocking, mock hoisting, automock behavior, and configuring mocked return values. It also notes limitations in the documentation and discusses considerations for TypeScript users.

### Source excerpt

For better or worse, my life has become infested by Jest mocks. I come from the land of dependency injection (I even gave a talk once!), but whenever I talk about dependency injection to JavaScript developers I get this reaction: Instead, mocking is king. Unfortunately, I've found Jests&

## Practicing Playwright: API Testing, Intercepting Network Requests, and Mocking APIs

DevFeed: [Practicing Playwright: API Testing, Intercepting Network Requests, and Mocking APIs](<https://devfeed.tech/articles/practicing-playwright-api-testing-intercepting-network-requests-and-mocking-apis-22405.md>)

Original publisher: [Read original article](<https://www.tjmaher.com/2026/05/practicing-playwright-api-testing.html>)

Author: T.J. Maher (noreply@blogger.com)

Published: 2026-05-28T02:20:30Z

Content type: tutorial

Language: en

Sources: [T.J. Maher](<https://devfeed.tech/sources/t-j-maher.md>)

Topics: [Playwright](<https://devfeed.tech/topics/playwright.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [API](<https://devfeed.tech/topics/api.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [Network](<https://devfeed.tech/topics/network.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [api-testing](<https://devfeed.tech/tags/api-testing.md>), [browser](<https://devfeed.tech/tags/browser.md>), [guide](<https://devfeed.tech/tags/guide.md>), [mocking](<https://devfeed.tech/tags/mocking.md>), [network](<https://devfeed.tech/tags/network.md>), [playwright](<https://devfeed.tech/tags/playwright.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

A practical tutorial on Playwright API testing using page.route to intercept, modify, abort, fetch, and mock network requests. It examines tests for the PracticeSoftwareTesting.com shopping cart and shows how API data can support UI assertions.

### Source excerpt

How would you intercept a network request and use the data for assertions? Mock a network request using those assertions? And make sure that all data is loaded in the UI before making your assertions, and that all tests can pass when run? We will be walking through Butch Mayhew's code that answers all of these questions, part of his LinkedIn Learning course: Playwright Essential Training. We will be examining the shopping cart test site PracticeSoftwareTesting.com and looking at code on Butch's companion GitHub site on how to mock out the API and use them in the UI tests. Playwright has a lot of features when it comes to API testing. You can intercept network requests, aborting, modifying, and mocking network requests. You can also simulate a slow network. This is all done through the Playwright methods: page.route. A route is the specific path or URL a client uses to request data or trigger a function on a server. GET /product would be an API call that gets everything from the address string called products, which then retrieves all products from the API endpoint called "products". The endpoint is "products" and the route is the name that accesses the endpoint. The Playwright API has a method called route, which allows Playwright to monitor and modify browser network traffic. Playwright.dev / Docs / Network: https://playwright.dev/docs/network Playwright and page.route: https://playwright.dev/docs/api/class-route Playwright Mocking API Guide: https://playwright.dev/docs/mock Adding page.route to your test allows you to do things such as: abort the route request with route.abort(), simulating various error codes such as accessdenied, addressunreachable, blockedbyclient, blockedbyresponse, connection aborted, connectionclosed, timedout, etc. continue sending the route's request with optional overrides such as changing the request URL, the headers, the method such as GET or POST, and the post data of the request. fetch the request without yet fulfilling it, so the res

## Lessons from Software Engineering at Google for Maintaining Healthy Codebases

DevFeed: [Lessons from Software Engineering at Google for Maintaining Healthy Codebases](<https://devfeed.tech/articles/what-i-learned-from-the-book-software-engineering-at-google-38697.md>)

Original publisher: [Read original article](<https://newsletter.techworld-with-milan.com/p/what-i-learned-at-swe-at-google-book>)

Author: Dr Milan Milanović

Published: 2026-02-26T16:01:23Z

Content type: opinion

Language: en

Sources: [Tech World With Milan Newsletter](<https://devfeed.tech/sources/tech-world-with-milan-newsletter.md>)

Topics: [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Dependency management](<https://devfeed.tech/topics/dependency-management.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [Refactoring](<https://devfeed.tech/topics/refactoring.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [releases](<https://devfeed.tech/topics/releases.md>), [upgrade](<https://devfeed.tech/topics/upgrade.md>)

Tags: [code-review](<https://devfeed.tech/tags/code-review.md>), [dependency-management](<https://devfeed.tech/tags/dependency-management.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [leadership](<https://devfeed.tech/tags/leadership.md>), [mocking](<https://devfeed.tech/tags/mocking.md>), [release](<https://devfeed.tech/tags/release.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

A review of Software Engineering at Google argues that the book's lessons apply to teams of different sizes. It highlights practices for evolving, sharing, testing, releasing, and eventually deleting code, along with code review, dependency management, productivity measurement, and engineering culture.

### Source excerpt

And what you can apply from today.

## Stop Mocking Auth (It's Breaking Your Tests)

DevFeed: [Stop Mocking Auth (It's Breaking Your Tests)](<https://devfeed.tech/articles/stop-mocking-auth-it-s-breaking-your-tests-5803.md>)

Original publisher: [Read original article](<https://neon.com/blog/stop-mocking-auth-its-breaking-your-tests>)

Author: Shridhar Deshmukh

Published: 2025-12-29T18:23:12Z

Content type: article

Language: en

Sources: [Neon Docs](<https://devfeed.tech/sources/blog-neon-docs.md>)

Topics: [Mocking](<https://devfeed.tech/topics/mocking.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [passwords](<https://devfeed.tech/topics/passwords.md>), [Database](<https://devfeed.tech/topics/database.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [mocking](<https://devfeed.tech/tags/mocking.md>), [password](<https://devfeed.tech/tags/password.md>), [product](<https://devfeed.tech/tags/product.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The article argues that mocking authentication makes test suites misleading because mocks can bypass password verification, session management, database constraints, and relationships between authentication and application data. It recommends testing the behavior that can fail in production rather than only verifying mocked assumptions.

### Source excerpt

If your application has user accounts, authentication touches everything: who can access what, what data belongs to whom, and how your system behaves when sessions expire or credentials are invalid. Auth is also one of the most commonly mocked components in test suites. The reaso...

## Evaluating search query relevance with judgment lists

DevFeed: [Evaluating search query relevance with judgment lists](<https://devfeed.tech/articles/evaluating-search-query-relevance-with-judgment-lists-78855.md>)

Original publisher: [Read original article](<https://www.elastic.co/search-labs/blog/judgment-lists-search-query-relevance-elasticsearch>)

Author: Jhon Guzmán

Published: 2025-12-11T00:00:00Z

Content type: tutorial

Language: en

Sources: [Elasticsearch Labs](<https://devfeed.tech/sources/elasticsearch-labs.md>)

Topics: [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [search-engines](<https://devfeed.tech/topics/search-engines.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [Search engine optimization (SEO)](<https://devfeed.tech/topics/seo.md>)

Tags: [a-b-testing](<https://devfeed.tech/tags/a-b-testing.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [inside-elastic](<https://devfeed.tech/tags/inside-elastic.md>), [performance](<https://devfeed.tech/tags/performance.md>), [performance-metrics](<https://devfeed.tech/tags/performance-metrics.md>), [relevance](<https://devfeed.tech/tags/relevance.md>), [search](<https://devfeed.tech/tags/search.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The article explains how judgment lists can provide a repeatable way to evaluate Elasticsearch search queries. It describes binary and graded relevance ratings, explicit, implicit, and AI-generated judgments, and metrics such as precision, recall, DCG, and MRR. A movie-search example uses the Ranking Evaluation API to show how changing minimum_should_match affects recall, while noting that recall gains can involve trade-offs. It recommends starting with a small set of important queries, validating results with users, and integrating evaluations into development pipelines.

### Source excerpt

Explore how to build judgment lists to objectively evaluate search query relevance and improve performance metrics such as recall, for scalable search testing in Elasticsearch.

## A Reproducible Process for Fixing Bugs

DevFeed: [A Reproducible Process for Fixing Bugs](<https://devfeed.tech/articles/how-to-fix-any-bug-36173.md>)

Original publisher: [Read original article](<https://overreacted.io/how-to-fix-any-bug/>)

Published: 2025-10-21T00:00:00Z

Content type: tutorial

Language: en

Sources: [Dan Abramov](<https://devfeed.tech/sources/dan-abramov.md>)

Topics: [bug](<https://devfeed.tech/topics/bug.md>), [React Router](<https://devfeed.tech/topics/react-router.md>), [React](<https://devfeed.tech/topics/react.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [browser](<https://devfeed.tech/topics/browser.md>)

Tags: [bug](<https://devfeed.tech/tags/bug.md>), [claude](<https://devfeed.tech/tags/claude.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [mocking](<https://devfeed.tech/tags/mocking.md>), [react](<https://devfeed.tech/tags/react.md>), [react-router](<https://devfeed.tech/tags/react-router.md>)

### AI overview

The article describes debugging a web app where adding a React Router server call caused scrolling to jitter. It argues that reliable reproductions are essential because Claude and human engineers can propose incorrect fixes without a reproducible test.

### Source excerpt

The joys of vibecoding.

## Quarkus - a component testing update

DevFeed: [Quarkus - a component testing update](<https://devfeed.tech/articles/quarkus-a-component-testing-update-43868.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-component-test-update/>)

Author: Martin Kouba (https://twitter.com/martunek)

Published: 2025-10-20T00:00:00Z

Content type: tutorial

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Dependency injection](<https://devfeed.tech/topics/dependency-injection.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>)

Tags: [dependency-injection](<https://devfeed.tech/tags/dependency-injection.md>), [mocking](<https://devfeed.tech/tags/mocking.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

This tutorial updates Quarkus component testing. It explains how the experimental JUnit 5 extension starts only the CDI container and Configuration service, supports lifecycle choices, and automatically mocks unsatisfied dependencies.

### Source excerpt

It's been a while since we introduced the component testing in Quarkus. In this blogpost, we will first quickly summarize the basic principles and then describe some of the new interesting features. Quick summary First, just a quick summary. The component model of Quarkus is built on top of CDI. An idiomatic way to test a Quarkus application is to use the quarkus-junit5 module and @QuarkusTest. However, in this case, a full Quarkus application needs to be built and started. In order to avoid unnecessary rebuilds and restarts the application is shared for multiple tests, unless a different test profile is used. One of the consequences is that some components (typically @ApplicationScoped and @Singleton CDI beans) are shared as well. What if you need to test the business logic of a component in isolation, with different states and inputs? For this use case, a plain unit test would make a lot of sense. However, writing unit tests for CDI beans without a running CDI container is often a tedious work. Dependency injection, events, interceptors - all the work has to be done manually and everything needs to be wired together by hand. In Quarkus 3.2, we introduced an experimental feature to ease the testing of CDI components and mocking of their dependencies. It's a JUnit 5 extension that does not start a full Quarkus application but merely the CDI container and the Configuration service. The lifecycle So when exactly does the QuarkusComponentTest start the CDI container? It depends on the value of @org.junit.jupiter.api.TestInstance#lifecycle. If the test instance lifecycle is Lifecycle#PER_METHOD (default) then the container is started during the before each test phase and stopped during the after each test phase. If the test instance lifecycle is Lifecycle#PER_CLASS` then the container is started during the before all test phase and stopped during the after all test phase. Components under test When writing a component test, it's essential to understand how the set of te

## Android App End-to-End Testing With FusionAuth

DevFeed: [Android App End-to-End Testing With FusionAuth](<https://devfeed.tech/articles/android-app-end-to-end-testing-with-fusionauth-43159.md>)

Original publisher: [Read original article](<https://fusionauth.io/blog/android-end-to-end-testing>)

Author: Aaron Ritter, Michael Roth

Published: 2025-08-20T00:00:00Z

Content type: tutorial

Language: en

Sources: [FusionAuth](<https://devfeed.tech/sources/fusionauth-blog.md>)

Topics: [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [LineageOS](<https://devfeed.tech/topics/lineageos.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [automated](<https://devfeed.tech/tags/automated.md>), [backend](<https://devfeed.tech/tags/backend.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [mocking](<https://devfeed.tech/tags/mocking.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [security](<https://devfeed.tech/tags/security.md>), [test](<https://devfeed.tech/tags/test.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>)

### AI overview

A tutorial on automating end-to-end tests for an Android Kotlin application that uses FusionAuth for OAuth2 authentication. It covers testing against a real FusionAuth backend, validating SDK functionality across Android versions and releases, and the limitations of mocking authentication flows.

### Source excerpt

How to end-to-end test an Android App including FusionAuth.

## Understanding Mocks, Stubs, Fakes, and Shunts in Test-Driven Development

DevFeed: [Understanding Mocks, Stubs, Fakes, and Shunts in Test-Driven Development](<https://devfeed.tech/articles/tdd-mocks-fakes-stubs-doubles-shunts-ayayay-28436.md>)

Original publisher: [Read original article](<https://craftingtechteams.substack.com/p/tdd-mocks-fakes-stubs-doubles-shunts>)

Author: Denis Čahuk

Published: 2025-07-21T08:05:36Z

Content type: article

Language: en

Sources: [Crafting Tech Teams](<https://devfeed.tech/sources/crafting-tech-teams.md>)

Topics: [Mocking](<https://devfeed.tech/topics/mocking.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>)

Tags: [mocking](<https://devfeed.tech/tags/mocking.md>), [tdd](<https://devfeed.tech/tags/tdd.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tests](<https://devfeed.tech/tags/tests.md>), [video](<https://devfeed.tech/tags/video.md>)

### AI overview

A recording from Denis Čahuk's live video explains the differences between mocks, stubs, fakes, and shunts, and examines how overusing or misunderstanding test doubles can create tangled tests. It discusses testing outgoing commands with mocks and how difficult mocking setups may indicate design problems.

### Source excerpt

A recording from Denis Čahuk's live video

## How Mocking Affects Software Design and Testability

DevFeed: [How Mocking Affects Software Design and Testability](<https://devfeed.tech/articles/every-mock-is-a-bet-against-your-design-28430.md>)

Original publisher: [Read original article](<https://craftingtechteams.substack.com/p/recording-every-mock-is-a-bet-against>)

Author: Denis Čahuk

Published: 2025-07-19T07:45:14Z

Content type: tutorial

Language: en

Sources: [Crafting Tech Teams](<https://devfeed.tech/sources/crafting-tech-teams.md>)

Topics: [Mocking](<https://devfeed.tech/topics/mocking.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Refactoring](<https://devfeed.tech/topics/refactoring.md>), [test-coverage](<https://devfeed.tech/topics/test-coverage.md>)

Tags: [coverage](<https://devfeed.tech/tags/coverage.md>), [mocking](<https://devfeed.tech/tags/mocking.md>), [mongodb](<https://devfeed.tech/tags/mongodb.md>), [refactoring](<https://devfeed.tech/tags/refactoring.md>), [tdd](<https://devfeed.tech/tags/tdd.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

A recorded talk examines when mocks are useful, common misconceptions about mocking and TDD, and how excessive or poorly chosen mocks can constrain software design and testability. It discusses multi-mock tests, database mocking, and designing narrow seams around dependencies.

### Source excerpt

If you've ever felt like your tests get in the way of refactoring, or like mocks make everything harder rather than simpler this stream is for you.

[Next page](<https://devfeed.tech/topics/mocking.md?cursor=WyIyMDI1LTA3LTE5VDA3OjQ1OjE0KzAwOjAwIiwgIjcyMDMxOWY3LWYwZGMtNDRmNC1hODU4LTNhZjRmOGNkYjhlOSJd>)