Add smoke test for rw dev and rw serve commands

[thedavidprice]

cc @jtoar @dac09

Storybook has two command options that, when used together, make it simple to test the start process within the context of CI. See --ci and --smoke-test via Storybook CLI Doc:

• ci: CI mode (skip interactive prompts, don't open browser)
• smoke-test: Exit (success) after successful start

Thanks to @virtuoushub's persistent work on #3515, we are now using these Storybook options to test in CI instead of the previous complicated sequence of steps.

If we added similar capability via and option/script/GH-action to rw dev and rw serve, it would greatly simplify testing these commands and processes within the context of CI:

• confirm all processes started successfully (no warnings or errors)
• confirm web assets are being served
• confirm API endpoint is healthy
• confirm GraphQL is healthy
• IF all status = success, then exit gracefully
• ELSE process.exit(1)

---

Note: this is related to my work on #3914

[dac09]

@thedavidprice as discussed during CTM, I don't the see the value in shipping the --ci or --smoketest option to the end users. I think we're better off having a simple test with playwright.

Guess who had this stuff in progress and working back in August last year? #3044 - time to revive the old code.

Do you want to update the issue to reflect this?

[thedavidprice]

Thanks @dac09! I did update the title and description. I agree that not adding the option to the commands is ideal for our CI purposes. However, I do think that adding an option like yarn rw serve --smoke-test is also useful for devs who could add this to CI for their own projects. (Agreed yarn rw dev not so helpful...)

But for now, I don't really care how we execute it as long as I can use it as a "run" step in a GH Action on both Windows and Ubuntu. So that's why I was also thinking about trying to build a script we could use in a GH Action, e.g. like this "check" action @jtoar recently created here.

@jtoar and I did get started on the CI workflow itself today, which is where I'd like to add the checks for rw dev and rw serve as additional run steps:

• Adds a CI Check to run CLI against Windows and Ubuntu; adds build:test-project as reusable fixture #4495

I wanted to to reproduce the Prisma installation error on Windows, and finally just started the process.