fixing module test

[keshav234156]

Fixes #1376
Make sure these boxes are checked before your pull request (PR) is ready to be reviewed and merged. Thanks!

• tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR -- or run tests locally with npm test
• code is in uniquely-named feature branch and has no merge conflicts
• PR is descriptively titled
• ask @publiclab/is-reviewers for help, in a comment below
• Insert-step functionality is working correct as expected.

We're happy to help you get this ready -- don't be afraid to ask for help, and don't be discouraged if your tests fail at first!

If tests do fail, click on the red X to learn why by reading the logs.

Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software
Please make sure to get at least two reviews before asking for merging the PR as that would make the PR more reliable on our part
Thanks!

[keshav234156]

@jywarren @harshkhandeparkar Please review the changes!!!

[codecov]

Codecov Report

Merging #1410 into main will increase coverage by 0.15%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1410      +/-   ##
==========================================
+ Coverage   66.12%   66.27%   +0.15%     
==========================================
  Files         125      125              
  Lines        2571     2571              
  Branches      404      404              
==========================================
+ Hits         1700     1704       +4     
+ Misses        871      867       -4

Impacted Files	Coverage Δ
src/modules/ReplaceColor/ReplaceColor.js	92.3% <0%> (+15.38%)	⬆️

[jywarren]

Whoa, does this resolve all the per-module tests? I see some edits but mostly changes in the expected output, i guess?

Should we add in the 1/0 status check here too?

[jywarren]

Awesome, checked the logs. Looks great. I'll merge this now, let's do the status check in follow-up. Can you open an issue for it? Thanks!!!