Alternative to #15 that uses Cypress instead. Similarly fixes #7 and fixes #14
Jest w/ Electron runs faster, and I prefer Jest's test runner and output quite a bit more than Cypress, so I'm likely going to merge that one instead. It also doesn't have any Cypress-specific gimmicks like the directories, plugins, config etc, so it requires less context to use and is probably more familiar to more people (though the Cypress-specific stuff does cut down on all the scripts and helpers fwiw).
Buuuut Cypress allows (requires actually) you to custom instrument your code for code coverage. Jest does it for you, which is great for most use cases, but it seems to give no flexibility and so it runs into the infinite cycle errors. I'll go over that more on #6, but for now we could stick with Jest w/ Electron and maybe eventually move to Cypress... that is if coverage actually ever works correctly 😕
Alternative to #15 that uses Cypress instead. Similarly fixes #7 and fixes #14
Jest w/ Electron runs faster, and I prefer Jest's test runner and output quite a bit more than Cypress, so I'm likely going to merge that one instead. It also doesn't have any Cypress-specific gimmicks like the directories, plugins, config etc, so it requires less context to use and is probably more familiar to more people (though the Cypress-specific stuff does cut down on all the scripts and helpers fwiw).
Buuuut Cypress allows (requires actually) you to custom instrument your code for code coverage. Jest does it for you, which is great for most use cases, but it seems to give no flexibility and so it runs into the infinite cycle errors. I'll go over that more on #6, but for now we could stick with Jest w/ Electron and maybe eventually move to Cypress... that is if coverage actually ever works correctly 😕