Install
Testing & Quality
Unit, integration, E2E, contract tests, test data, coverage, and performance/chaos testing.
- 4 Subtopics
- 5 Tracked terms
- Last 30 days Feed window
Inside Testing & Quality
What this topic collects on
An article joins this feed when it matches these terms. Each one is also a search of its own.
Related topics
- Languages & Runtimes
- Editors, IDEs & Developer Experience
- Frontend Web
- Backend & APIs
- Data, Databases & Streaming
- DevOps, CI/CD & Platform Engineering
- Security & Privacy Engineering
- Architecture & Patterns
- AI/ML Engineering & LLMOps
- Collaboration & Project Management
- Open Source & Licensing
- Careers, Learning & Events
Latest in Testing & Quality
Verify a Real Axiomark Chain Yourself
5+ hour, 35+ min ago (521+ words) Everyone in this market says their records are independently verifiable. Very few of them will hand you a record and let you try. Below are two sealed decision chains: one intact, one with a single field altered after sealing. Verify…...
My parser reported a parse error on a file that was never malformed
14+ min ago (554+ words) A build step that reads requirement tables out of a document reported this, every run: reason=parse has an obvious reading. Either the document is malformed or the parser is broken. A person following that reason code goes and looks…...
A deprecated value has to live somewhere, and widening the set was the wrong somewhere
14+ min ago (590+ words) A check refused a row I had just added. The row was a retired signing key, kept so that records signed under it can still be read. The check said: The set of accepted schemes has exactly one element, and…...
How to change reasoning effort in Codex CLI: model_reasoning_effort values and one-off overrides
37+ min ago (430+ words) Codex feels slow, or it overthinks a trivial fix. The knob for that is reasoning effort, the Codex counterpart of extended thinking in Claude Code, controlled by the model_reasoning_effort key. In short: set model_reasoning_effort = "high" (or another value) in ~/.codex/config.toml…...
My build went green and the permanent record kept almost none of it
1+ hour, 5+ min ago (569+ words) A clean run at a release boundary. Every check green. Then the step that writes the run into the append-only record, and this: The run succeeded. The record of the run mostly does not exist. That is the part worth…...
Sixteen XORs and not a single if
1+ hour, 18+ min ago (990+ words) Verbose is a small experimental language I build — its compiler proves properties about your code (termination, declared reads, sound types) and emits tiny x86-64 machine code: no runtime, no GC, no libc. Its emitted binaries already compute the TLS 1.3 cryptography for…...
My check ran green every time and its result could never reach the thing that needed it
1+ hour, 5+ min ago (491+ words) An acceptance report reads one cell per unit. For weeks it read the same thing on every single unit: absent is not a failure. It means the acceptance step looked for a result and found nothing there. Meanwhile the check…...
My determinism check can only test one producer in seven, and the print says so
1+ hour, 38+ min ago (545+ words) I added a check that asks one question: run the thing that produces this record twice, and do you get the same bytes? One of seven. That number is not a coverage gap I plan to close. It is the…...
A question on Discord found two bugs in my RAG system. Fixing them found a third.
1+ hour, 53+ min ago (611+ words) Every test passed. The tests had the same blind spots as the code. A developer saw Ossian's MCP... Tagged with rag, kafka, ai, opensource....
My release smoke test passed on the message that says it failed
2+ hour, 12+ min ago (607+ words) Here is the step, as it had been since the first release: Read the last line on its own. It passes when the released version appears anywhere in the output. Now read what npm prints when the version is not…...