Automation
AI
Test Automation
Constellation Based Automation: Why automation needs the 'Milky Way' strategy

Constellation Based Automation: Why automation needs the 'Milky Way' strategy

December 28, 2025 3 min read
🎯

What You'll Learn

  • The "Milky Way" Strategy: Why navigating by universal constants beats looking at the ground
  • CBA vs POM: Why the Page Object Model is failing in the modern, chaotic web
  • The Starlight Protocol: Separating "Intent" from "Environment Maintenance"
  • Sentinels: Autonomous background agents (Janitors, Waiters, Historians) that heal your tests
  • Language Freedom: How to mix Python, Go, and Node.js in a single automation ecosystem
  • Hero Story Reporting: Visualizing the value of proactive self-healing

Ever felt like you're playing a perpetual game of whack-a-mole with your automation scripts? You write a perfect checkout test, and then—*bam*—a newsletter popup appears. An A/B test shifts a button. A slow API call causes a timeout. The result? Script Bloat. Your "5-line test" becomes a 50-line monster of `if/else` checks and explicit sleeps.

The Biological Inspiration: The Dung Beetle’s Secret

There is a species of dung beetle that can navigate thousands of miles in a perfectly straight line. It doesn't have a map. It doesn't know where every rock or hole is. It simply looks up at the Milky Way. By orienting itself to a "Universal Constant" that never changes, it can overcome any obstacle on the ground without getting lost.

Ground-Lookers vs. Star-Navigators
Most automation frameworks fail because they are "Ground-Lookers." They are obsessed with the DOM. When the ground shifts, the test dies. Constellation-Based Automation (CBA) teaches your tests to look up.

Why the Page Object Model is Dying

The Page Object Model (POM) was built for a simpler web. Today’s web is chaotic, asynchronous, and filled with "Noise." In a typical POM setup, the test script is a micro-manager. It spends 90% of its time on environment maintenance rather than business logic.

FeaturePage Object Model (POM)Constellation-Based Automation (CBA)
Logic TypeImperative: You code the "How"Reactive: You code the "What"
Handling PopupsManual `if/else` checksAutomatic (The Janitor Sentinel)
MaintenanceUpdate dozens of Page ObjectsUpdate 1 Sentinel
Test CodeLarge, brittle, and noisyTiny, readable, and pure

The Starlight Protocol: Hub & Sentinels

CBA introduces the Starlight Protocol. We’ve separated the "Animal" (your test's intent) from the "Environment" (the DOM noise). The environment is managed by Sentinels—specialized, language-agnostic agents.

  • The Hub (The Flight Controller): Owns the browser and broadcasts a stream of "Starlight" (DOM mutations, network pulses).
  • The Janitor (Python/AI): Watches for popups and overlays, clearing them before the main script even knows they existed.
  • The Waiter (Go): Monitors the "Network Pulse" to prevent actions during instability.
  • The Historian (Node.js): Manages the "State Constellation" (auth tokens and session persistence).
Code
// Intent Layer: Pure and simple
await navigation.to("/checkout");
// The Janitor Sentinel clears the "10% Off" popup automatically in the background
await checkout.submit();

Measure Success with Hero Story Reporting

CBA doesn't just say "Pass." It generates a Hero Story—a visual timeline that distinguishes between the Intent Path (the goal) and the Sentinel Interventions (the proactive corrections). It proves that your intent is bigger than the environment's noise.

The Result
During our latest Phase 3 prototype on a "Chaos Terrain," the CBA system achieved 100% navigational purity. The intent script remained blind to obstacles, focusing only on the goal, while Sentinels cleared sequential failures in milliseconds.

Stop building scripts that are afraid of the ground. Build a system that navigates by the stars. Welcome to the revolution.

Dhiraj Das

About the Author

Dhiraj Das | Senior Automation Consultant | 10+ years building test automation that actually works. He transforms flaky, slow regression suites into reliable CI pipelines—designing self-healing frameworks that don't just run tests, but understand them.

Creator of many open-source tools solving what traditional automation can't: waitless (flaky tests), sb-stealth-wrapper (bot detection), selenium-teleport (state persistence), selenium-chatbot-test (AI chatbot testing), lumos-shadowdom (Shadow DOM), and visual-guard (visual regression).

Share this article:

Get In Touch

Interested in collaborating or have a question about my projects? Feel free to reach out. I'm always open to discussing new ideas and opportunities.