Istqb on Ocarina — manual

01.02 — ISTQB vs pytest / Jest / Mocha

Wed, 20 May 2026 00:00:00 +0000

01.02 — ISTQB vs pytest / Jest / Mocha#

The methodological observation#

Past the technical bet on the technical / non-technical barrier (see 01-flip-the-problem.md), there’s a second bet: the one on trade vocabulary.

The ISTQB and professional testers have spent decades building a precise, battle-tested vocabulary: test cycles, campaigns, test suites, test cases, test steps. A clear hierarchy, built to organize, trace and drive software quality.

Automation tools have largely ignored that legacy.

12.08 — Ocarina in the testing industry

Wed, 20 May 2026 00:00:00 +0000

12.08 — Ocarina in the testing industry#

Ocarina isn’t a better pytest, isn’t a better Robot Framework, isn’t a better Cypress. It’s structurally elsewhere. This chapter tries to explain the shift it represents and the head start it takes.

1. The current industry map#

Three big e2e tool families#

Family	Examples	Model
Text DSLs	Robot Framework, Cucumber + Gherkin	Permanent translation layer between text and code
Runner plugins	pytest-selenium, pytest-playwright, pytest-bdd	Grafted onto pytest, inherit its lifecycle
Vendor SaaS	BrowserStack, Sauce Labs, LambdaTest, Cypress Dashboard	Local runner + paid execution cloud

Three shared friction surfaces#

Friction	Manifestation
Marketing > Technical	Tools sold on demos, conferences, and oriented certifications. Hype drives adoption.
Vendor lock-in	Once adopted, refactor is costly, hostage taking.
Misplaced cognitive effort	Understanding the tool takes longer than doing the work.

2. Ocarina’s technical bet#

No text DSL → pure Python, embedded DSL.
No pytest plugin → integrated runner, absolute ISTQB fidelity.
No async/await → simplicity, Selenium-synchronous compatibility, no “geek tricks”.
No SaaS → all local, very dense core, white box.

12.15 — Typing, ISTQB, Reinforcement Learning, probes: why AI works in Ocarina

Wed, 20 May 2026 00:00:00 +0000

12.15 — Typing, ISTQB, Reinforcement Learning, probes: why AI works in Ocarina#

Why so much obsession over strict typing, formalizing every interface, alignment on ISTQB, refusing to execute an assertion without having observed? The mechanism is borrowed from Reinforcement Learning: an agent only progresses under constraint + reward signal.

1. A naked LLM is just a bad collaborator#

An LLM without a structured environment is:

Optimistic — it assumes its code works.
Persuasive — its output is convincing even when wrong.
Memoryless — it forgets conventions between sessions.
Feedbackless — it has no way to know it was wrong.
Loves what it deems “most likely” — it drifts toward popular patterns, not correct ones.

Without an environment, an LLM is an over-confident junior dev producing code that looks right, breaks in prod, and learns nothing from the failure.