# Integration testing

Integration testing is a software-testing approach that combines application components or modules and evaluates how well they work together.

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

## How to Perform eSIM Testing: Steps, Scenarios, and Automation Approach

DevFeed: [How to Perform eSIM Testing: Steps, Scenarios, and Automation Approach](<https://devfeed.tech/articles/how-to-perform-esim-testing-steps-scenarios-and-automation-approach-146866.md>)

Original publisher: [Read original article](<https://testgrid.io/blog/esim-testing/>)

Author: Sanjaykumar Ghinaiya

Published: 2026-11-20T13:29:09Z

Content type: tutorial

Language: en

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

Topics: [Mobile Testing](<https://devfeed.tech/topics/mobile-testing.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [approach](<https://devfeed.tech/tags/approach.md>), [automation](<https://devfeed.tech/tags/automation.md>), [esim](<https://devfeed.tech/tags/esim.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [mobile-app-testing](<https://devfeed.tech/tags/mobile-app-testing.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

eSIM testing must verify the full path from profile provisioning through network registration and usable services: successful installation alone does not ensure data, SMS, or voice will work. The guide recommends covering profile download and integrity, lifecycle state changes, activation and recovery, security and authorization, connectivity, roaming, and device compatibility. Its workflow is to define supported devices, operators, and consumer (SGP.22) or IoT (SGP.32) architecture; prepare physical devices, authorized profiles, and diagnostics; provision and activate; run functional, network, and end-to-end checks; then analyze logs and traces. Real-device coverage, standardized configurations, detailed diagnostics, and repeatable regression automation can improve scale and reproducibility. Automation depends on exposed device, app, API, operator, and provisioning controls; some carrier- or device-controlled operations may need specialized access or manual validation. Functional testing is distinct from formal GSMA conformance testing.

### Source excerpt

What happens when an eSIM profile installs successfully, but the device still cannot register on the right network or establish the services the subscriber expects? That's why eSIM testing has to cover more than the activation screen. You need to validate profile provisioning and management, device behavior, network registration, connectivity, recovery, and the application experience [...]

## 7 Ways AI Agents Fail in Production (and How to Catch Each One)

DevFeed: [7 Ways AI Agents Fail in Production (and How to Catch Each One)](<https://devfeed.tech/articles/7-ways-ai-agents-fail-in-production-and-how-to-catch-each-one-146247.md>)

Original publisher: [Read original article](<https://machinelearningmastery.com/7-ways-ai-agents-fail-in-production-and-how-to-catch-each-one/>)

Author: Nahla Davies

Published: 2026-11-20T11:00:00Z

Content type: article

Language: en

Sources: [MachineLearningMastery.com](<https://devfeed.tech/sources/machinelearningmastery-com.md>)

Topics: [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [ReAct agent Python](<https://devfeed.tech/topics/react-agent-python.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [Chaos Engineering](<https://devfeed.tech/topics/chaos-engineering.md>), [Exception handling](<https://devfeed.tech/topics/exception-handling.md>), [long-running](<https://devfeed.tech/topics/long-running.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [agent-evaluation](<https://devfeed.tech/tags/agent-evaluation.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [fail](<https://devfeed.tech/tags/fail.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [production](<https://devfeed.tech/tags/production.md>)

### AI overview

A green tool response does not prove an agent completed its task; verify outcomes in resulting state and external records. The excerpt proposes seven regression checks: strictly validate tool arguments; compare extracted fields and source versions with confirmed ground truth; test whether injected document instructions are proposed and ensure they never execute; deny unauthorized cross-tenant or unapproved actions and assert stored data stays unchanged; retry with a stable operation ID and deduplicate matching requests; restart from persistent checkpoints and assert completion only when an authorized receipt exists; and stop repeated actions when progress stalls, using separate limits for calls, time, spend, and graph execution. Correlate run events under one ID, distinguish proposed, denied, waiting, and complete states, and pair each failing fixture with a passing control. The excerpt notes limits: confidence scores and citations do not establish correctness, in-memory checkpoints are lost on restart, and a timeout may leave an action's outcome unknown.

### Source excerpt

Three events that look alike need separate names.

## How I Traced a Missing Vercel AI SDK Duration Histogram

DevFeed: [How I Traced a Missing Vercel AI SDK Duration Histogram](<https://devfeed.tech/articles/how-i-traced-a-missing-vercel-ai-sdk-duration-histogram-146215.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-i-traced-a-missing-vercel-ai-sdk-duration-histogram?source=rss>)

Author: Aditya Reddy

Published: 2026-11-20T10:15:02Z

Content type: tutorial

Language: en

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

Topics: [vercel ai sdk](<https://devfeed.tech/topics/vercel-ai-sdk.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [SDK](<https://devfeed.tech/topics/sdk.md>)

Tags: [ai-observability](<https://devfeed.tech/tags/ai-observability.md>), [ai-sdk-telemetry](<https://devfeed.tech/tags/ai-sdk-telemetry.md>), [distributed-tracing](<https://devfeed.tech/tags/distributed-tracing.md>), [failures](<https://devfeed.tech/tags/failures.md>), [generation](<https://devfeed.tech/tags/generation.md>), [inference](<https://devfeed.tech/tags/inference.md>), [llm-observability](<https://devfeed.tech/tags/llm-observability.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [performance-monitoring](<https://devfeed.tech/tags/performance-monitoring.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [vercel](<https://devfeed.tech/tags/vercel.md>), [vercel-ai-sdk](<https://devfeed.tech/tags/vercel-ai-sdk.md>)

### AI overview

In the author's controlled comparison, `@ai-sdk/otel` 1.0.157 exported no inference duration histogram, while 1.0.160 recorded 25 observations across generation, streaming, and five thrown errors. A span's `gen_ai.client.operation.duration` attribute did not itself produce a metric: tracing and metrics use separate provider paths, and the histogram requires a `MeterProvider`, reader, and exporter. The author checked the in-memory export against a control counter, flushed after each sequential mock call, and derived per-call durations from cumulative sums. For a stream, the histogram measured the full invocation (median 202.3 ms), while first text arrived at a median 43.6 ms; these are distinct timings. Counts represent model attempts, retries may add attempts, and local tool execution is outside the duration. The comparison used pinned package versions and mock calls; it does not establish behavior for every real service or backend.

### Source excerpt

I ran 25 mock calls per version to see how the Vercel AI SDK records generation, streaming and failures in its OpenTelemetry inference histogram.

## How to aggregate test results across teams with Temporal Nexus

DevFeed: [How to aggregate test results across teams with Temporal Nexus](<https://devfeed.tech/articles/how-to-aggregate-test-results-across-teams-with-temporal-nexus-146865.md>)

Original publisher: [Read original article](<https://temporal.io/blog/how-to-aggregate-test-results-across-teams-with-temporal-nexus>)

Author: Brooks Newberry

Published: 2026-11-20T00:00:00Z

Content type: article

Language: en

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

Topics: [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [Remote Procedure Call (RPC)](<https://devfeed.tech/topics/rpc.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>)

Tags: [aggregate](<https://devfeed.tech/tags/aggregate.md>), [collect](<https://devfeed.tech/tags/collect.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [format](<https://devfeed.tech/tags/format.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [nexus](<https://devfeed.tech/tags/nexus.md>), [release](<https://devfeed.tech/tags/release.md>), [release-engineering](<https://devfeed.tech/tags/release-engineering.md>), [report](<https://devfeed.tech/tags/report.md>), [results](<https://devfeed.tech/tags/results.md>), [teams](<https://devfeed.tech/tags/teams.md>), [temporal](<https://devfeed.tech/tags/temporal.md>), [temporal-voices](<https://devfeed.tech/tags/temporal-voices.md>), [test](<https://devfeed.tech/tags/test.md>)

### AI overview

Temporal's Release Engineering team built a shared report format and Nexus Operation to collect test evidence from cloud validation and open source test Workflows while leaving tests and verdicts with their owners. Producers call a named Operation through an allowed Temporal Endpoint using their existing Temporal connections; a direct gRPC write API would require a reachable service and separate authentication and access controls. The synchronous handler validates and stores reports, keyed by (source, business_id), then returns the record ID. That key makes retries after a lost response return the same record, but repeated submissions can replace contents, and older payloads are not rejected by timestamp. Each report and result uses pass, warn, fail, or skipped; a test failure can coexist with successful ingestion. The team reads reports through a separate gRPC API. Nexus access is limited to explicitly allowed Namespaces in the same Cloud Account, and the synchronous database work must finish within ten seconds; Temporal recommends asynchronous Operations for uncertain database latency or availability. Reports support release decisions but do not automatically determine readiness,

### Source excerpt

How Temporal's Release Engineering team used a Nexus Operation and a shared report format to collect test results from many teams in one place.

## Introducing CodeRabbit Verify: Agentic application testing and AI quality assurance

DevFeed: [Introducing CodeRabbit Verify: Agentic application testing and AI quality assurance](<https://devfeed.tech/articles/introducing-coderabbit-verify-agentic-application-testing-and-ai-quality-assurance-140985.md>)

Original publisher: [Read original article](<https://coderabbit.ai/blog/introducing-coderabbit-verify>)

Author: Tejas Venugopal

Published: 2026-11-18T12:00:00Z

Content type: release

Language: en

Sources: [CodeRabbit](<https://devfeed.tech/sources/coderabbit.md>)

Topics: [Test automation](<https://devfeed.tech/topics/test-automation.md>), [ui-testing](<https://devfeed.tech/topics/ui-testing.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [bugfixes](<https://devfeed.tech/topics/bugfixes.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-quality](<https://devfeed.tech/tags/ai-quality.md>), [application](<https://devfeed.tech/tags/application.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [code](<https://devfeed.tech/tags/code.md>), [english](<https://devfeed.tech/tags/english.md>), [faster](<https://devfeed.tech/tags/faster.md>), [featured](<https://devfeed.tech/tags/featured.md>), [functional](<https://devfeed.tech/tags/functional.md>), [less](<https://devfeed.tech/tags/less.md>), [product](<https://devfeed.tech/tags/product.md>), [qa](<https://devfeed.tech/tags/qa.md>), [quality](<https://devfeed.tech/tags/quality.md>), [quality-assurance](<https://devfeed.tech/tags/quality-assurance.md>), [ship](<https://devfeed.tech/tags/ship.md>), [software](<https://devfeed.tech/tags/software.md>), [test](<https://devfeed.tech/tags/test.md>), [testing](<https://devfeed.tech/tags/testing.md>), [verify](<https://devfeed.tech/tags/verify.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

CodeRabbit Verify tests a running application against PR changes and reusable user journeys, aiming to catch functional bugs and broken workflows that unit tests or manual review may miss. For each PR, it builds editable scenarios from commits, source code, user-provided tests and documentation; existing CodeRabbit review context may also inform them. Expected behavior comes from intended behavior, docs and existing test expectations. Results are tied to the tested commit, and failures include observations and evidence that can be handed to CodeRabbit Agent or another coding agent. For regression testing, Verify proposes plain-English journeys for team review; approved journeys can be run on demand, tagged, or scheduled against a branch and test environment. Scheduled runs can create Jira or Linear issues. Verify records browser activity, screenshots and logs, and distinguishes application bugs from checks blocked by setup or other limitations. CodeRabbit Agent prepares and snapshots a sandbox environment for reuse, separate from production. The excerpt says PR runs, full-repository journey runs and CodeRabbit Agent fixes are free during the public beta; PR testing starts with `@ไ`

### Source excerpt

Automatically test your agentic code, catch functional bugs, and ship software faster with less manual QA

## Security that compounds

DevFeed: [Security that compounds](<https://devfeed.tech/articles/security-that-compounds-141985.md>)

Original publisher: [Read original article](<https://temporal.io/blog/security-that-compounds>)

Author: Kent Gruber

Published: 2026-11-18T00:00:00Z

Content type: article

Language: en

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

Topics: [Agentic SOC](<https://devfeed.tech/topics/agentic-soc.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [policy-as-code](<https://devfeed.tech/topics/policy-as-code.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [controls](<https://devfeed.tech/tags/controls.md>), [knowledge](<https://devfeed.tech/tags/knowledge.md>), [risks](<https://devfeed.tech/tags/risks.md>), [scale](<https://devfeed.tech/tags/scale.md>), [security](<https://devfeed.tech/tags/security.md>), [temporal](<https://devfeed.tech/tags/temporal.md>), [temporal-voices](<https://devfeed.tech/tags/temporal-voices.md>)

### AI overview

Temporal's security team uses a versioned repository of security boundaries, decisions, and tests as shared context for people and agents. Agents help triage reports, review designs, answer customer questions, assess dependency alerts, and run cross-repository campaigns; people make consequential decisions and approve merges. Deterministic hooks and policy code enforce controls outside the model: Deputy applies supply-chain policy across laptops, CI, and download time, while Camper tracks campaigns as Temporal Workflows and coordinates pull requests. The team checks agent claims against cited sources and tests, and treats incoming reports as untrusted. The article reports that one September vulnerability fix was merged and released in under 24 hours, with a reproducer and regression test. It also notes limits: agents can be wrong, and most investigations still run as long-lived agent sessions; moving them onto Temporal Workflows remains planned work.

### Source excerpt

See how Temporal's security team combines AI agents, shared security knowledge, and deterministic controls to investigate risks and scale security work.

## How we built Datadog's agentic vulnerability hunting system

DevFeed: [How we built Datadog's agentic vulnerability hunting system](<https://devfeed.tech/articles/how-we-built-datadog-s-agentic-vulnerability-hunting-system-142008.md>)

Original publisher: [Read original article](<https://www.datadoghq.com/blog/datadogs-agentic-vulnerability-hunting-system/>)

Author: Bianca Lankford; Matt Meen; Adrien Peronnet

Published: 2026-11-18T00:00:00Z

Content type: article

Language: en

Sources: [Datadog](<https://devfeed.tech/sources/datadog-the-monitor-blog.md>)

Topics: [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [context](<https://devfeed.tech/topics/context.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [container escape](<https://devfeed.tech/topics/container-escape.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>)

Tags: [agent-frameworks](<https://devfeed.tech/tags/agent-frameworks.md>), [agent-harnesses](<https://devfeed.tech/tags/agent-harnesses.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-models](<https://devfeed.tech/tags/ai-models.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [application-security-testing](<https://devfeed.tech/tags/application-security-testing.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [attack-paths](<https://devfeed.tech/tags/attack-paths.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [cilium](<https://devfeed.tech/tags/cilium.md>), [cloud-metadata](<https://devfeed.tech/tags/cloud-metadata.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [context](<https://devfeed.tech/tags/context.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [security](<https://devfeed.tech/tags/security.md>), [threat](<https://devfeed.tech/tags/threat.md>), [threat-detection](<https://devfeed.tech/tags/threat-detection.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

Datadog's vulnerability hunting pipeline uses compact, human-reviewed threat packs to give agents service-specific security requirements, trust assumptions, code locations, and known protections. Packs are drafted from code and security materials, clarified with service experts, and reviewed before use. The pipeline routes discovery, qualification, and reproduction tasks to capable cost-effective models. A judge qualifies a candidate only when it identifies a declared invariant, reachable entry point, and path that violates the invariant; qualified findings then receive a proof-of-concept attempt, while unverified cases retain that limitation. Datadog benchmarks changes using frozen pack and repository versions and hidden reference findings. A separate semantic judge matches reports by attacker capability, boundary, root cause, and exploit path. Repeated runs track union detection and stable detection, currently defined as detection in at least 7 of 10 runs, a provisional threshold. The text reports that threat packs reduced noise and improved report quality, and describes confirmed findings, while noting that model outputs vary and proposed fixes remain future work.

### Source excerpt

We developed threat packs that give our agents the context they need to run efficient, repeatable hunts. Learn how we did it.

## Agents are users, so your software needs evals

DevFeed: [Agents are users, so your software needs evals](<https://devfeed.tech/articles/agents-are-users-so-your-software-needs-evals-136001.md>)

Original publisher: [Read original article](<https://vercel.com/blog/agent-evals>)

Author: Yury Selivanov

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

Content type: tutorial

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Test automation](<https://devfeed.tech/topics/test-automation.md>), [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-software](<https://devfeed.tech/tags/agentic-software.md>), [agentic-testing](<https://devfeed.tech/tags/agentic-testing.md>), [agents](<https://devfeed.tech/tags/agents.md>), [api](<https://devfeed.tech/tags/api.md>), [cli](<https://devfeed.tech/tags/cli.md>), [command](<https://devfeed.tech/tags/command.md>), [cost](<https://devfeed.tech/tags/cost.md>), [decision](<https://devfeed.tech/tags/decision.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [doing](<https://devfeed.tech/tags/doing.md>), [e2e](<https://devfeed.tech/tags/e2e.md>), [eval](<https://devfeed.tech/tags/eval.md>), [evals](<https://devfeed.tech/tags/evals.md>), [fast](<https://devfeed.tech/tags/fast.md>), [filter](<https://devfeed.tech/tags/filter.md>), [observability](<https://devfeed.tech/tags/observability.md>), [software](<https://devfeed.tech/tags/software.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

Agent evals measure how often software agents complete user tasks correctly across repeated trials; a successful API call or one good manual run can hide wrong outcomes. The excerpt recommends choosing the cheapest test tier that catches the target problem, then using end-to-end evals for tasks whose success depends on a sequence of actions. Build a small task set from user-relevant failures, with repeatable environments and verifiers that score each requirement. Track success rate and choose pass@k or pass^k according to whether occasional success or consistent reliability matters; measure steps, time and cost on successful trials. Run variants repeatedly, inspect failed and passing traces to identify root causes and misleading passes, then rerun after a targeted fix. The example uses Harbor with Vercel Sandboxes for concurrent trials, AI Gateway for model calls, and Vercel storage for traces. The excerpt also stresses isolating seed data and verifiers from agent writes, and notes that small trial counts and saturated evals limit what results can establish.

### Source excerpt

Agents are now users of software, doing work on people's behalf. Whether you're building the agent or the software it uses (API, CLI, MCP server, SDK), evals give you a way to measure how well that work gets done. Agents probably missed your launch video and billboard on Highway 101, but they still go through the same funnel a human does to find and use a product: Discovery, Selection, Access, and Success. You can build evals for any stage of this funnel. Here, we'll focus on the final stage, Success: whether the agent completes the user's task correctly. That's more difficult to check than it sounds. An agent can place a "successful" order for a hot latte when the user asked for an iced one. The request worked, so the logs in your Observability stack look fine. And because LLM outputs vary between runs, one good manual test can't tell you whether a fix worked. You need to repeat the same tasks and grade the outcomes, before and after the change. That's what an eval is, a test you run many times and score. Here's how we build one. The agentic testing pyramid If a test asks "did it work?", an eval asks "how often does it work, and how well?" We group agentic software tests by how many LLM calls they typically need: deterministic tests (0), one-turn evals (1), and E2E evals (2+ across a whole task). This has turned out to be a great proxy for the effort to build them, the time they take to run, and the cost of running them. Just like in the practical test pyramid, the cheap and fast tests should make up the bulk of your test suite. To use the pyramid, start with the problem you want to catch and pick the lowest tier that can catch it. For Success, that's the top. A one-turn eval checks a single decision, like which command the agent runs first. But Success depends on the whole sequence of steps (e.g. search for cafes -> filter on user criteria -> place the latte order). Each one can look reasonable on its own, and the agent can still get the wrong outcome. An E2E eval l

## How We Reached 99% Line Coverage in a React Native App

DevFeed: [How We Reached 99% Line Coverage in a React Native App](<https://devfeed.tech/articles/how-we-reached-99-line-coverage-in-a-react-native-app-134517.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-we-reached-99percent-line-coverage-in-a-react-native-app?source=rss>)

Author: John Adib

Published: 2026-11-15T13:37:46Z

Content type: article

Language: en

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

Topics: [React Native](<https://devfeed.tech/topics/react-native.md>), [Expo](<https://devfeed.tech/topics/expo.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>), [Instrumentation](<https://devfeed.tech/topics/instrumentation.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Spec Driven Development](<https://devfeed.tech/topics/spec-driven-development.md>)

Tags: [automated-regression-testing](<https://devfeed.tech/tags/automated-regression-testing.md>), [ci](<https://devfeed.tech/tags/ci.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [jest](<https://devfeed.tech/tags/jest.md>), [maestro](<https://devfeed.tech/tags/maestro.md>), [maestro-testing](<https://devfeed.tech/tags/maestro-testing.md>), [mobile-app-testing](<https://devfeed.tech/tags/mobile-app-testing.md>), [react-native](<https://devfeed.tech/tags/react-native.md>), [react-native-testing](<https://devfeed.tech/tags/react-native-testing.md>), [react-native-unit-tests](<https://devfeed.tech/tags/react-native-unit-tests.md>), [test-coverage](<https://devfeed.tech/tags/test-coverage.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The team reached 99.26% line coverage in October by making tests part of completing changes, expanding Jest unit tests, and bringing Maestro device flows into CI. The figure covered 22,903 of 23,072 eligible lines across four Jest shards; branch coverage was 95.55%, and CI thresholds were pinned to that measured baseline. The team excluded test helpers, Storybook, development-only code and other files from the production-code scope. Inventory counts grew from 113 unit-test files and 14 Maestro YAML files in April to 2,257 and 404 in October, but file counts did not establish behavioral coverage. Although repository leaf flows reached all 99 non-exempt product routes, CI-run leaves reached only 28. The article cautions that coverage cannot show whether assertions catch defects or what happens on iOS and Android; regression tests that fail against the old defect, plus device runs, screenshots and recordings, supplied other review evidence.

### Source excerpt

How one engineering team scaled React Native testing with Jest, Maestro, and CI, reaching 99.26% line coverage while improving verification.

## Nobody Owns the Handoff: Why Integration Defects Have No Home in Multi-Vendor Programs

DevFeed: [Nobody Owns the Handoff: Why Integration Defects Have No Home in Multi-Vendor Programs](<https://devfeed.tech/articles/nobody-owns-the-handoff-why-integration-defects-have-no-home-in-multi-vendor-programs-133295.md>)

Original publisher: [Read original article](<https://sdtimes.com/integration/nobody-owns-the-handoff-why-integration-defects-have-no-home-in-multi-vendor-programs/>)

Author: Shivani Managari

Published: 2026-11-13T21:12:36Z

Content type: opinion

Language: en

Sources: [SD Times](<https://devfeed.tech/sources/sd-times.md>)

Topics: [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [acceptance](<https://devfeed.tech/tags/acceptance.md>), [after](<https://devfeed.tech/tags/after.md>), [all](<https://devfeed.tech/tags/all.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [argument](<https://devfeed.tech/tags/argument.md>), [award](<https://devfeed.tech/tags/award.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [budget](<https://devfeed.tech/tags/budget.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [business](<https://devfeed.tech/tags/business.md>), [business-process](<https://devfeed.tech/tags/business-process.md>), [defects](<https://devfeed.tech/tags/defects.md>), [first](<https://devfeed.tech/tags/first.md>), [guest-view](<https://devfeed.tech/tags/guest-view.md>), [handoffs](<https://devfeed.tech/tags/handoffs.md>), [integration](<https://devfeed.tech/tags/integration.md>), [integration-tests](<https://devfeed.tech/tags/integration-tests.md>), [over](<https://devfeed.tech/tags/over.md>), [picture](<https://devfeed.tech/tags/picture.md>), [process](<https://devfeed.tech/tags/process.md>), [schedule](<https://devfeed.tech/tags/schedule.md>), [takes](<https://devfeed.tech/tags/takes.md>)

### AI overview

At vendor boundaries, a component can meet its own specification while the combined business process fails; when contracts assign no owner to the handoff, diagnosis and approval disputes can cost more time and money than the fix. The excerpt recommends naming an accountable owner and escalation path for each interface, funding cross-vendor work, and defining who writes, provisions, and accepts integration tests. Require evidence against an agreed interface version, including pass/fail criteria, environment, results, open defects, and disclosure of simulators. Gate relevant milestones on end-to-end scenarios, and consider joint-acceptance payment terms only for the highest-risk seams, with responsibilities written down; smaller vendors may decline that risk. Set these terms during solicitation, since changes after award may require contract modification. The dollar figures and scenarios are presented as illustrative.

### Source excerpt

The fix takes six hours. The argument over whose fix it is takes three weeks -- and the schedule absorbs every day of it. Picture it, hypothetically: a record crosses from Vendor A to Vendor B and arrives corrupted, so Vendor B's intake rejects it and the business process stops. Both vendors check their own... ... continue reading The post Nobody Owns the Handoff: Why Integration Defects Have No Home in Multi-Vendor Programs appeared first on SD Times.

## From desktop to cloud to road

DevFeed: [From desktop to cloud to road](<https://devfeed.tech/articles/from-desktop-to-cloud-to-road-133358.md>)

Original publisher: [Read original article](<https://ubuntu.com//blog/from-desktop-to-cloud-to-road>)

Author: Jaume Rafols

Published: 2026-11-13T09:31:00Z

Content type: article

Language: en

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

Topics: [Ubuntu](<https://devfeed.tech/topics/ubuntu.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>)

Tags: [abstraction](<https://devfeed.tech/tags/abstraction.md>), [abstractions](<https://devfeed.tech/tags/abstractions.md>), [algorithms](<https://devfeed.tech/tags/algorithms.md>), [api](<https://devfeed.tech/tags/api.md>), [application](<https://devfeed.tech/tags/application.md>), [automotive](<https://devfeed.tech/tags/automotive.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [data-centers](<https://devfeed.tech/tags/data-centers.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [failures](<https://devfeed.tech/tags/failures.md>), [features](<https://devfeed.tech/tags/features.md>), [integration](<https://devfeed.tech/tags/integration.md>), [software](<https://devfeed.tech/tags/software.md>), [teams](<https://devfeed.tech/tags/teams.md>), [toolchain](<https://devfeed.tech/tags/toolchain.md>), [vehicle](<https://devfeed.tech/tags/vehicle.md>), [vehicles](<https://devfeed.tech/tags/vehicles.md>), [workstations](<https://devfeed.tech/tags/workstations.md>)

### AI overview

The article argues that matching software environments across developer workstations, cloud CI and vehicle ECUs can reduce dependency conflicts, toolchain mismatches and manual porting. It describes environmental parity as two layers: hardware abstraction that separates applications from silicon-specific drivers, and consistent kernels and libraries across platforms. Canonical presents Ubuntu as its approach, citing native x86, ARM64 and RISC-V support and a consistent software stack from development through deployment. For Ubuntu Pro, it claims up to 15 years of LTS, API stability with continuous regression testing, and processes aligned with ISO/SAE 21434. These are the article's claims; the excerpt provides no independent evaluation or comparison with other providers.

### Source excerpt

In an era where software defines vehicle value, engineering teams face a friction bottleneck. They spend hours fighting dependency conflicts, toolchain mismatches, and integration failures instead of writing vehicle features. As vehicles effectively become data centers, teams waste hours resolving dependency conflicts across desktop workstations, cloud, and physical targets. This article explores how establishing consistency [...]

## IP Integration Challenges Evolve

DevFeed: [IP Integration Challenges Evolve](<https://devfeed.tech/articles/ip-integration-challenges-evolve-130167.md>)

Original publisher: [Read original article](<https://semiengineering.com/ip-integration-challenges-evolve/>)

Author: Brian Bailey

Published: 2026-11-12T08:05:00Z

Content type: article

Language: en

Sources: [Semiconductor Engineering](<https://devfeed.tech/sources/semiconductor-engineering.md>)

Topics: [Chip design](<https://devfeed.tech/topics/chip-design.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [accelerate](<https://devfeed.tech/tags/accelerate.md>), [added](<https://devfeed.tech/tags/added.md>), [addition](<https://devfeed.tech/tags/addition.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agile-analog](<https://devfeed.tech/tags/agile-analog.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-automation](<https://devfeed.tech/tags/ai-automation.md>), [analog-content](<https://devfeed.tech/tags/analog-content.md>), [axiomise](<https://devfeed.tech/tags/axiomise.md>), [but](<https://devfeed.tech/tags/but.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [chiplet](<https://devfeed.tech/tags/chiplet.md>), [chiplet-integration](<https://devfeed.tech/tags/chiplet-integration.md>), [chiplets](<https://devfeed.tech/tags/chiplets.md>), [complex](<https://devfeed.tech/tags/complex.md>), [first](<https://devfeed.tech/tags/first.md>), [ic-manage](<https://devfeed.tech/tags/ic-manage.md>), [integration](<https://devfeed.tech/tags/integration.md>), [ip](<https://devfeed.tech/tags/ip.md>), [ip-integration](<https://devfeed.tech/tags/ip-integration.md>), [ip-verification](<https://devfeed.tech/tags/ip-verification.md>), [keysight](<https://devfeed.tech/tags/keysight.md>), [low-power-high-performance](<https://devfeed.tech/tags/low-power-high-performance.md>), [more](<https://devfeed.tech/tags/more.md>), [power-and-thermal-control](<https://devfeed.tech/tags/power-and-thermal-control.md>), [semiconductor](<https://devfeed.tech/tags/semiconductor.md>), [solutions](<https://devfeed.tech/tags/solutions.md>), [synopsys](<https://devfeed.tech/tags/synopsys.md>), [top-stories](<https://devfeed.tech/tags/top-stories.md>), [verification](<https://devfeed.tech/tags/verification.md>), [version-control](<https://devfeed.tech/tags/version-control.md>), [vsia](<https://devfeed.tech/tags/vsia.md>)

### AI overview

IP integration failures often emerge between individually verified blocks, where mismatched protocol assumptions can cause deadlocks, lost credits, ordering errors, or system hangs. Complexity depends on interactions and undocumented assumptions, not simply chip size. The excerpt identifies incomplete specifications, software and firmware dependencies, power sequencing, thermal and analog constraints, chiplet interoperability, opaque or differently configured IP, and weak hardware/software version traceability as growing pressures. It notes that UCIe addresses early firmware download and link-layer interoperability, while system-level agreement on address maps, coherency, and software remains necessary. Verification may need to cover legal configurations and cross-block behavior; AI models are cited as helping reach corner cases faster. The article concludes that management mechanisms are evolving alongside the problem, with a follow-up report planned on newer solutions and AI.

### Source excerpt

Integration challenges are growing more complex, but the problem is well understood and solutions are emerging. The post IP Integration Challenges Evolve appeared first on Semiconductor Engineering.

## How Open Is Open? Iceberg, Catalogs, and User Choice

DevFeed: [How Open Is Open? Iceberg, Catalogs, and User Choice](<https://devfeed.tech/articles/how-open-is-open-iceberg-catalogs-and-user-choice-129822.md>)

Original publisher: [Read original article](<https://www.dataengineeringweekly.com/p/how-open-is-open-iceberg-catalogs>)

Author: Ananth Packkildurai

Published: 2026-11-11T20:50:33Z

Content type: opinion

Language: en

Sources: [Data Engineering Weekly](<https://devfeed.tech/sources/data-engineering-weekly.md>)

Topics: [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>), [Data Management](<https://devfeed.tech/topics/data-management.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [API Governance](<https://devfeed.tech/topics/api-governance.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>)

Tags: [apache](<https://devfeed.tech/tags/apache.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [apache-polaris](<https://devfeed.tech/tags/apache-polaris.md>), [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [change](<https://devfeed.tech/tags/change.md>), [choice](<https://devfeed.tech/tags/choice.md>), [commit](<https://devfeed.tech/tags/commit.md>), [control](<https://devfeed.tech/tags/control.md>), [engines](<https://devfeed.tech/tags/engines.md>), [giving](<https://devfeed.tech/tags/giving.md>), [iceberg](<https://devfeed.tech/tags/iceberg.md>), [next](<https://devfeed.tech/tags/next.md>), [open](<https://devfeed.tech/tags/open.md>), [providers](<https://devfeed.tech/tags/providers.md>), [test](<https://devfeed.tech/tags/test.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

Apache Iceberg's REST catalog protocol offers a foundation for catalog and engine choice, but an API connection alone does not establish production interoperability. The excerpt argues for a community-run, production-ready catalog as a common integration target, backed by public, versioned compatibility results that spell out supported operations, optional capabilities, configurations, and limitations. It also calls for controlled performance workloads covering metadata loading, scan planning, and concurrent commits, plus tested migration procedures addressing permissions, identities, credentials, catalog state, and active writers. Apache Polaris and Iceberg's REST Compatibility Kit are existing contributions; the proposed next step is to connect them to explicit expectations and evidence, while allowing alternative implementations and keeping the specification authoritative.

### Source excerpt

The next test of openness: giving users the freedom to choose engines, control their catalogs, and change providers.

## How GitHub Used AI to Port Copilot From TypeScript to Rust in Record Time

DevFeed: [How GitHub Used AI to Port Copilot From TypeScript to Rust in Record Time](<https://devfeed.tech/articles/how-github-used-ai-to-port-copilot-from-typescript-to-rust-in-record-time-126820.md>)

Original publisher: [Read original article](<https://blog.bytebytego.com/p/how-github-used-ai-to-port-copilot>)

Author: ByteByteGo

Published: 2026-11-10T16:30:55Z

Content type: article

Language: en

Sources: [ByteByteGo](<https://devfeed.tech/sources/bytebytego.md>)

Topics: [GitHub Copilot](<https://devfeed.tech/topics/github-copilot.md>), [GitHub Copilot CLI](<https://devfeed.tech/topics/github-copilot-cli.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [GitHub Copilot SDK](<https://devfeed.tech/topics/github-copilot-sdk.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [about](<https://devfeed.tech/tags/about.md>), [act](<https://devfeed.tech/tags/act.md>), [added](<https://devfeed.tech/tags/added.md>), [after](<https://devfeed.tech/tags/after.md>), [ai](<https://devfeed.tech/tags/ai.md>), [article](<https://devfeed.tech/tags/article.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [github](<https://devfeed.tech/tags/github.md>), [learnings](<https://devfeed.tech/tags/learnings.md>), [look](<https://devfeed.tech/tags/look.md>), [port](<https://devfeed.tech/tags/port.md>), [porting](<https://devfeed.tech/tags/porting.md>), [rust](<https://devfeed.tech/tags/rust.md>), [this](<https://devfeed.tech/tags/this.md>), [time](<https://devfeed.tech/tags/time.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [used](<https://devfeed.tech/tags/used.md>), [was](<https://devfeed.tech/tags/was.md>), [we-ll](<https://devfeed.tech/tags/we-ll.md>)

### AI overview

GitHub replaced Copilot's TypeScript runtime with Rust through incremental component level changes, allowing ongoing development and keeping each change reviewable. Thin wrappers connected Rust components to remaining TypeScript, and the team preserved existing behavior, validated changes with end to end tests, and moved more interconnected components later. A coordinating agent assigned work to child sessions on separate branches; concurrent builds overwhelmed one developer's laptop, so builds were serialized. Review agents compared implementations for behavior and compatibility, with human reviewers checking architecture and risk. The migration encountered subtle compatibility, state management, integration, and performance regressions. In reported tests, a client turn and cleanup fell from 5.25 seconds to 292 milliseconds; throughput rose from 7.55 to 120 session lifecycles per second, and peak private memory in a 10 client test fell from 1,383 MB to 126 MB. The excerpt reports about $120,000 in AI token costs, plus developer time, and emphasizes clear instructions and strong, protected tests.

### Source excerpt

In this article, we'll look at how this porting was done and the learnings along the way.

## Software Project Rescue: When to Stabilize, Refactor, or Rebuild

DevFeed: [Software Project Rescue: When to Stabilize, Refactor, or Rebuild](<https://devfeed.tech/articles/software-project-rescue-when-to-stabilize-refactor-or-rebuild-127132.md>)

Original publisher: [Read original article](<https://hackernoon.com/software-project-rescue-when-to-stabilize-refactor-or-rebuild?source=rss>)

Author: Mariia Popovych

Published: 2026-11-10T16:23:59Z

Content type: article

Language: en

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

Topics: [Software](<https://devfeed.tech/topics/software.md>), [Tech Debt](<https://devfeed.tech/topics/tech-debt.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [Software Process](<https://devfeed.tech/topics/software-process.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [developer-productivity](<https://devfeed.tech/topics/developer-productivity.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-avatar](<https://devfeed.tech/tags/ai-avatar.md>), [ai-code](<https://devfeed.tech/tags/ai-code.md>), [ai-coding-tools](<https://devfeed.tech/tags/ai-coding-tools.md>), [ai-content](<https://devfeed.tech/tags/ai-content.md>), [ai-services](<https://devfeed.tech/tags/ai-services.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [booking](<https://devfeed.tech/tags/booking.md>), [bug](<https://devfeed.tech/tags/bug.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [build](<https://devfeed.tech/tags/build.md>), [business](<https://devfeed.tech/tags/business.md>), [failure-in-software](<https://devfeed.tech/tags/failure-in-software.md>), [legacy-codebase-stabilization](<https://devfeed.tech/tags/legacy-codebase-stabilization.md>), [product](<https://devfeed.tech/tags/product.md>), [project](<https://devfeed.tech/tags/project.md>), [rebuild](<https://devfeed.tech/tags/rebuild.md>), [refactor](<https://devfeed.tech/tags/refactor.md>), [software](<https://devfeed.tech/tags/software.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [software-product-recovery](<https://devfeed.tech/tags/software-product-recovery.md>), [software-project-rescue](<https://devfeed.tech/tags/software-project-rescue.md>), [software-refactor-vs-rebuild](<https://devfeed.tech/tags/software-refactor-vs-rebuild.md>), [technical-debt](<https://devfeed.tech/tags/technical-debt.md>), [technical-debt-management](<https://devfeed.tech/tags/technical-debt-management.md>)

### AI overview

Software rescue begins with an audit to identify what is stable, fragile, and blocking development, then prioritizes problems affecting users and revenue. Stabilization addresses specific fragile areas when the core architecture is sound; refactoring restructures code when coupling or misplaced logic makes changes risky; a rebuild is warranted when the technology or architecture cannot support requirements or maintenance costs exceed replacement. The article describes focused interventions for integrations, production booking flows, AI generated code, handovers, and releases. Improvements proceed incrementally, with a handover that explains changes and remaining risks. Its case example attributes unreliable video production across three AI services to missing orchestration between providers, which the team mapped and rebuilt.

### Source excerpt

Software rescue isn't a last resort for failed products. Here's what it actually covers - and how to tell if your product needs it before something breaks.

## How we rebuilt the Shopify app in 12 weeks

DevFeed: [How we rebuilt the Shopify app in 12 weeks](<https://devfeed.tech/articles/how-we-rebuilt-the-shopify-app-in-12-weeks-126837.md>)

Original publisher: [Read original article](<https://shopify.engineering/shopify-app-rebuild>)

Author: Remi Vanhee

Published: 2026-11-10T14:36:23Z

Content type: article

Language: en

Sources: [Shopify Engineering](<https://devfeed.tech/sources/shopify-engineering.md>), [Shopify Engineering - Shopify Engineering](<https://devfeed.tech/sources/shopify-engineering-shopify-engineering.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [mobile-app-performance](<https://devfeed.tech/topics/mobile-app-performance.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [context-architecture](<https://devfeed.tech/topics/context-architecture.md>), [Shopify](<https://devfeed.tech/topics/shopify.md>), [Android](<https://devfeed.tech/topics/android.md>), [android-app-bundle](<https://devfeed.tech/topics/android-app-bundle.md>), [app startup](<https://devfeed.tech/topics/app-startup.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [app](<https://devfeed.tech/tags/app.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [code](<https://devfeed.tech/tags/code.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [shopify](<https://devfeed.tech/tags/shopify.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [validation](<https://devfeed.tech/tags/validation.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

Shopify says it rebuilt its mobile app from React Native to native Swift and Kotlin in 12 weeks with about 30 engineers and agents writing most of the code. The central change was the workflow around implementation: a shared cross-platform Reflex architecture, a CLI and testable business logic for millisecond feedback without a device, small migration checkpoints checked against the existing app, and CI guardrails for architectural drift. Pods of two engineers owned product areas across both platforms; agents reviewed PRs first, while humans retained final review and shipping decisions. Consistency made cross-platform changes easier to compare and reuse, at the cost of some platform idiom. Faster code generation shifted constraints to compute, CI, review, merging, and coordination. Shopify reports launch-time reductions, smaller Android binaries and lower memory use, and improved Android crash-free sessions; the excerpt provides figures for these outcomes. It also says new features without an existing screen remain a distinct challenge.

### Source excerpt

What changed when agents started writing our mobile code, and how we redesigned our architecture, tooling, and workflow around validation.

## How we moved our frontend off Firestore and built Lovable Realtime

DevFeed: [How we moved our frontend off Firestore and built Lovable Realtime](<https://devfeed.tech/articles/how-we-moved-our-frontend-off-firestore-and-built-lovable-realtime-126536.md>)

Original publisher: [Read original article](<https://lovable.dev/blog/lovable-realtime-service>)

Author: Ata Marzban

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

Content type: article

Language: en

Sources: [Lovable](<https://devfeed.tech/sources/lovable.md>)

Topics: [Frontend & real-time](<https://devfeed.tech/topics/frontend-real-time.md>), [Firestore](<https://devfeed.tech/topics/firestore.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [Full Stack Development](<https://devfeed.tech/topics/full-stack-development.md>), [build vs buy database solutions](<https://devfeed.tech/topics/build-vs-buy-database-solutions.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [backend](<https://devfeed.tech/tags/backend.md>), [cdc](<https://devfeed.tech/tags/cdc.md>), [change-data-capture](<https://devfeed.tech/tags/change-data-capture.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [firestore](<https://devfeed.tech/tags/firestore.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [go](<https://devfeed.tech/tags/go.md>), [lovable](<https://devfeed.tech/tags/lovable.md>), [reactive](<https://devfeed.tech/tags/reactive.md>), [realtime](<https://devfeed.tech/tags/realtime.md>), [server](<https://devfeed.tech/tags/server.md>), [service](<https://devfeed.tech/tags/service.md>), [subscriptions](<https://devfeed.tech/tags/subscriptions.md>), [technical-blog](<https://devfeed.tech/tags/technical-blog.md>)

### AI overview

Lovable replaced browser-side Firestore listeners with a Go WebSocket service that computes each user's authorized data view and refreshes it when source data or permissions change. Firestore and Spanner updates flow through change data capture and NATS to affected subscriptions; server-side projections, hashing, and wire-level deltas reduce redundant payloads. This kept the existing databases while centralizing authorization and payload shaping in the Go backend. The team tested with shadow traffic, then rolled out by feature flag over about a week without user-facing incidents. For Sep. 5-Oct. 5, 2026, it reported a peak of 2.06 million concurrent subscriptions and 2.61 billion frames. Estimated application payload fell from a 40 TB full-snapshot baseline to 1.11 TB through deduplication, deltas, and reconnect state reuse; protocol and transport overhead were excluded. The article notes that permission dependencies require explicit field comparisons, supported by static analysis, and that long-lived WebSockets require connection-aware scaling and careful reconnect management.

### Source excerpt

How we replaced frontend Firestore listeners with a Go and NATS realtime service, with reactive authorization, server-shaped payloads, and 2.06 million live subscriptions.

## Statically Verifying Well-Definedness of Separately Compiled Attribute Grammars

DevFeed: [Statically Verifying Well-Definedness of Separately Compiled Attribute Grammars](<https://devfeed.tech/articles/statically-verifying-well-definedness-of-separately-compiled-attribute-grammars-127180.md>)

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

Author: Federico Bruzzone, Walter Cazzola, Luca Favalli

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

Content type: article

Language: en

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

Topics: [Credo](<https://devfeed.tech/topics/credo.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [compilation](<https://devfeed.tech/tags/compilation.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cs-pl](<https://devfeed.tech/tags/cs-pl.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [data](<https://devfeed.tech/tags/data.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [development](<https://devfeed.tech/tags/development.md>), [errors](<https://devfeed.tech/tags/errors.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [extension](<https://devfeed.tech/tags/extension.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [flexibility](<https://devfeed.tech/tags/flexibility.md>), [flow](<https://devfeed.tech/tags/flow.md>), [guarantees](<https://devfeed.tech/tags/guarantees.md>), [integration](<https://devfeed.tech/tags/integration.md>), [key](<https://devfeed.tech/tags/key.md>), [language](<https://devfeed.tech/tags/language.md>), [modular](<https://devfeed.tech/tags/modular.md>), [modular-development](<https://devfeed.tech/tags/modular-development.md>)

### AI overview

Separately compiled language extensions can introduce attributes that make previously generated AST structures unsafe, leading to runtime errors such as undefined attribute accesses. The paper presents nlgcheck, a data-flow-based static analysis tool for the Neverlang workbench that checks composed, separately compiled language components before execution. The authors report that mutation testing on Neverlang projects found it improves robustness while preserving modularity and flexibility, with performance they say is suitable for routine development.

### Source excerpt

arXiv:2602.03777v2 Announce Type: replace-cross Abstract: The development of programming languages involves complex theoretical and practical challenges, particularly when addressing modularity and reusability through language extensions. While language workbenches aim to enable modular development under the constraints of the language extension problem, one critical constraint--separate compilation--is often relaxed due to its complexity. However, this relaxation undermines artifact reusability and integration with common dependency systems. A key difficulty under separate compilation arises from managing attribute grammars, as extensions may introduce new attributes that invalidate previously generated abstract syntax tree structures. Existing approaches, such as the use of dynamic maps in the Neverlang workbench, favor flexibility at the cost of compile-time correctness, leading to potential runtime errors due to undefined attributes. This work addresses this issue by introducing nlgcheck, a theoretically sound static analysis tool based on data-flow analysis for the Neverlang language workbench, which detects potential runtime errors--such as undefined attribute accesses--when separately compiled language components are composed, before the resulting language is ever run, thus preserving separate compilation while maintaining strong static correctness guarantees. Experimental evaluation using mutation testing on Neverlang-based projects demonstrates that nlgcheck effectively enhances robustness without sacrificing modularity or flexibility and with a level of performance that does not impede its adoption in daily development activities.

## Revenue Hub Connects Quote to Cash. Your Integration Still Needs a Ledger.

DevFeed: [Revenue Hub Connects Quote to Cash. Your Integration Still Needs a Ledger.](<https://devfeed.tech/articles/revenue-hub-connects-quote-to-cash-your-integration-still-needs-a-ledger-125757.md>)

Original publisher: [Read original article](<https://hackernoon.com/revenue-hub-connects-quote-to-cash-your-integration-still-needs-a-ledger?source=rss>)

Author: Pratik Thakker

Published: 2026-11-10T04:15:08Z

Content type: article

Language: en

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

Topics: [event-driven data processing](<https://devfeed.tech/topics/event-driven-data-processing.md>), [event-sourcing](<https://devfeed.tech/topics/event-sourcing.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>)

Tags: [accounting](<https://devfeed.tech/tags/accounting.md>), [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [automation](<https://devfeed.tech/tags/automation.md>), [billing](<https://devfeed.tech/tags/billing.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [contract-management](<https://devfeed.tech/tags/contract-management.md>), [contracts](<https://devfeed.tech/tags/contracts.md>), [data-governance](<https://devfeed.tech/tags/data-governance.md>), [data-integration](<https://devfeed.tech/tags/data-integration.md>), [design](<https://devfeed.tech/tags/design.md>), [enterprise-software](<https://devfeed.tech/tags/enterprise-software.md>), [event](<https://devfeed.tech/tags/event.md>), [hub](<https://devfeed.tech/tags/hub.md>), [hubspot](<https://devfeed.tech/tags/hubspot.md>), [idempotency](<https://devfeed.tech/tags/idempotency.md>), [identity](<https://devfeed.tech/tags/identity.md>), [integration](<https://devfeed.tech/tags/integration.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [ledger](<https://devfeed.tech/tags/ledger.md>), [ownership](<https://devfeed.tech/tags/ownership.md>), [processing](<https://devfeed.tech/tags/processing.md>), [quote](<https://devfeed.tech/tags/quote.md>), [reconciliation](<https://devfeed.tech/tags/reconciliation.md>), [revenue](<https://devfeed.tech/tags/revenue.md>), [revenue-operations](<https://devfeed.tech/tags/revenue-operations.md>), [system-design](<https://devfeed.tech/tags/system-design.md>)

### AI overview

HubSpot Revenue Hub connects quoting, contracts, billing, and payments, but integrations still need explicit ownership, identity, event handling, and reconciliation to explain how an agreement produced a bill and collection. The article proposes an append-oriented, integration-owned event ledger that distinguishes commitments, scheduled billing, invoices, collections, and accounting measures; records stable business keys, effective time, processing outcomes, and downstream references; and handles retries without repeating financial side effects. It recommends resolving buyer and payer roles explicitly, treating configuration changes as revenue-process policy, testing failure and recovery cases, and classifying reconciliation differences with an owner and evidence requirement. Start with one narrow commercial motion and verify the account's enabled paths and billing behavior: HubSpot documentation describes configuration-dependent requirements, and direct contract creation is documented as beta. Example fields and event states are proposed designs, not native HubSpot properties or workflows.

### Source excerpt

Design Revenue Hub integrations with explicit identity, event processing, billing ownership, and reconciliation instead of assuming connected means correct.

## How to Build an Accessible Gold Value Calculator in Vanilla JavaScript

DevFeed: [How to Build an Accessible Gold Value Calculator in Vanilla JavaScript](<https://devfeed.tech/articles/how-to-build-an-accessible-gold-value-calculator-in-vanilla-javascript-126631.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/how-to-build-an-accessible-gold-value-calculator-in-vanilla-javascript/>)

Author: M Ahmad Shahmir

Published: 2026-11-10T03:47:01Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [Web Content Accessibility Guidelines](<https://devfeed.tech/topics/web-content-accessibility-guidelines.md>), [Web](<https://devfeed.tech/topics/web.md>), [aria](<https://devfeed.tech/topics/aria.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>)

Tags: [accessible](<https://devfeed.tech/tags/accessible.md>), [build](<https://devfeed.tech/tags/build.md>), [calculator](<https://devfeed.tech/tags/calculator.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [html-css](<https://devfeed.tech/tags/html-css.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [value](<https://devfeed.tech/tags/value.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

The tutorial builds a gold value calculator that converts grams, pennyweight, or troy ounces to grams and computes pure gold weight, melt value, and an optional buyer payout. It uses a pure JavaScript calculation and validation module, accessible labeled controls with a live output, and URL parameters to restore and share inputs. For a prefilling spot price, it puts the provider API key behind a Node.js/Express endpoint with a five-minute cache, three-second timeout, and stale-price fallback; users can edit the price. The text distinguishes melt value from an actual buyer offer and recommends labeling results as estimates. It also shows tests with Node's built-in runner. A server is optional if users enter the spot price themselves or a scheduled job supplies static JSON.

### Source excerpt

null Continue reading How to Build an Accessible Gold Value Calculator in Vanilla JavaScript on SitePoint.

## Making payment method testing repeatable: building the Adyen Payment Simulator

DevFeed: [Making payment method testing repeatable: building the Adyen Payment Simulator](<https://devfeed.tech/articles/making-payment-method-testing-repeatable-building-the-adyen-payment-simulator-126555.md>)

Original publisher: [Read original article](<https://medium.com/adyen/making-payment-method-testing-repeatable-building-the-adyen-payment-simulator-5c11d6fcbe18?source=rss----64941d9fbc09---4>)

Author: Adyen

Published: 2026-11-09T14:15:51Z

Content type: article

Language: en

Sources: [Adyen Tech](<https://devfeed.tech/sources/adyen-tech.md>)

Topics: [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [reproducibility](<https://devfeed.tech/topics/reproducibility.md>)

Tags: [adyen](<https://devfeed.tech/tags/adyen.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [bank](<https://devfeed.tech/tags/bank.md>), [banking](<https://devfeed.tech/tags/banking.md>), [capture](<https://devfeed.tech/tags/capture.md>), [card](<https://devfeed.tech/tags/card.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [code](<https://devfeed.tech/tags/code.md>), [confidence](<https://devfeed.tech/tags/confidence.md>), [developers](<https://devfeed.tech/tags/developers.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [environment](<https://devfeed.tech/tags/environment.md>), [failure](<https://devfeed.tech/tags/failure.md>), [flow](<https://devfeed.tech/tags/flow.md>), [integration](<https://devfeed.tech/tags/integration.md>), [integration-testing](<https://devfeed.tech/tags/integration-testing.md>), [payment](<https://devfeed.tech/tags/payment.md>), [payments](<https://devfeed.tech/tags/payments.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [simulator](<https://devfeed.tech/tags/simulator.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The Adyen Payment Simulator makes common payment outcomes repeatable so teams can test complete payment lifecycles, including asynchronous results and post-payment actions. For flows such as UPI Intent, a test selects an authorized, refused, or canceled outcome on a simulator page; Adyen then sends an AUTHORISATION webhook, and the integration must commit the resulting state. This exposes bugs that checking only an initial pending response can miss. The design favors explicit outcome selection over injecting arbitrary payment state, and shares a common lifecycle while keeping payment-specific continuations visible. Per-method response adapters shape requests and responses; generic flows share simulation logic, while UPI has dedicated logic, and webhook delivery is shared. The simulator complements provider sandboxes, which can offer a more faithful shopper experience beyond the merchant page but require separate integrations. It does not simulate every method-specific quirk, provide load-test throughput characteristics, or reproduce failure modes that require production telemetry; availability also depends on the payment method.

### Source excerpt

By Ayodeji Ogundare, Henk Grent, Marc Sernatinger, and Shantanu Tarey Adyen supports merchants around the world, and our catalog of payment methods keeps growing. For merchants integrating with us, payments are the heart of the business, and the code that handles them is among the most consequential software they ship. A broken payment path isn't just an inconvenience; it's lost revenue and lost shopper trust. Getting a green happy-path response during integration testing doesn't prove your integration will hold up under the conditions that actually matter at go-live. In live, many payment methods finish outside your checkout: the shopper approves in their banking or payment app, and your integration hears about the result later. A test that only checks the first response never sees that. How a payment finishes varies by payment method. That's why we built the Adyen Payment Simulator: to give developers and QA engineers a way to test the most common success and failure scenarios on demand, with the same result every time, from authorized, refused and canceled payments to post-payment modifications such as capture and refund. That way they can build confidence in their integration, before launch and whenever they need to reproduce a known outcome later, without setting up a separate test environment for every payment method. Payment methods don't behave alike A basic card payment can be completed in a single request and a single response. Many other payment methods can't. For those, the flow a merchant tests against follows a lifecycle: an initial call, an additional action the integration must perform, an asynchronous result, and a final state the merchant has to commit. Different payment methods interrupt that lifecycle in different places. Three concrete examples: UPI Intent, India's real-time bank-to-bank payment method, where the shopper is redirected to a UPI app, the initial response is pending, and the result is established only when the integration receives

## How to build a paid booking calendar your marketers can edit with Stripe and Webflow Cloud

DevFeed: [How to build a paid booking calendar your marketers can edit with Stripe and Webflow Cloud](<https://devfeed.tech/articles/how-to-build-a-paid-booking-calendar-your-marketers-can-edit-with-stripe-and-webflow-cloud-123937.md>)

Original publisher: [Read original article](<https://www.webflow.com/blog/stripe-booking-calendar-webflow-cloud>)

Author: Ismail Ajagbe

Published: 2026-11-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [Webflow Blog](<https://devfeed.tech/sources/webflow-blog.md>)

Topics: [webflow](<https://devfeed.tech/topics/webflow.md>), [hosting](<https://devfeed.tech/topics/hosting.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [booking](<https://devfeed.tech/tags/booking.md>), [calendar](<https://devfeed.tech/tags/calendar.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cms](<https://devfeed.tech/tags/cms.md>), [collection](<https://devfeed.tech/tags/collection.md>), [guides](<https://devfeed.tech/tags/guides.md>), [stripe](<https://devfeed.tech/tags/stripe.md>), [time](<https://devfeed.tech/tags/time.md>), [webflow](<https://devfeed.tech/tags/webflow.md>)

### AI overview

The build keeps editable time slots in Webflow CMS and uses a Next.js 15 app on Webflow Cloud with Stripe Checkout to take payment. It prevents duplicate bookings by claiming each slot in a SQLite table with a unique slot ID before creating checkout; a signed Stripe webhook books the slot only after payment is confirmed, or releases it when checkout expires. The guide covers the CMS fields, credentials, database migration, API routes, calendar page, local webhook testing, deployment, and troubleshooting. It requires Node.js 22.13 or later, npm, a Stripe test account, and suitable Webflow access; mounting on a custom domain requires Premium. CMS list responses may lag edits by up to five minutes, though checkout rechecks the live item. Anonymous checkout requests can hold slots for up to 36 minutes, so the guide recommends rate limiting. It also notes that slots count toward CMS limits and should be periodically removed or archived.

### Source excerpt

Learn how to sell time slots from a Webflow CMS collection with Stripe Checkout.

## Composable Parts Architecture

DevFeed: [Composable Parts Architecture](<https://devfeed.tech/articles/composable-parts-architecture-121430.md>)

Original publisher: [Read original article](<https://blog.devops.dev/composable-parts-architecture-b660caf40e8f?source=rss----33f8b2d9a328---4>)

Author: Scaibu

Published: 2026-11-06T09:47:16Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [architecture-components](<https://devfeed.tech/topics/architecture-components.md>), [Dependency Inversion](<https://devfeed.tech/topics/dependency-inversion.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [adapter pattern](<https://devfeed.tech/topics/adapter-pattern.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [Functional programming](<https://devfeed.tech/topics/functional-programming.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [event-sourcing](<https://devfeed.tech/topics/event-sourcing.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [clean-architecture](<https://devfeed.tech/tags/clean-architecture.md>), [code](<https://devfeed.tech/tags/code.md>), [components](<https://devfeed.tech/tags/components.md>), [connect](<https://devfeed.tech/tags/connect.md>), [contracts](<https://devfeed.tech/tags/contracts.md>), [crash](<https://devfeed.tech/tags/crash.md>), [data](<https://devfeed.tech/tags/data.md>), [data-ownership](<https://devfeed.tech/tags/data-ownership.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [design](<https://devfeed.tech/tags/design.md>), [durability](<https://devfeed.tech/tags/durability.md>), [enterprise-architecture](<https://devfeed.tech/tags/enterprise-architecture.md>), [event](<https://devfeed.tech/tags/event.md>), [event-driven-architecture](<https://devfeed.tech/tags/event-driven-architecture.md>), [execution](<https://devfeed.tech/tags/execution.md>), [features](<https://devfeed.tech/tags/features.md>), [independent](<https://devfeed.tech/tags/independent.md>), [integrate](<https://devfeed.tech/tags/integrate.md>), [internals](<https://devfeed.tech/tags/internals.md>), [logic](<https://devfeed.tech/tags/logic.md>), [messages](<https://devfeed.tech/tags/messages.md>), [parts](<https://devfeed.tech/tags/parts.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>)

### AI overview

The architecture aims to let parts change independently by having them depend on published, versioned contracts rather than one another's internals. Each part owns its data and exposes pure logic through ports and replaceable adapters; manifests let the platform validate and wire parts without hand-edited central registries. Events through a durable log are the default connection, while synchronous requests are reserved for cases needing an immediate answer and constrained to short call chains. An atomic outbox, idempotency keys, deduplication, checkpoints, deadlines, and retries make interruptions and duplicate delivery recoverable; consumers keep read-only data copies and reconcile them against their owner. The same contracts and host protocol support different runtimes, with adapters and test kits handling host-specific integration. The excerpt also describes contract versioning, graph validation, and domain-based deployment packing as ways to manage growth. These are architectural prescriptions; the supplied text does not establish implementation results.

### Source excerpt

How small, independent parts connect, share data, survive disconnects, integrate with any host, and grow to 1000+ features -- where adding or changing something touches one place, not a hundred.Contents The six rules Vocabulary The system at a glance Anatomy of a part Contracts Connecting parts Execution model inside a part Data ownership and sharing Integrating with any system Durability: connections that break safely Changing the system Scaling to 1000+ parts Platform components Enforcement Testing Adding a new part: checklist Anti-patterns Open decisions Introduction Most large systems do not fail because a single component is badly written. They fail because components know too much about each other. One service reads another service's tables "just this once"; a handler calls three other services in sequence because it was quicker than designing an event; a central routing file collects one line from every team until nobody can change it without a merge conflict. Each shortcut is harmless on its own. Together they produce a system in which adding a field means editing a hundred files, an outage in one corner takes down everything, and a dropped network connection corrupts data. This document describes a structure that prevents those outcomes by design rather than by discipline. It rests on two ideas: No part knows another part. Parts know contracts. A part is aware of its own logic and of the published, versioned contracts it uses. It never sees another part's code, storage, or deployment details. Because nothing depends on internals, internals can change freely. Every connection is assumed to break, and breaking must cost nothing. Networks drop, processes crash, and messages arrive twice or out of order. Instead of trying to prevent these failures, the structure makes each one harmless: nothing is lost, nothing happens twice, and nothing waits forever. Everything that follows is an elaboration of those two ideas, together with the tooling that keeps them true as

## Data Access Testing With @testcontainers

DevFeed: [Data Access Testing With @testcontainers](<https://devfeed.tech/articles/data-access-testing-with-testcontainers-117746.md>)

Original publisher: [Read original article](<https://blog.master.dev/data-access-testing-with-testcontainers/>)

Author: Adam Rackis

Published: 2026-11-04T12:58:05Z

Content type: tutorial

Language: en

Sources: [Master.dev Blog RSS Feed](<https://devfeed.tech/sources/master-dev-blog-rss-feed.md>)

Topics: [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [Testcontainers](<https://devfeed.tech/topics/testcontainers.md>), [mutation-testing](<https://devfeed.tech/topics/mutation-testing.md>), [Unit testing](<https://devfeed.tech/topics/unit-testing.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [claude](<https://devfeed.tech/tags/claude.md>), [cli](<https://devfeed.tech/tags/cli.md>), [container](<https://devfeed.tech/tags/container.md>), [containers](<https://devfeed.tech/tags/containers.md>), [crud](<https://devfeed.tech/tags/crud.md>), [database](<https://devfeed.tech/tags/database.md>), [database-schema](<https://devfeed.tech/tags/database-schema.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-container](<https://devfeed.tech/tags/docker-container.md>), [drizzle](<https://devfeed.tech/tags/drizzle.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [schema](<https://devfeed.tech/tags/schema.md>), [testcontainers](<https://devfeed.tech/tags/testcontainers.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tests](<https://devfeed.tech/tags/tests.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [unit-tests](<https://devfeed.tech/tags/unit-tests.md>)

### AI overview

For complex data access logic, an isolated database integration test can verify that real inserts and queries preserve the expected object structure. The article uses `@testcontainers/postgresql` to start a temporary Postgres container in Vitest, applies a Drizzle schema with `drizzle-kit push`, and exercises workout insertion and retrieval through the application's actual code. A round-trip assertion catches errors in joins, writes, or ordering without tying the test to particular table rows, which the author says makes it less fragile to schema changes. The tradeoff is setup time: the suite takes over a second to start, and Docker must be available locally; GitHub Actions Ubuntu runners are said to include it. The author recommends reserving this approach for meaningful, non-trivial database logic rather than basic CRUD tests.

### Source excerpt

Testing data access code has always been awkward: unit tests want to be fast and isolated, and a real database is neither. With Docker and @testcontainers you can spin up a throwaway Postgres inside your Vitest suite, push your Drizzle schema into it, and verify that your real insert and query code round-trips correctly.

[Next page](<https://devfeed.tech/topics/integration-testing.md?cursor=WyIyMDI2LTExLTA0VDEyOjU4OjA1KzAwOjAwIiwgImM0ZWFjMGVjLWRkNzEtNDQ1Ni05MTQ3LTE4NGQzN2VjZjZmOCJd>)