Component unit tests enzyme

[AWolf81]

Related Issue:
#309

Summary:

• Added Enzyme setup
• Removed flow typing from tests
• Added first tests
  • Progressbar
  • Sidebar

Tests

• Progressbar component
• Sidebar component

[codecov]

Codecov Report

Merging #340 into master will increase coverage by 4.12%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #340      +/-   ##
==========================================
+ Coverage   20.73%   24.86%   +4.12%     
==========================================
  Files         248      152      -96     
  Lines        3945     3628     -317     
  Branches      391      389       -2     
==========================================
+ Hits          818      902      +84     
+ Misses       2846     2452     -394     
+ Partials      281      274       -7

Impacted Files	Coverage Δ
...nents/ProjectIconSelection/ProjectIconSelection.js	0% <ø> (ø)	⬆️
src/sagas/task.saga.js	64.56% <ø> (ø)	⬆️
src/components/Sidebar/Sidebar.js	75% <ø> (+75%)	⬆️
src/components/ProgressBar/ProgressBar.js	100% <100%> (+100%)	⬆️
src/components/AddDependencyInitialScreen/index.js
src/components/Toggle/Toggle.stories.js
src/components/AddDependencyModal/index.js
src/components/TwoPaneModal/index.js
src/components/SettingsButton/index.js
src/components/Toggle/index.js
... and 99 more

[AWolf81]

@idoberko2 would be great if you could review the setup and first tests? If there is nothing against using Enzyme we can merge this to have the setup ready and we can continue to add more tests afterwards.

[melanieseltzer]

LGTM! Just a question about a file I wasn't sure about.

Also since you were adding /* eslint-disable flowtype/require-valid-file-annotation */ to the tests missing it, do you mind doing it to WhimsicalInstaller.helpers.test.js and Initialization.helpers.test.js? Just found out they are also not disabled and we can just do it in this branch.

[melanieseltzer]

I'm not familiar with what we're having in the repo for VSCode settings, was this supposed to be committed? If so what does it do?

[AWolf81]

I'd like to add the launch settings so it's possible to use the integrated debugger during testing - so you can add breakpoints etc. Just open the debugger pane (striked-through bug icon, see screenshot below) select the configuration & click play. (No config in the screenshot)

OK, I'll check the other test files and also disable flowjs there.

[AWolf81]

OK, I've fixed all linting errors. Also added two unrelated flow linting errors.

[melanieseltzer]

Ah that's cool 👍

[idoberko2]

@AWolf81, how do you want to proceed with this one?
Should I just start covering components with tests or you intend to write some tests on your side (I don't want us to step on each other's tows)?
Should I branch out of this one (in case you're about to merge it)?

[AWolf81]

@idoberko2 if the setup is OK in this PR, we can merge it to master. Can we merge this?

Then you can branch from master and we can track progress on issue #309. Just add the components you'd like to work-on as a comment and I'll add mine (if I'm adding some tests - no progress on my side at the moment).

[idoberko2]

@AWolf81, the setup looks good and I can confirm it runs successfully on my environment both via the CLI and the VSCode integration.