# test Published articles for test. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## AI Agent Governance: Why It Belongs in Your Platform DevFeed: [AI Agent Governance: Why It Belongs in Your Platform]() Original publisher: [Read original article]() Author: Prateek Mittal Published: 2026-09-16T20:28:57.610955Z Content type: article Language: en Sources: [Harness Blog]() Topics: [AI Agent](), [Artificial Intelligence](), [observability](), [audit](), [test](), [Deployment](), [Monitoring](), [pull-requests]() Tags: [ai](), [ai-agent](), [audit](), [deployment](), [governance](), [monitoring](), [observability](), [pull-requests](), [test]() ### AI overview Engineering leaders from Yelp, Platformable, and Harness argue that AI agent governance must be automated, continuously enforced, and built into the platform rather than left to policy documents. The article discusses audit trails, agent-to-agent access controls, experiment tracking, testing, latency monitoring, rollback paths, and observability for agent-driven changes. ### Source excerpt Engineering leaders from Yelp, Platformable, and Harness explain why AI agent governance has to be built into the platform, not a policy doc. | Blog ## Scheduling gRPC and GraphQL Requests with Postman Monitors (Beta) DevFeed: [Scheduling gRPC and GraphQL Requests with Postman Monitors (Beta)]() Original publisher: [Read original article]() Author: Harsh Vardhan Published: 2026-09-16T16:00:00Z Content type: tutorial Language: en Sources: [Postman Blog]() Topics: [gRPC](), [Postman](), [Monitoring](), [Authentication]() Tags: [beta](), [general](), [graphql](), [graphql-monitoring](), [how-to](), [monitor-grpc-streaming](), [monitoring](), [monitors](), [postman](), [postman-monitors-grpc-graphql](), [scheduling](), [test]() ### AI overview This tutorial explains how to schedule gRPC and GraphQL requests with Postman Monitors in beta. It covers supported request types, streaming caveats, response testing, authentication, and current feature limitations. ### Source excerpt Postman Monitors now run gRPC and GraphQL requests in beta. Learn how to schedule them, test responses, and send feedback. Start monitoring today. The post Scheduling gRPC and GraphQL Requests with Postman Monitors (Beta) appeared first on Postman Blog. ## Quiz: Python's Mutable vs Immutable Types: What's the Difference? DevFeed: [Quiz: Python's Mutable vs Immutable Types: What's the Difference?]() Original publisher: [Read original article]() Author: Real Python Published: 2026-09-16T12:00:00Z Content type: tutorial Language: en Sources: [Real Python]() Topics: [Python](), [gotchas]() Tags: [gotchas](), [python](), [test](), [tutorial]() ### AI overview An interactive 12-question quiz tests understanding of Python's mutable and immutable types, including built-in type categories and common mutability issues such as variable aliasing, mutable default arguments, and shallow copies. ### Source excerpt Find out how Python's mutable and immutable types behave, and see how mutability shapes lists, tuples, dictionaries, and your own classes. ## 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 ## How to upgrade hundreds of React components without breaking production DevFeed: [How to upgrade hundreds of React components without breaking production]() Original publisher: [Read original article]() Author: Khan Academy Published: 2019-09-23T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [React](), [Design system](), [upgrade](), [Accessibility](), [consistency](), [test](), [Deployment](), [Code]() Tags: [accessibility](), [components](), [consistency](), [deployment](), [design-system](), [engineering](), [how-to](), [news](), [production](), [react](), [test](), [upgrade](), [web-frontend]() ### AI overview This article explains how Khan Academy upgraded hundreds of React buttons and links to components from its Wonder Blocks design system. It describes using a prop-conversion guide, organizing small team-owned changes, deploying often, and validating the migration with detailed test plans and responsive screenshots. ### Source excerpt By Jangmi Jo Background In 2018, we started renewing our color system using our new shared design system, ... 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 ## 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. ## The Default Deny Dilemma: A Practical Guide to Kubernetes Network Policies DevFeed: [The Default Deny Dilemma: A Practical Guide to Kubernetes Network Policies]() Original publisher: [Read original article]() Author: Wellingtone Luvonga Published: 2026-09-08T03:00:00Z Content type: tutorial Language: en Sources: [CYBERTEC PostgreSQL | Services & Support]() Topics: [Kubernetes](), [Network](), [Security](), [Zero Trust](), [Architecture & Design]() Tags: [blog](), [cni](), [container](), [guide](), [how-to](), [ingress](), [kubernetes](), [network](), [network-security](), [postgersql](), [security](), [test](), [yaml](), [zero-trust]() ### AI overview A hands-on lab for implementing zero-trust network segmentation in Kubernetes with NetworkPolicies. It demonstrates default-deny rules, label-based ingress and egress permissions, DNS access, external API restrictions, and traffic validation in a three-tier frontend, backend, and PostgreSQL architecture enforced by Calico. ### Source excerpt This blog is a deep walkthrough about network policies in Kubernetes, read to know more. The post The Default Deny Dilemma: A Practical Guide to Kubernetes Network Policies appeared first on CYBERTEC PostgreSQL | Services & Support. ## ACEMAGIC Kron Mini K5 Review - Part 2: A $400 Intel Core 3 304 Wildcat Lake mini PC tested with Windows 11 Pro DevFeed: [ACEMAGIC Kron Mini K5 Review - Part 2: A $400 Intel Core 3 304 Wildcat Lake mini PC tested with Windows 11 Pro]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-06T07:34:36Z Content type: comparison Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Intel Core](), [pc](), [Windows 11](), [intel](), [cpu]() Tags: [2-5gbe](), [3dmark](), [4k](), [8k](), [artificial-intelligence-ai](), [benchmarks](), [ethernet](), [geekbench](), [hardware](), [intel-core](), [mini-pc](), [mini-pcs](), [passmark](), [pcmark](), [review](), [reviews](), [test](), [testing](), [wifi-6](), [wildcat-lake](), [windows-11](), [youtube]() ### AI overview This review tests the ACEMAGIC Kron Mini K5, an Intel Core 3 304 Wildcat Lake mini PC running Windows 11 Pro. It covers system and AI benchmarks, 4K and 8K Firefox video playback, 2.5GbE and Wi-Fi 6 throughput, thermal performance, fan noise, and power consumption. ### Source excerpt After checking out the hardware of the ACEMAGIC Kron Mini K5 with an unboxing and a teardown in the first part of the review, we've now had time to test the Intel Core 3 304 Wildcat Lake mini PC in more depth with Windows 11 Pro. So in this article, we'll report our experience with the penta-core mini PC, testing features, running system and AI benchmarks, playing 4K and 8K YouTube videos on Firefox, measuring network throughput (2.5GbE and WiFi 6), evaluating thermal performance, and measuring fan noise and power consumption. Software overview and feature testing The System > About window confirms we have a 1.5 GHz (base frequency) Intel Core 3 304 computer paired with 12GB of RAM and 477GB of storage, running Windows 11 Pro 25H2 build 26200.9168. HWiNFO 64 provides additional details about the 15W Intel Core 3 304 penta-core (1P+4E) Wildcat Lake-U processor, the motherboard with [...] The post ACEMAGIC Kron Mini K5 Review - Part 2: A $400 Intel Core 3 304 Wildcat Lake mini PC tested with Windows 11 Pro appeared first on CNX Software - Embedded Systems News. ## An RTOS for Ages Two and Up -- Zephyr Podcast #049 DevFeed: [An RTOS for Ages Two and Up -- Zephyr Podcast #049]() Original publisher: [Read original article]() Author: Benjamin Cabé Published: 2026-09-04T20:01:01Z Content type: article Language: en Sources: [Zephyr Project]() Topics: [Embedded Software Dev](), [Testing](), [Arduino](), [Hardware](), [Maintainers](), [GitHub](), [Robotics](), [Wi-Fi]() Tags: [arduino](), [blog](), [engineering](), [firmware](), [github](), [halow](), [hardware](), [harness](), [maintainers](), [open](), [podcast](), [robotics](), [test](), [zephyr]() ### AI overview Zephyr Podcast episode 049 covers open-firmware hardware that does not yet run Zephyr, hardware-in-the-loop testing with Twister's pytest harness, project growth and contributors, Arduino Core for Zephyr 1.0, maintainer news, new drivers and subsystems, Wi-Fi HaLow support, and Zephyr's robotics community. ### Source excerpt The Dato DUO and the Teenage Engineering catalogue: lovely open-firmware noise machines that do not run Zephyr ...yet! Using the pytest harness in Twister to coordinate a device under test... ## 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 ## Auditing an AI setup and keeping key components independent of providers DevFeed: [Auditing an AI setup and keeping key components independent of providers]() Original publisher: [Read original article]() Author: Nate Published: 2026-09-02T13:01:35Z Content type: opinion Language: en Sources: [Nate's Substack]() Topics: [Artificial Intelligence](), [audit](), [prompt](), [test]() Tags: [ai](), [audit](), [plan](), [prompt](), [setup](), [test]() ### AI overview The article discusses a $600-plus AI setup, components kept outside individual providers, and a test used to evaluate expensive plans. ### Source excerpt My $600-plus AI setup, what I keep outside every provider, and the test each expensive plan has to pass. ## Implicit Assertions Are More Readable DevFeed: [Implicit Assertions Are More Readable]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-09-01T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [test](), [API](), [properties]() Tags: [api](), [cypress](), [how-to](), [products](), [properties](), [test]() ### AI overview A tutorial on making Cypress API tests more readable by using descriptive assertions, precise value ranges, implicit assertions, and cy-spok for validating nested response objects. ### Source excerpt Recently I saw a Linkedin post that shows "b ## Examining the artifacts job of a Playwright GitLab CI / CD pipeline DevFeed: [Examining the artifacts job of a Playwright GitLab CI / CD pipeline]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-29T23:19:22Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [Playwright](), [GitLab](), [CI/CD Pipeline](), [CI/CD](), [test]() Tags: [bun-create-playwright](), [ci-cd](), [ci-cd-pipeline](), [gitlab](), [playwright](), [screenshots](), [test](), [trace](), [videos]() ### AI overview This tutorial examines how a Playwright GitLab CI/CD pipeline stores and exposes test artifacts. It explains the playwright-report, test-results, and reports/junit folders and describes generated HTML and JUnit reports, screenshots, videos, and trace reports. ### Source excerpt You may have noticed that in the GitLab CI / CD Pipeline for our Playwright project, in the .gitlab-ci.yml file, after our scripts has run, in the Test stage, there is a subsection called "artifacts" with certain paths to something called "playwright-report", "test-results", and "reports". The Playwright -> Artifacts -> Reports stage playwright: extends: .bun_playwright stage: test timeout: 30 minutes ... ... artifacts: when: always paths: - playwright-report/ - test-results/ - reports/ reports: junit: reports/junit/results.xml expire_in: 30 days https://gitlab.com/tjmaher/bun-create-playwright/-/blob/main/.gitlab-ci.yml Every time Playwright tests run, it generates proof of the test execution: screenshots capturing the state of the UI when a test failed, video recordings of an entire browser session, HTML and JUnit XML test reports, trace reports showing action logs, network requests. These artifacts, when the tests run locally, are placed by the Playwright Test runner in generated folders, playwright-report and test-results, along with a folder called reports/junit. With this post, we will be examining how this artifacts stage of the GitLab CI/ CD pipeline produces downloadable artifacts we can examine. Playwright-Report: A Playwright Test folderThe Playwright Test runner creates a folder called "playwright-report", if it doesn't already exist, and an HTML file called index.html documenting the completed test run. From Playwright.dev / Test Reporters: "Playwright Test comes with a few built-in reporters for different needs and ability to provide custom reporters. [...] All built-in reporters show detailed information about failures, and mostly differ in verbosity for successful runs. [...] HTML reporter produces a self-contained folder that contains report for the test run that can be served as a web page". The HTML Report is the one that automatically opens after you run your tests locally, or if you are using the node package manager: npx playwright show-report ## AI Coding Tip 034 - Stop Hoarding Rules in Your AGENTS.md DevFeed: [AI Coding Tip 034 - Stop Hoarding Rules in Your AGENTS.md]() Original publisher: [Read original article]() Author: Maxi Contieri Published: 2026-08-28T18:10:58Z Content type: tutorial Language: en Sources: [Maximiliano Contieri - Software Design]() Topics: [ai-coding](), [coding](), [Code]() Tags: [agents](), [ai-coding](), [coding](), [context](), [developer](), [how-to](), [mcp](), [skills](), [test]() ### AI overview The article advises developers to regularly audit AGENTS.md files and skills, remove rules that no longer matter, and test whether instructions still improve agent performance. It highlights context bloat, stale skills, dead MCP servers, plugins, and hooks as ongoing maintenance costs. ### Source excerpt TL;DR: Audit your AGENTS.md and skills on a schedule, or you keep paying context rent on rules the model has outgrown. Common Mistake ❌ Every time the AI does something wrong, you add a rule to stop ## Keeping Documentation Honest with an OpenAPI Snapshot Diff DevFeed: [Keeping Documentation Honest with an OpenAPI Snapshot Diff]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-08-25T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [OpenAPI Specification](), [FastAPI](), [ci](), [Pytest](), [Documentation](), [JSON](), [test]() Tags: [api-documentation](), [ci](), [ci-cd](), [documentation](), [fastapi](), [json](), [openapi](), [pytest](), [test](), [testing]() ### AI overview The article explains how to keep API documentation aligned with a FastAPI application by generating its OpenAPI schema from the running code, comparing it with a committed snapshot in CI, normalizing the JSON diff, and requiring deliberate snapshot regeneration. ### Source excerpt FastAPI app.openapi() snapshot test in pytest: fail CI when the live OpenAPI schema drifts from the committed openapi.snapshot.json. ## Setting up a CI/ CD pipeline with GitLab: Quality, Test and Report DevFeed: [Setting up a CI/ CD pipeline with GitLab: Quality, Test and Report]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-25T02:28:52Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [CI/CD Pipeline](), [GitLab](), [Testing](), [Playwright](), [pull-requests](), [TypeScript]() Tags: [bun-create-playwright](), [ci-cd](), [ci-cd-pipeline](), [code-reviews](), [gitlab](), [playwright](), [test](), [testing](), [typescript](), [workflows]() ### AI overview A tutorial on setting up a three-stage GitLab CI/CD pipeline for merge requests. The pipeline runs code-quality checks, smoke and regression tests, and produces a downloadable report, with stages executed sequentially and jobs within each stage running in parallel. ### Source excerpt So far, we have reviewed how to review code with ES Lint + Prettier and Typecheck, how to set up and run smoke tests, how to run all Playwright + TypeScript tests, and reviewed the HTML report of results. In this post, we are going to set up a three stage GitLab CI/ CD pipeline that will run against every merge request: Quality (lint, typecheck, prettier) --> Test ( smoke + regression ) --> Report ( Downloadable ) I haven't used GitLab since when I worked at ThreatStack back in 2020. ( See my blog entry Getting to Know GitLab and How They Test the UI ) GitLab reads .gitlab-ci.yml from the repository root and turns it into a pipeline, a set of jobs, grouped into stages, running whenever you push a change to a repository. Stages run one after another, and jobs within a stage run in parallel. If one stage fails, the stages after it are skipped. This begs the question: What is GitLab? What is CI/ CD? Or a pipeline? Or a merge request? What is GitLab? GitLab began in 2011 as a side project by Ukrainian programmer Dmytro Zaporozhets, built to help developers work together on code more easily. Over time, it grew into a large open-source DevOps platform. More than just storing code, it handles code reviews, CI/CD (continuous integration and continuous delivery), and package registries. A company called GitLab Inc. was eventually created to turn the project into a commercial product. What makes GitLab different from tools that only host Git repositories (like a basic Git server) is that it bundles the entire software delivery process into one application. This includes: Merge requests - GitLab's term for proposing and reviewing code changes before they're merged into the main codebase (similar to a "pull request" in GitHub) Issue tracking - a built-in system for logging bugs, tasks, and feature requests Pipelines - automated workflows that build, test, and deploy code whenever changes are pushed So instead of stitching together separate tools for version control, testing, an ## Glamsterdam Repricing Impact for Smart Contract Developers DevFeed: [Glamsterdam Repricing Impact for Smart Contract Developers]() Original publisher: [Read original article]() Author: Ethereum Foundation Protocol Research; EthPandaOps; and Specifications teams Published: 2026-08-24T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Solidity](), [Transactions]() Tags: [developers](), [ethereum](), [research-development](), [smart-contract](), [test](), [upgrade]() ### AI overview The upcoming Glamsterdam upgrade will reprice Ethereum state creation and access through EIP-8037 and EIP-8038. Historical transaction replays found that most contracts are unaffected, while some may require preventative updates or higher gas limits. ### Source excerpt ... ## How to Configure Playwright Test to run smoke tests, headed tests, and debug versions through scripts in package.json DevFeed: [How to Configure Playwright Test to run smoke tests, headed tests, and debug versions through scripts in package.json]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-20T02:13:32Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [Playwright](), [Script](), [Bun](), [Smoke Tests](), [test](), [Package manager]() Tags: [bun](), [bun-create-playwright](), [commands](), [gitlab](), [how-to](), [install](), [playwright](), [test](), [tests]() ### AI overview A tutorial on configuring Playwright Test commands in package.json scripts. It demonstrates shortcuts for headed, traced, Chromium, Firefox, WebKit, smoke, debugging, reporting, linting, formatting, and type-checking workflows, and explains using Bun and bunx to run commands. ### Source excerpt Earlier, we went over how we could create scripts in the package.json file of our Playwright framework to add typechecking, linting, and formatting your code with prettier. Want to see the entire bun-create-playwright project? It is on tinyurl.com/bun-create-playwright! With this post, we will explore how the built-in test runner for Playwright Test can run headed tests, debug versions of tests, and smoke tests. ... and shortcuts for all of these can be set up in the scripts in your package.json! If you are using "bun" as a package manager, as we are in bun-create-playwright, just type out "bun run", a space and then the shortcut such as: bun run test package.json "scripts": { "test": "playwright test", "test:headed": "playwright test --headed", "test:trace": "playwright test --trace on", "test:chromium": "playwright test --project=chromium", "test:firefox": "playwright test --project=firefox", "test:webkit": "playwright test --project=webkit", "test:smoke": "playwright test --project=chromium --grep '@smoke'", "test:flaky": "playwright test --project=chromium --repeat-each=20", "test:ui": "playwright test --ui", "test:debug": "playwright test --debug", "test:failed": "playwright test --last-failed", "test:login": "playwright test tests/login.spec.ts", "test:secure-area": "playwright test tests/secure-area.spec.ts", "report:list": "playwright test --reporter=list", "report:line": "playwright test --reporter=line", "report:dot": "playwright test --reporter=dot", "report:blob": "playwright test --reporter=blob", "report": "playwright show-report", "codegen": "playwright codegen", "lint": "eslint .", "lint:ci": "eslint . --max-warnings 0", "lint:fix": "eslint . --fix", "format": "prettier --write .", "format:check": "prettier --check .", "format:debug": "prettier --check . --log-level debug", "format:diff": "prettier --list-different", "typecheck": "tsc --noEmit" }, bun-create-playwright / package.json Do you need to really set up shortcuts like these? Certainly not! B ## Build a dependency-graph inventory before changing the container DevFeed: [Build a dependency-graph inventory before changing the container]() Original publisher: [Read original article]() Published: 2026-08-18T00:00:00Z Content type: tutorial Language: en Sources: [Koin - Cloud-Inject.io -Kotzilla]() Topics: [Dependency injection](), [Android](), [test](), [Gradle]() Tags: [android](), [build](), [configuration](), [dependency](), [graph](), [process](), [test]() ### AI overview This tutorial recommends creating a framework-independent dependency-graph inventory before migrating dependency injection. It explains how to document entry points, ownership, implementations, lifetimes, qualifiers, modules, replacement values for tests, and architectural constraints, then validate the design through smaller executable test slices. ### Source excerpt A dependency-injection migration often starts with framework syntax. That is too late. First describe the graph without using the framework's vocabulary. The inventory should show which objects exist, who owns them, and which runtime fact selects one implementation over another. Start from entry points List application entry points: the Android application, a worker, a navigation destination, a command-line process, and each test fixture. Trace the objects requested at each entry point. Stop the trace at explicit boundaries such as a database driver, HTTP transport, clock, file system, or platform service. ## Keep Kotlin Multiplatform bindings at the platform boundary DevFeed: [Keep Kotlin Multiplatform bindings at the platform boundary]() Original publisher: [Read original article]() Published: 2026-08-18T00:00:00Z Content type: tutorial Language: en Sources: [Koin - Cloud-Inject.io -Kotzilla]() Topics: [Kotlin Multiplatform](), [Kotlin](), [implementation](), [modules](), [configuration](), [test]() Tags: [configuration](), [implementation](), [kotlin](), [kotlin-multiplatform](), [module](), [multiplatform](), [test](), [verification]() ### AI overview A guide to keeping Kotlin Multiplatform dependency bindings at platform boundaries. It recommends defining small capability interfaces in common code, implementing them in platform source sets, organizing modules around capabilities and product features, and testing both shared contracts and real platform bindings. ### Source excerpt Kotlin Multiplatform makes source-set boundaries visible, but a dependency container can blur them again. A shared module should state a capability such as secure storage, HTTP transport, or local time. The platform source set should supply the implementation. Put contracts where consumers can see them Define the smallest useful interface in common code. Avoid copying a platform API into that interface. A storage contract might expose read, write, and remove; it does not need to expose Android preferences or an Apple keychain type. ## Review a Koin upgrade as a graph change, not a version bump DevFeed: [Review a Koin upgrade as a graph change, not a version bump]() Original publisher: [Read original article]() Published: 2026-08-18T00:00:00Z Content type: tutorial Language: en Sources: [Koin - Cloud-Inject.io -Kotzilla]() Topics: [Dependency injection](), [upgrade](), [modules](), [test](), [Compose]() Tags: [android](), [compose](), [dependency-injection](), [modules](), [test](), [upgrade]() ### AI overview This tutorial explains how to review a Koin dependency-injection upgrade as an architecture change rather than a simple version bump. It recommends recording the existing dependency graph, modules, warnings, startup results, and verification output; upgrading mechanisms separately; checking all startup variants; and maintaining tested rollback procedures. ### Source excerpt Dependency-injection upgrades can change more than API names. Verification behavior, annotation processing, Compose packages, compiler integration, and deprecations can all alter how the graph is built. Treat the upgrade as an architecture change with a defined before-and-after record. Freeze the current graph Before changing versions, save the dependency lock or resolved graph, the list of DI modules, startup smoke-test results, and verification-test output. Record warnings that already exist so a new warning is not confused with old noise. ## Find technical debt at dependency-injection boundaries DevFeed: [Find technical debt at dependency-injection boundaries]() Original publisher: [Read original article]() Published: 2026-08-18T00:00:00Z Content type: article Language: en Sources: [Koin - Cloud-Inject.io -Kotzilla]() Topics: [Dependency injection](), [Framework](), [Code]() Tags: [architecture](), [defects](), [dependency-injection](), [errors](), [review](), [structure](), [technical](), [test](), [tests]() ### AI overview This article explains how dependency-injection code can expose architectural debt. It identifies signals such as oversized modules, string qualifiers, lifetime inversion, construction that starts work, broad production-container tests, and definitions spread across UI locations. It recommends paying down debt at product-slice boundaries, separating construction from behavior, adding focused graph and behavior tests, and measuring ownership, verification, startup, and test setup. ### Source excerpt Dependency-injection code is often treated as plumbing. It is also a compact map of architecture decisions. Review it for debt signals before adding another binding. Signals worth investigating An oversized application module usually means feature boundaries are not explicit. String qualifiers can hide a missing type. Definitions that open databases or start jobs during graph creation mix construction with behavior. A process-scoped object that accepts a screen-owned dependency indicates lifetime inversion. ## Implementing Page Objects in Playwright DevFeed: [Implementing Page Objects in Playwright]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-16T22:04:38Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [Playwright](), [selectors](), [test](), [Development]() Tags: [bun](), [bun-create-playwright](), [code](), [gitlab](), [jest](), [page-object](), [playwright](), [selectors](), [test](), [tests]() ### AI overview A tutorial on using Playwright page objects to organize web application tests, centralize selectors, reduce repetition, and simplify maintenance. It compares Playwright Test and Library approaches and demonstrates setting up a login-page object. ### Source excerpt Picture a login screen, such as The-Internet / Login. On this LoginPage, there is: a heading: Login Page a user name textbox with the label, "Username" a password textbox with the label, "Password" a login button, with the role of a button, and the name of "Login" a flash message that appears if you enter invalid credentials such as "NotAUser" and "NotAPassword". If you successfully log in with "tomsmith" and "SuperSecretPassword!, there is a SecureArea: a heading: "Secure Area" a flash message "You logged into a secure area!" a Logout button. Sure, you could interact with each web element in your test... but what if the username text box locator changes? You would have to update multiple tests every time the element changed. ... Instead, you could place it in a Page Object, something that Playwright handles well! "A page object represents a part of your web application. An e-commerce web application might have a home page, a listings page and a checkout page. Each of them can be represented by page object models. "Page objects simplify authoring by creating a higher-level API which suits your application and simplify maintenance by capturing element selectors in one place and create reusable code to avoid repetition". Using Playwright's Built-In Test Runner? Or Something Else? You may have noticed in https://playwright.dev/docs/pom that there are two different styles of page objects. One for "Test". One for "Library". Test: If you are writing actual Playwright test suites, and Playwright's built in test runner, use the Test section as a guide when creating page objects. Library: If you are integrating Playwright into an existing test framework such as Jest or Cucumber and just want browser automation, instead of having pre-built page fixtures, etc, you can use this format. Setting Up Page Objects Let's review a page object I created for the main login page on my GitLab account for the bun-create-typescript project, tests/pages/LoginPage.ts. The first thing we do is [Next page]()