refactor(tests): enzyme => react-testing-library

[theashraf]

• I have read freeCodeCamp's contribution guidelines.
• My pull request has a descriptive title (not a vague title like Update index.md)
• My pull request targets the master branch of freeCodeCamp.
• None of my changes are plagiarized from another source without proper attribution.
• All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
• My changes do not use shortened URLs or affiliate links.

Closes #37690

[gitpod-io]

[raisedadead]

Ah.. my bad. I forgot to mention and clarify that we use Enzyme for our in browser test runner (for the curriculum), where should probably leave it as is in the test runner(for now).

Hey @ValeraS do you think there is a better way to test the react challenges?

[ValeraS]

@raisedadead It may be difficult to replace the enzyme in challenges tests. The enzyme allows you to check the internal state of the component. testing-library does not.

IMHO, we can use the testing-library for client tests as best practice and enzyme for challenges tests, because we want to check the internals of the components.

[theashraf]

Well, I added back enzyme for the reasons mentioned by @ValeraS which makes sense

[raisedadead]

Thanks @ValeraS !
Thanks @theashraf will have this pulled down and merged soon :)

[RandellDawson]

@raisedadead I believe this PR may have broken something. We are receiving many reports on the forum about the React challenges no longer working. I have validated they do not seem to work on Chrome or Firefox. The following error appears in the console with the correct solution for the first challenge.

Link to challenge

[RandellDawson]

Update: Now I am not sure. Reverting or not reverting the changes, I can not reproduce the problem locally.

[ojeytonwilliams]

I can't reproduce it either. .org .dev and local all seem fine. Also, the changes in frame-runner.js should not have any effect on the functionality.

One complete guess is that, somehow, they've got a broken version of the enzyme adapter cached. Maybe.

[RandellDawson]

When you say "they", how do you mean?

[ojeytonwilliams]

I just meant "the people that are experiencing the problem.".

Since you don't see the problem when you npm run clean-and-develop you could try building the site and checking again. It looks webpack related, after all.

[raisedadead]

Hi @RandellDawson @ojeytonwilliams can you point me to the threads on forum? Thanks.

[RandellDawson]

@raisedadead
https://www.freecodecamp.org/forum/t/react-redux-tutorials-tests-are-not-executing/326155/6

I have tried everything I know to do, but still get the error I show above when running any of the React challenges' tests.