v0.91.0
Changelog
- 97dfe60 --share: every run can end with a link anyone can open
- 47fb62d --since: run the tests this change could have broken, and say what was skipped
- a743d81 0.19.0
- 6485216 0.20.0
- 8240886 0.20.1 — a code sample is not a read
- 4ddd8b2 0.9.0 — a recording now proves the outcome, not just the clicks
- 0eff493 README: the npm page leads with testing, and documents what shipped
- 138c466 a mistyped command no longer reports the customer's app as broken
- 6770f3e add the research the last several commits were built from
- 9889185 authenticated runs, embedded content, and a guard against the green tick on a broken page
- 26acb02 break: fabrication vectors in suggest, false positives in layout, and a wedged suite
- e3047c6 cli 0.7.0: the audit reads whatever analytics you already run
- 2d5d860 cli 0.8.1: the frontmatter fix, one comment implementation, and a comment that stops the next duplicate
- 34111b3 commercial licence, and stop claiming MIT
- 2fc1e9b commit the export the committed tree has been importing since c991034
- 124b2c3 commit the rest of the tree the tests were already written against
- 91a4b9d delete the dashboard: this instance is a data layer now
- f790861 desk kept neither of the two contracts it shares with the rest of the CLI
- c340ebd do not lecture someone about production for a run that cannot happen
- b320061 document the four flags that shipped invisible
- 78b4ea0 file the bug in Linear or Jira, once, and only when it is theirs
- 8d19d02 guard: what this repo needs that nothing declares
- 6cede19 name the API key in the help, where somebody looks first
- a4f7c0c never write the password down
- f8055d7 npx smolanalytics desk: the findings, in the terminal
- e2b7888 npx smolanalytics test: a URL, a sentence, a verdict
- 4e3ad08 one comment implementation, not two
- 7ea4b84 one replay claim, one caveat: stop quoting three different benchmarks
- 4ab3813 our own suite was on the path we sell against
- 906e590 parallel runs, three engines, uploads, and state a test can be given
- 9b1a513 plan check stops failing green builds
- 70b3adb put the guard on the pull request, scoped to the change
- 24a307f replay the page the recording was made on, not the site root
- 5a8e0a4 research: the field, the graveyard, and the red team
- d9e1b01 say when a run went nowhere, and give the CI template a slot for it
- 4351f59 send what the run cost, instead of measuring it and dropping it
- 5618843 stop writing raw NUL bytes into source files
- 4a5430a suggest, suspected code, preview URLs and layout sanity
- b8e108a tell somebody: the verdict reaches Slack, or any webhook
- c2c8cdf tests for the module that holds the passwords
- 6222823 the CI loop: a folder of sentences, one comment on the pull request
- 24c8d40 the CLI half of the same sweep: version, per-command help, and the money event
- 5125e8e the dashboard finally shows whether your tracking works
- f3b8750 the dashboard is about test runs now, not about analytics
- 69c38b3 the false-green guard earns its wiring, or it does not get wired
- 5535a49 the plan-check guard follows the vocabulary to its new home
- c991034 the ship verdict: what we did not check, said out loud
- a7558e9 the suite people keep believing: flaky, evidence, and test-data safety
- 46148d2 the suite: what we check, and whether each check is believed
- 2a7f150 the testing half inside the editor: a local MCP server
- 73d45cb three blockers found by walking the product in a real browser
- 8074968 twelve red tests are one cause, said before the twelve
- d1e29c9 what a run cost, and a ceiling on the next one
- b32c80c why it was flaky, when the two runs actually say
- 4394c45 write into the analytics they already have
Run it: docker run -p 8080:8080 ghcr.io/arjun0606/smolanalytics