Daily UX Writing Challenge Day 3

#challenge #ux #uxwriting #beginners

I managed to lose my phone on the bus today after work, luckily a kind homeless man picked it up for me, but trying to locate him to get it back was a struggle. Luckily after almost 3 hrs in the cold I managed to get my phone back~ So I was planning to just go to sleep and skip the challenge for the day. Unfortunately my brain was like 'it's only the 3rd day and you failed the streak already?!' So here I am.

Thankfully it was a nice short one today and didn't require much
thinking. Initially I wasn't sure what tone of voice I should use as I have no idea what the company is and made a slighter longer message with a friendly tone then noticed the character limit which didn't leave me with any options other than a super, short, clear concise message.

Top comments (0)

5 Playwright CLI Flags That Will Transform Your Testing Workflow

0:56 --last-failed: Zero in on just the tests that failed in your previous run

2:34 --only-changed: Test only the spec files you've modified in git

4:27 --repeat-each: Run tests multiple times to catch flaky behavior before it reaches production

5:15 --forbid-only: Prevent accidental test.only commits from breaking your CI pipeline

5:51 --ui --headed --workers 1: Debug visually with browser windows and sequential test execution

Learn how these powerful command-line options can save you time, strengthen your test suite, and streamline your Playwright testing experience. Click on any timestamp above to jump directly to that section in the tutorial!

0:56 --last-failed: Zero in on just the tests that failed in your previous run
2:34 --only-changed: Test only the spec files you've modified in git
4:27 --repeat-each: Run tests multiple times to catch flaky behavior before it reaches production
5:15 --forbid-only: Prevent accidental test.only commits from breaking your CI pipeline
5:51 --ui --headed --workers 1: Debug visually with browser windows and sequential test execution

Watch Full Video 📹️