Add bundled configuration for Cypress

[ayushn21]

This is a 🙋 feature or enhancement.

Summary

This PR adds a bundled configuration for Cypress based on the automation by @ParamagicDev (https://github.com/ParamagicDev/bridgetown-automation-cypress).

There's an issue with running the tests though. We run yarn start before running the tests which forks off processes to run the Bridgetown server and Webpack dev server. These processes aren't killed after the test suite ends so the only way to run the server again is to find the process id and kill the process before running yarn start again.

Not quite sure how to fix this. Once we switch to Rake, would be possible to fix this problem? Might be worth holding off on merging until then.

To Do

• Figure out a fix for the the orphaned server processes during testing
• Update docs on website

Context

Resolves #311

[jaredcwhite]

Not sure the switch to Rake would automatically resolve the issue, but yeah would make sense to implement then and not now (thus having to reimplement later).

[ayushn21]

I took a (very) short peek at your Rake/Roda etc PR and saw that the commands in Rake were triggered using Ruby (Bridgetown::Commands::Build.start etc etc) ... so figured that might give us an easier way to kill the forked processes once the tests are run. This is a complete guess though; I know next to nothing about Rake and orchestrating processes and things.

[ayushn21]

@jaredcwhite I'm half asleep (it's 1am here) but I got on a roll so thought I'd sort this out. I think it should be more or less good to go. It'd be great if you could take a peek and let me know if you have any feedback.

Otherwise will re-test and merge tomorrow when I'm more awake!

[jaredcwhite]

This look great! I'll test it out more when I get a chance but meanwhile LGTM. (Just one question about the Rake tasks)

[ayushn21]

Thanks! I'll leave this open until you get a chance to test it, just in case something's not quite right. Seemed ok in my testing but you never know!