Run cypress in test environment and still get changes picked up?

[benlieb]

We are aware of the suggestion to use ENV['CYPRESS'] in development mode, but we find this this option non-functional/unappealing for a number of reasons.

We have a lot of differences between development mode and test mode: environment keys, storage buckets, firebase emulators etc. We want all these to be configured properly as they are for our rspec suite.

Is there an alternative to still get rails and javascript changes to reload cypress in test mode? It seems that would be first thing on the list of a gem like cypress-on-rails, but I don't see it anywhere. Perhaps I missed it?

The alternative is to make our own environment system so we can run with our test env config in development mode (and just to get code reloading), which seems like an anti-pattern.

All help appreciated!

[justin808]

@benlieb would you be open to having my ShakaCode team help you? If so, please book a call or email me.

[benlieb]

@justin808 Just to confirm, is this a paid service your offering? Or just really good developer relations, lol?