#826 Update Cypress

[snowteamer]

Summary of changes

• Updated Cypress to 6.2.0
• Had to change one line in group-contributions.spec.js to use not.exist instead of not.be.visible (see nonexistent element assertions in the Cypress migration guide).
• Temporarily downgrade Node from v15 to v14 to avoid a dependency compatibility issue that was found by running the tests. Some of our dependencies do not support Node v15 yet.

Additional info

The overall Cypress run for this build took 3min 40s, which is 23s better than the run from #1041, and 14s better than the run from #1040.

Therefore, the performance issues mentionned in #829 seem to have been resolved, or to no longer be relevant.

As for the other issues, I'm not sure. There are a lot of open issues on the Cypress repo, but I didn't go as far as investigating enough of them to guess if the situation was better in version 3.5.

Maybe @sandrina-p could tell whether we can safely upgrade?

Closes #1042

[taoeffect]

Awesome PR @snowteamer!

One request: could you please update your version of node and npm? The reason I ask is because using the latest version will produce a different package-lock.json file. We'd like to use the latest version of it so as to avoid conflicts in PRs going forward.

E.g., when I test locally, I get a large diff after running npm install that has a different lockfileVersion:

-> % git diff   

diff --git a/package-lock.json b/package-lock.json
index 2bdb51d7..48d74d2c 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,8 +1,20071 @@
 {
   "name": "group-income-simple",
   "version": "0.0.1",
-  "lockfileVersion": 1,
+  "lockfileVersion": 2,

When I run npm version, here are the values I get:

-> % npm version
{
  'group-income-simple': '0.0.1',
  npm: '7.0.15',
  node: '15.4.0',

 [ ... snip irrelevant values ... ]

You can update node to 15 using whatever package manager you're using, and if it doesn't update npm to at least 7.0.15 after doing that, then you can do it yourself by running npm i -g npm@latest.

Finally, feel free to bump the minimum node version requirements in the README.md from 12 to 15.

[snowteamer]

That's indeed a good idea, now that our Travis config no longer mandates using Node v14.

However, since this might be useful for other contributors, I will add that npm i -g npm@latest will not upgrade npm from v6.x to v7.x, but only to the latest v6.x version.

So I had to run npm i -g npm@7, explicitly specifying the major version number.

[snowteamer]

Hmm this still causes a merge conflict and a rather large diff - should I temporarily use the exact Node and NPM versions listed in your console output?

[taoeffect]

@snowteamer Let's try to troubleshoot this on Slack

[taoeffect]

Excellent work @snowteamer! Thank you for sending this in! 😄