Skip to content
EngineerAdvisory
Menu
Design
English

Engineer / Advisory / Categories

Testing & QA

  1. Streamlined CI/CD processes, saving 4,000 hours

    Streamlined CI/CD processes, saving 4,000 hours by introducing automation in software development pipelines.

    Streamlined CI/CD to save ~4,000 hours, making releases faster and more reliable so the team could ship with confidence.

  2. Migrated the API to Huma v2 at 100% parity

    Migrated the HTTP API from Fiber to Huma v2 — 649 paths and 760 operations — reaching and holding 100% parity between the routes the server registers and the OpenAPI description it publishes.

    Migrated the HTTP API from Fiber to Huma v2 — 649 paths, 760 operations — at 100% parity between registered routes and the published OpenAPI description.

  3. Authored 578 go‑task automation targets

    Authored 578 go‑task automation targets spanning native, Docker and HTTPS dev modes, linting, testing, database and deployment.

    Authored 578 go-task automation targets across native, Docker and HTTPS modes — linting, testing, database and deployment behind one toolchain.

  4. Set a zero‑warnings bar across six languages

    Set a zero‑warnings quality bar across six languages — Go, TypeScript, SQL, Python, Shell and Markdown — enforced by pre‑commit hooks.

    Set a zero-warnings quality bar across Go, TypeScript, SQL, Python, Shell and Markdown, enforced by pre-commit hooks.

  5. Built a test suite across Go, SQL and browser

    Built a layered automated test suite — 981 Go tests, 543 frontend and browser specs, 494 SQL behavioural tests — with mutation testing, property‑based tests and an accessibility gate.

    Built a layered automated test suite — 981 Go tests, 543 frontend specs and 494 SQL behavioural tests — with mutation, property and accessibility gates.

  6. Built a 268‑check guard engine for the repo

    Built the repository's guard engine — 268 registered commit checks, 277 lint rules and 15 custom ESLint rules — plus 146 tests of the guards themselves, so the build holds the standard, not review.

    Built a guard engine of 268 registered commit checks, 277 lint rules and 15 custom ESLint rules, with 146 tests of the guards themselves.

  7. Built a 22‑linter commit gate

    Built a commit gate of 22 one‑line linters plus five that earn a paragraph, with no warning tier and no inline suppressions permitted, covering HTML, CSS, JavaScript, Python, YAML, Markdown, shell, links, spelling, secrets and typography.

    Mechanical objections are made by a machine before a commit exists, and the gate is the only reviewer this project has.

  8. A safety net that no longer costs half an hour

    Cut the site's browser‑driven quality gate from 1,636 seconds to 615 by scheduling its checks longest‑first through a worker pool bounded to four lanes, after measuring that alphabetical order cost 320 seconds against 224.

    The gate went from 1,636 seconds to 615, while the checks got broader rather than thinner — the serial cost went up and the wall clock came down.

  9. Put the documentation under its own linter

    Put the documentation under its own linter — a per‑file line budget that only ratchets down, an index requirement and a real‑path check — which found six of nine plans marked done while carrying unchecked boxes, and fourteen commit‑gating tasks named in no document.

    Twenty-six documents totalling about 2,666 effective lines, each under a budget that cannot grow, with every path and symbol they name checked against the…

  10. Linted the 10,242‑line quality gate itself

    Brought 10,242 lines of quality‑gate JavaScript under a formatter and a linter after establishing it was the largest body of code in the repository and the only one nothing read, fixing 13 findings and suppressing none.

    The largest and most load-bearing code in the repository is now formatted, linted and type-checked, with thirteen findings fixed and zero suppressions.

  11. Held the generator to 981 tests and 92% coverage

    Held the generator to 981 test cases at a 92% branch‑coverage floor with warnings treated as failures, and asserted idempotence by running the whole build pipeline twice from an empty file and requiring the second pass to change nothing.

    The pipeline can be re-run against a live database without fear, which is what makes incremental content work possible at all.

  12. Passed 106 of 106 PDF/UA‑1 profile checks

    Recorded PDF/UA‑1 validation across nine documents with 106 of 106 configured accessibility‑profile checks passing, while the archival variant failed one of 146 rules.

    All configured accessibility-profile checks passed. The archival claim is stated honestly as a near-miss with the specific gap named.

  13. Enabled every linter rule as an error

    Selected every rule the Python linter has as an error, working through 1,815 findings to reach zero, with each of the few exemptions carrying a written reason and two of them backed by a checker instead of a comment.

    The linter runs at full strength with zero findings, and every deviation is documented at the line where it is taken.

  14. Wrote tests for the checkers themselves

    Wrote tests for the checkers themselves after establishing that a checker fed only clean input will one day report clean because it read nothing — planting a misspelling to confirm the spell‑check finds it, and taking an id range from the database rather than from a number in the test.

    Every checker in the project now has a test that proves it fails on bad input, and the range assertions read from the source of truth.

  15. Found the hooks and the gate disagreeing

    Found the commit hooks and the quality gate running different checks while a document promised they were the same, by comparing the two lists in a test — the five that only ever ran by hand were the ones reading the CV prose.

    The hook and the gate provably run the same checks, and the prose checks now run on every commit.

  16. Built a cross‑language figure check

    Built a cross‑language content check that fails when a translation drops a figure the English states, and when a language uses notation it does not use — finding two Danish descriptions missing a metric and sixteen Ukrainian spans quoting in the English style.

    Eighteen real defects closed and the class closed with them, since every future translation is compared to its English source before it can be committed.

  17. Adopted Swift 6 strict concurrency over C

    Adopted Swift 6 complete strict concurrency with no actors, bridging a blocking C event loop to the main actor through one producer, one consumer and one ordering — after establishing that a task per event loses the ordering the interface depends on.

    The application compiles under complete strict concurrency with no suppressions, and event ordering is a structural property rather than a hope.

  18. Wrote a parser verifying every FFI call

    Wrote a parser that reads the real 7,308‑line C header and verifies every call site, every enum constant and that every pointer‑owning class is final, after a hand‑written placeholder header let calls to three removed functions compile, link and crash.

    The class of defect that produced the original crash cannot recur, because a stale reference is now a build failure rather than a runtime one.

  19. Took the test suite to 8.9 seconds

    Took the test suite from six tests over a sixty‑second limit to 135 passing in 8.9 seconds by profiling the main thread and removing the two calls it sat inside for 3,989 samples out of 4,017.

    The suite went from six tests over sixty seconds — 74 seconds of wall clock — to 135 tests passing in 8.9, which puts it inside the window where it runs on…

  20. Rewrote error messages to stop blaming users

    Rewrote the application's error messages against a written tone standard after a refused sign‑in blamed the user for mistyping when the provider actually required an app‑specific password, and covered it with a test that names the provider.

    The error surface follows a stated standard and the case that prompted it is covered by a test that fails on the old text.

  21. Made six collectors state what they skipped

    Made six reporting collectors state the part of their input they never read — files that stayed shut, probes not installed, journal lines unrecognised — and fitted thresholds to 116 measured samples, after establishing that a blind collection and a healthy host render the same page.

    A page of this platform's numbers now carries its own blind spots beside its findings. None of the self-measurement is a gate, and that is stated rather than…

Contact

Still working out what you need?

Tell us what is going wrong, or what you are trying to build. We will tell you what it would take, roughly what it would cost, and whether we are the right people for it.

From 1,400 DKK an hour, excluding VAT — and less per hour on a longer booking.

welcome@engineer.company +45 50 10 61 84 Copenhagen, Denmark