# Tests Published articles for Tests. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Why human oversight is shifting from writing code to defining requirements DevFeed: [Why human oversight is shifting from writing code to defining requirements]() Original publisher: [Read original article]() Author: Naseeb Ahmed Mian Published: 2026-09-17T13:00:00Z Content type: opinion Language: en Sources: [The New Stack]() Topics: [Requirements](), [AI Agent](), [Code](), [Availability]() Tags: [agent](), [agents](), [ai-agents](), [ai-engineering](), [andela](), [automated](), [availability](), [code](), [pipeline](), [post-contributed](), [requirements](), [review](), [software-development](), [sponsor-andela](), [sponsored-post-contributed](), [tests]() ### AI overview The article argues that human oversight of AI-assisted software development should focus on defining and reviewing requirements, not only checking whether generated code conforms to them. It illustrates the risk with a flawed availability-related requirement that passed specification review, generated six passing tests, traceability checks, and automated QA while violating the feature's intended outcome. ### Source excerpt This walks through the pipeline our agents operate inside--from a recorded scoping meeting through unit specs, spec review, generated code, The post Why human oversight is shifting from writing code to defining requirements appeared first on The New Stack. ## Write End-to-End Tests in Your Backend's Language DevFeed: [Write End-to-End Tests in Your Backend's Language]() Original publisher: [Read original article]() Author: James McConkey Published: 2026-09-17T12:00:42Z Content type: tutorial Language: en Sources: [Atomic Object]() Topics: [Testing](), [Playwright](), [FastAPI](), [Python](), [test data](), [Pydantic](), [SQLAlchemy](), [ASP.NET Core](), [PostgreSQL](), [Docker Compose]() Tags: [asp-net-core](), [code](), [data](), [docker-compose](), [fastapi](), [playwright](), [postgresql](), [project-team-management](), [python](), [sqlalchemy](), [tests](), [the-software-life]() ### AI overview This article argues that end-to-end test-data setup is often the main design challenge, because tests must create consistent domain records while running alongside other tests. It recommends using browser-testing tools in the backend's language when possible, keeping meaningful relationships inline, and extracting small creation helpers without hiding scenario intent. ### Source excerpt The browser is often the easiest part of an end-to-end test. Consider a test that verifies a user can complete an overdue task. The visible interaction is small: sign in, find the task, click Complete, and observe the new status. Before any of that can happen, the test needs a workspace, a user, a project, and [...] The post Write End-to-End Tests in Your Backend's Language appeared first on Atomic Spin. ## Profiling App Engine Memcached DevFeed: [Profiling App Engine Memcached]() Original publisher: [Read original article]() Author: Khan Academy Published: 2017-05-01T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Latency](), [Logging](), [Data structures]() Tags: [engineering](), [infrastructure](), [latency](), [logging](), [memcached](), [news](), [patterns](), [profiling](), [tests]() ### AI overview Khan Academy engineers profile App Engine Memcached to estimate access latency and evaluate whether on-demand content fetching could support separate content trees for each language. Most requests showed 1-4 ms latency, usually below 10 ms, while a single multi-get performed similarly to a single get. ### Source excerpt By Ben Kraft Last year, Willow wrote about how we optimized our in-memory content data to take up ... Read more ## Babel in Khan Academy's i18n Toolchain DevFeed: [Babel in Khan Academy's i18n Toolchain]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-06-22T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [Babel](), [Internationalization (i18n)](), [toolchain](), [es6](), [JavaScript](), [Parser](), [Universal Syntax Tree.](), [Open Source]() Tags: [api](), [architecture](), [babel](), [build](), [build-system](), [code](), [engineering](), [es6](), [eslint](), [frontend](), [javascript](), [news](), [plugin](), [source](), [structure](), [syntax](), [tests](), [toolchain](), [types](), [web-frontend](), [workflow]() ### AI overview Khan Academy describes switching its ES6 and JSX frontend compilation from jstransform to Babel. The article explains a custom Babel plugin for preserving the project's internationalization behavior and discusses matching generated output, line numbers, whitespace, and the existing build chain. ### Source excerpt By Kevin Barabash We've been using ES6 (along with JSX) for sometime at Khan Academy. Right now, we're ... Read more ## The Autonomous Dumbledore DevFeed: [The Autonomous Dumbledore]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-04-25T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [API](), [Job](), [test](), [maintenance](), [Code]() Tags: [api](), [bugs](), [engineering](), [feature](), [fetch](), [job](), [maintenance](), [news](), [running](), [scheduled](), [test](), [tests](), [web-frontend]() ### AI overview An intern at Khan Academy describes the Autonomous Dumbledore, a system that monitors PSAT score-linking endpoints through recurring tests and automatically enables or disables the related feature based on recent results. ### Source excerpt By Evy Kassirer When I arrived at Khan Academy to start my internship on the Official SAT Practice ... Read more ## Starting Android at Khan Academy DevFeed: [Starting Android at Khan Academy]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-02-29T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Android](), [android-development](), [Development](), [Library](), [modules](), [ci](), [Mocking]() Tags: [android](), [android-development](), [development](), [engineering](), [libraries](), [mobile](), [mocking](), [module](), [modules](), [news](), [open-source](), [picasso](), [play-store](), [pre-commit](), [retrofit](), [test](), [tests]() ### AI overview Khan Academy describes its first Android app, launched in August 2015, and the engineering practices used to build it. The team adopted established Android and open-source libraries, separated Android-independent core code from the app module, and used fast JVM tests and continuous integration. ### Source excerpt By Ben Komalo The journey of a thousand miles... In March, 2015--almost 1 year ago to the day--we ... Read more ## tota11y - an accessibility visualization toolkit DevFeed: [tota11y - an accessibility visualization toolkit]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-06-08T22:00:00Z Content type: release Language: en Sources: [Khan Academy]() Topics: [Accessibility](), [audit](), [Testing](), [Tooling](), [browser](), [Chrome]() Tags: [accessibility](), [accessibility-testing](), [audit](), [browser](), [chrome](), [developer-tools](), [engineering](), [frontend](), [linter](), [news](), [testing](), [tests](), [tooling](), [unit-tests](), [visualization](), [web](), [web-frontend]() ### AI overview Khan Academy announces tota11y, an accessibility visualization toolkit designed to make manual accessibility testing easier for developers. The article describes its development and use of browser-based annotations to help teams understand and fix accessibility issues. ### Source excerpt By Jordan Scales Today we're releasing tota11y (on GitHub), an accessibility visualization toolkit that aims to reduce the ... Read more ## Improving Test Coverage in the Interview Coach Application with GitHub Copilot DevFeed: [Improving Test Coverage in the Interview Coach Application with GitHub Copilot]() Original publisher: [Read original article]() Author: Aaron Powell Published: 2026-09-15T16:00:21Z Content type: tutorial Language: en Sources: [Visual Studio Blog]() Topics: [test-coverage](), [Test coverage](), [GitHub Copilot](), [App](), [Visual Studio](), [Code]() Tags: [agent](), [analysis](), [code-coverage](), [copilot](), [github-copilot](), [productivity](), [projects](), [run](), [test](), [test-coverage](), [testing](), [tests](), [unit-tests](), [visual-studio]() ### AI overview This tutorial explains how to improve test coverage in the Interview Coach application by establishing a baseline, using GitHub Copilot's Test Agent to generate unit tests, and analyzing coverage across the solution. The article reports coverage increasing from 37% to 81%. ### Source excerpt Today I want to look at how we can improve on the test coverage that we have in the Interview Coach application. This application has some unit tests in it already, but I'm sure there is room for improvement. Defining our baseline Before we start writing tests, it's a good idea to have a baseline [...] The post Today I will... improve test coverage appeared first on Visual Studio Blog. ## How to Use Differential Testing During a Legacy Migration DevFeed: [How to Use Differential Testing During a Legacy Migration]() Original publisher: [Read original article]() Author: Hugo Teijiz Published: 2026-09-14T16:25:50Z Content type: tutorial Language: en Sources: [freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More]() Topics: [migration](), [Testing](), [TypeScript](), [Integration testing](), [API](), [observability](), [Artificial Intelligence]() Tags: [ai](), [api](), [architecture](), [artificial-intelligence](), [code](), [how-to](), [integration](), [legacy-code](), [legacy-modernization](), [migration](), [modernization](), [observability](), [software-architecture](), [software-testing](), [testing](), [tests](), [tutorial](), [typescript]() ### AI overview This tutorial explains how to use differential testing during a legacy migration by running old and new implementations with identical inputs and comparing their behavior. It covers equivalence rules, output normalization, nondeterministic values, errors, side effects, automated testing, mismatch analysis, production shadow traffic, and using AI to classify divergences without allowing it to determine correctness. ### Source excerpt The most dangerous moment in a legacy migration isn't necessarily when you start writing the new implementation. It's when the new implementation looks finished. The code compiles, the tests pass, the ## Agentic Engineering in Python: From Vibes to Evidence DevFeed: [Agentic Engineering in Python: From Vibes to Evidence]() Original publisher: [Read original article]() Author: Ben Batman Published: 2026-09-14T14:00:00Z Content type: tutorial Language: en Sources: [Real Python]() Topics: [Loop Engineering](), [AI Agent](), [Python](), [Transformers](), [Code review](), [Test-driven development]() Tags: [agentic](), [agentic-engineering](), [ai-coding-agents](), [cheat-sheet](), [code-review](), [learning](), [python](), [tests]() ### AI overview This tutorial presents agentic engineering in Python as a disciplined workflow for delegating bounded tasks to AI coding agents while retaining human control over intent, constraints, review, and release decisions. It explains execution and acceptance loops, the Engineering Evidence Ladder, and the RECAP review method for evaluating agent-generated changes with tests, type hints, refactoring, and code review. ### Source excerpt Move from vibe coding to agentic engineering in Python, using tests, types, and code review to prove an AI agent's changes are safe to keep. ## Datasette 1.0a39 and 0.65.4 security releases DevFeed: [Datasette 1.0a39 and 0.65.4 security releases]() Original publisher: [Read original article]() Author: Simon Willison Published: 2026-09-11T03:27:16Z Content type: release Language: en Sources: [Simon Willison's Weblog]() Topics: [releases](), [Security](), [audit](), [AI-assisted coding](), [ai security](), [agentic-engineering](), [Generative AI](), [Large Language Model](), [Claude](), [gpt-6-astra]() Tags: [agentic-engineering](), [agentic-engineering-63](), [ai](), [ai-2-236](), [ai-security-research](), [ai-security-research-42](), [coding-agents](), [datasette](), [datasette-1-542](), [generative-ai](), [generative-ai-1-982](), [llms](), [llms-1-948](), [releases](), [releases-31](), [security](), [security-634](), [tests]() ### AI overview Datasette 1.0a39 and 0.65.4 are security patch releases for the alpha and stable series. They address issues found during an extensive audit, including instances that mix public and private tables. The audit used Claude Fable 5.1, GPT-5.6, and GPT-6 Astra alongside human review and automated tests. ### Source excerpt Datasette 1.0a39 and 0.65.4 security releases Today we're releasing two new security patch versions of Datasette: 1.0a39 and 0.65.4 - one for the current alpha series and one for the stable 0.65.x family. These are security fixes which you should apply if you are running a Datasette instance on the public web - in particular if that instance mixes both public and private tables. Following issues reported by Sevban Dönmez, Alex Garcia and I ran an extensive audit of Datasette using Claude Fable 5.1, GPT-5.6, and GPT-6 Astra. We then spent almost a week collaborating on and reviewing the fixes. They helped find some very subtle bugs. We'll be incorporating security audits by frontier models into all of our development work going forward. Alex came up with a way of splitting the work which I found extremely productive: Alex Garcia and I worked together running and then responding to the audit, working in a shared private repository. For most of the issues we split the work: one of us would create the automated tests highlighting the issue, then the other would implement the fix. This ensured that two separate humans had eyes on each of the issues, in addition to our coding agents running different models. Tags: releases, security, ai, datasette, generative-ai, llms, agentic-engineering, ai-security-research ## Introducing Encore x Daytona DevFeed: [Introducing Encore x Daytona]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-09-08T00:00:00Z Content type: release Language: en Sources: [Encore Updates]() Topics: [AI-assisted coding](), [coding](), [Cloud]() Tags: [agents](), [coding-agents](), [infrastructure](), [sandbox](), [tests](), [tools]() ### AI overview Encore and Daytona provide coding agents with isolated, persistent sandboxes for building and verifying complete backends against local infrastructure that mirrors production declarations. ### Source excerpt Let your coding agents build and verify against real infrastructure, inside a sandbox. ## Refactoring Should NOT Touch Your Acceptance Tests DevFeed: [Refactoring Should NOT Touch Your Acceptance Tests]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-09-03T06:00:37Z Content type: opinion Language: en Sources: [Optivem Journal]() Topics: [Refactoring](), [Pull Request](), [test]() Tags: [change](), [dsl](), [refactor](), [refactoring](), [test](), [tests]() ### AI overview The article argues that a refactoring pull request should not change acceptance tests or their DSL, because doing so changes behavior rather than merely restructuring code. ### Source excerpt A "refactor" PR that changes the acceptance test or the DSL isn't a refactor -- it's a behavioral change ## Orchestrating Playwright test suites with Temporal for independent retries DevFeed: [Orchestrating Playwright test suites with Temporal for independent retries]() Original publisher: [Read original article]() Author: Simon Emms Published: 2026-09-03T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Playwright](), [Orchestration](), [ci](), [test]() Tags: [browsers](), [ci](), [orchestration](), [playwright](), [retry](), [temporal-voices](), [tests]() ### AI overview This article explores using Temporal to orchestrate Playwright end-to-end test suites as independent, durable units of work. The approach allows failed tests to retry independently while preserving progress instead of restarting the entire CI job. ### Source excerpt Learn how Temporal can orchestrate end-to-end test suites so failed tests retry independently, preserving progress without restarting the entire CI job. ## Mongorewind: Rewind Your MongoDB Test Data Without Restoring a Backup DevFeed: [Mongorewind: Rewind Your MongoDB Test Data Without Restoring a Backup]() Original publisher: [Read original article]() Author: Zelmar Michelini Published: 2026-09-02T11:38:40Z Content type: tutorial Language: en Sources: [Blog - Percona]() Topics: [MongoDB](), [Terminal](), [Command-line interface](), [ci](), [dashboards](), [Streams]() Tags: [ci](), [code](), [commands](), [database](), [mongodb](), [state](), [terminal](), [tests](), [ui]() ### AI overview This article introduces mongorewind, a terminal UI tool that records MongoDB data changes through a cluster-wide change stream and reverses them in reverse chronological order. It is designed to restore test data to its pre-test state without restoring a backup and supports interactive and CI use. ### Source excerpt Mongorewind: Rewind Your MongoDB Test Data Without Restoring a Backup One day, my friend Martín told me about a problem he and his team were dealing with. Every time they needed to run a pre-production test, they had to restore a copy of the production database into their test cluster. That process alone takes about ... Continued The post Mongorewind: Rewind Your MongoDB Test Data Without Restoring a Backup appeared first on Percona. ## Catch AI Regressions Before They Ship with AI Evals in CI/CD DevFeed: [Catch AI Regressions Before They Ship with AI Evals in CI/CD]() Original publisher: [Read original article]() Author: Shibam Dhar Published: 2026-09-02T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [AI Agent](), [CI/CD](), [Testing](), [AI Development]() Tags: [agent](), [ai](), [ai-agent](), [ai-evals](), [ci-cd](), [datasets](), [production](), [quality](), [tests]() ### AI overview Harness AI Evals uses golden datasets, response-quality metrics, and blocking quality gates in CI/CD to catch AI agent regressions before production. In an e-commerce support-agent test, an early run passed about 65% of cases, below the 70% deployment threshold, revealing incorrect, missing, or incomplete answers. ### Source excerpt Harness AI Evals tests AI agent quality in CI/CD, using golden datasets and quality gates to catch behavioral regressions before production. | Blog ## Cypress 16: faster tests, starting with HTTP/2 support DevFeed: [Cypress 16: faster tests, starting with HTTP/2 support]() Original publisher: [Read original article]() Published: 2026-09-01T17:28:34Z Content type: release Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Testing](), [HTTP](), [Chromium](), [Node.js](), [Streaming](), [Vite]() Tags: [chromium](), [ci](), [cypress](), [http](), [node-js](), [streaming](), [tests](), [vite]() ### AI overview Cypress 16 improves end-to-end test performance with HTTP/2 support, zero-delay typing, faster visibility checks, retrying cookie and storage commands, and automatic memory management. The release also updates Node.js, Electron, and Chromium versions and removes Cypress.env() as part of its security work. ### Source excerpt Cypress 16 goes after slow test suites from every angle: HTTP/2 support, zero-delay typing, faster visibility checks, retrying cookie commands, and automatic memory management. Most of it arrives without editing a single test. Here's what changed, why, and how to upgrade. ## Agents babysitting agents DevFeed: [Agents babysitting agents]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-31T18:26:02Z Content type: opinion Language: en Sources: [WorkOS Blog]() Topics: [Development](), [AI-assisted coding](), [Pull Request](), [Claude Code](), [Model Context Protocol (MCP)](), [Terminal](), [Monitoring](), [cursor]() Tags: [agent](), [agents](), [claude](), [claude-code](), [coding-agents](), [cursor](), [mcp](), [monitoring](), [pull-request](), [review](), [terminal](), [tests]() ### AI overview WorkOS engineers describe using one coding agent to supervise another after pull requests are opened, with headless monitoring, narrowly scoped jobs, visible costs, protected credentials, and human approval for merging. ### Source excerpt How WorkOS engineers make agents babysitting agents safe: a headless surface to supervise through, scoped jobs, visible costs, and a human on the merge button. ## How Developers Can Test Their Feature Branch Against Various Playwright Configurations Before Creating a Merge Request in GitLab CI/CD DevFeed: [How Developers Can Test Their Feature Branch Against Various Playwright Configurations Before Creating a Merge Request in GitLab CI/CD]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-28T20:18:08Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [GitLab](), [CI/CD](), [Playwright](), [YAML](), [Development]() Tags: [bun-create-playwright](), [chromium](), [ci-cd](), [firefox](), [gitlab](), [gitlab-ci](), [playwright](), [tests](), [yaml]() ### AI overview This tutorial shows how to configure a GitLab CI/CD pipeline so developers can test a feature branch before creating a merge request. It uses spec inputs in a YAML configuration to let users choose the branch, Playwright test suite, and browser, including Chromium, Firefox, WebKit, or all browsers. ### Source excerpt Developers need the option to test out their feature branch before merging it into main. In the last section, we set up a GitLab CI/CD Pipeline in our bun-create-playwright project to check every GitLab Merge Request. Now, we will be giving developers option to create a new pipeline where they can choose: Which feature branch to test against. Which test suite to execute (LoginPage tests? Secure Area? Or all of them?) Which Playwright browser to use: Chromium, Firefox, WebKit, or all. All these features can be set up using our .gitlab-ci.yaml file! Go to to bun-create-playwright, view the Pipelines section, and select the New Pipeline button. Run a New Bun-Create-Playwright Pipeline If you go to the Run new pipeline page at https://gitlab.com/tjmaher/bun-create-playwright/-/pipelines/new you can see the following default values I've set: https://gitlab.com/tjmaher/bun-create-playwright/-/pipelines/new By default: Branch name is "main", TEST_SUITE is "all", BROWSER is "all". ... But all these values can be set, with the developer choosing the options laid out in the .gitlab-ci.yaml file. Collect User Data With Spec Inputs We are going to be adding to the GitLab Pipeline we built in our last post Setting up a CI/ CD pipeline with GitLab: Quality, Test and Report. First, we are going to add a "spec" section to the header of the YAML file to define the behavior of a pipeline, and within that spec header, we will ask the person who triggered a new pipeline to set user defined inputs for the pipeline. spec: inputs: browser: description: "Browser project to run against." default: "all" options: ["all", "chromium", "firefox", "webkit"] suite: description: "Select full regression suite, or a single spec" default: "all" options: ["all", "login.spec.ts", "secure-area.spec.ts"] This is where we declare the "browser" and "suite" variables that appear when a user creates a new pipeline. We've given them a choice to run their feature branch code against: Browser: All, Chromium, Fir ## Handling Asynchronous Images in Android Screenshot Tests DevFeed: [Handling Asynchronous Images in Android Screenshot Tests]() Original publisher: [Read original article]() Author: Alex Zhukovich Published: 2026-08-27T07:41:23Z Content type: tutorial Language: en Sources: [Alex Zhuk - Android development and testing]() Topics: [Testing](), [Android](), [test](), [Compose]() Tags: [android](), [asynchronous](), [junit](), [screenshot-testing](), [tests]() ### AI overview This tutorial explains why asynchronous image loading makes Android screenshot tests unstable or inconsistent. It presents two approaches for deterministic results: injecting fake images with the coil-test library and using Compose inspection mode when the first approach is unavailable. ### Source excerpt This article is based on a chapter from my book, Mastering Android Screenshot Testing. Modern applications frequently load images asynchronously, which is a common cause of unstable screenshot tests or confusion when you review newly generated screenshots. A test can pass locally and fail on CI, produce a different image ## CircleCI Smarter Testing: Stop running tests that don't matter DevFeed: [CircleCI Smarter Testing: Stop running tests that don't matter]() Original publisher: [Read original article]() Author: Nathan Fish Published: 2026-08-26T19:00:00Z Content type: article Language: en Sources: [The CircleCI Blog Feed | CircleCI]() Topics: [Testing](), [CI/CD]() Tags: [accelerate](), [auto-rerun-failed-tests](), [ci-cd](), [circleci](), [circleci-news](), [developer-productivity](), [dynamic-test-splitting](), [engineering-productivity](), [flaky](), [intelligent-test-selection](), [parallel](), [pipeline](), [quality](), [reduce](), [smarter-testing](), [test-impact-analysis](), [testing](), [tests](), [time]() ### AI overview CircleCI describes Smarter Testing, a set of features designed to reduce CI/CD test execution time by skipping tests unaffected by changes, balancing parallel nodes, and retrying flaky tests. The article says early users have seen test runs up to four times faster. ### Source excerpt Testing eats up to half your pipeline time. See how CircleCI Smarter Testing skips unaffected tests, rebalances parallel nodes, and retries flaky tests. ## Harness RT Agents Detect Resilience Risks and Generate Tests for CD Pipelines and Kubernetes Workloads DevFeed: [Harness RT Agents Detect Resilience Risks and Generate Tests for CD Pipelines and Kubernetes Workloads]() Original publisher: [Read original article]() Author: Uma Mukkara Published: 2026-08-24T00:00:00Z Content type: release Language: en Sources: [Harness Blog]() Topics: [Resilience](), [Testing](), [Continuous Delivery (CD)](), [Kubernetes](), [dashboards]() Tags: [agentic](), [agents](), [blog](), [chaos](), [configuration](), [continuous-delivery](), [dashboards](), [deployment](), [experiments](), [infrastructure](), [insights](), [kubernetes](), [load](), [pipelines](), [product](), [resilience](), [services](), [teams](), [testing](), [tests]() ### AI overview Harness announces an update to Resilience Testing called RT Agents. The agents analyze CD pipelines and Kubernetes workloads for resilience risks, recommend the testing needed to confirm those risks, and can generate and run chaos experiments or load tests and interpret the results. ### Source excerpt RT Agents detect resilience risk in your CD pipelines and Kubernetes workloads, then generate and run chaos experiments or load tests to confirm it. | Blog ## How to prevent AI coding tools from hiding test failures DevFeed: [How to prevent AI coding tools from hiding test failures]() Original publisher: [Read original article]() Author: Maxi Contieri Published: 2026-08-23T19:31:15Z Content type: tutorial Language: en Sources: [Maximiliano Contieri - Software Design]() Topics: [ai-coding](), [coding](), [Code review]() Tags: [ai](), [ai-coding](), [code-review](), [coding](), [how-to](), [tests]() ### AI overview This tutorial explains how AI coding tools can appear to fix defects by deleting failing tests, reverting business-rule changes, or commenting out assertions. It recommends writing the failing test first, specifying expected behavior precisely, forbidding deletions and skips, and reviewing the diff. ### Source excerpt TL;DR: Write the failing test first and ban deletions, or the AI deletes your test, reverts your fix, and calls it done. Common Mistake ❌ You ask the AI to fix a failing test, and it deletes the test ## Designing Libraries and SDKs for Human Developers and Coding Agents DevFeed: [Designing Libraries and SDKs for Human Developers and Coding Agents]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-08-22T17:08:47Z Content type: opinion Language: en Sources: [The CommonsBlog]() Topics: [SDKs](), [AI-assisted coding](), [Agentic development](), [Documentation](), [test](), [Specifications]() Tags: [agentic](), [blog](), [coding-agents](), [documentation](), [open-source](), [sdk](), [sdks](), [specifications](), [tests]() ### AI overview This opinion article argues that library and SDK authors should support both human developers and coding agents. It recommends clear source-code comments, generated API documentation, robust and runnable test suites, coverage analysis, and language-neutral specifications with conformance tests to clarify intended behavior and support faithful ports. ### Source excerpt Let's explore how we can succeed with libraries and SDKs at a time when coding agents will be consuming what we create, as will ordinary developers [Next page]()