When running the cypress component tests lots of eslint errors are reported. These appear to be a configuration issue rather than an actual issue with the code as they mostly report undefined variables or functions in cypress (e.g. 'cy' is not defined). But the tests themselves run perfectly fine.

Steps to Reproduce

1. cd to farmdata2_modules
2. run ./test_runner.bash ct --spec **/Error*.spec.comp.js
3. observe the errors at the top of the ouput.

Also note that the test itself passes. This suggests maybe that eslint is running in a different context than the cypress tests themselves. It is worth further note that if the tests are run in the Cypress GUI there is no reporting of eslint errors at all.

Simply disabling the running of eslint before the component tests would be an acceptable solution.