Testing methodology and frameworks

Let’s talk about how we should be testing. It’s obvious we should be testing more, but we need some guidelines to help ensure that our tests are high quality and that contributors can easily see what they should be doing.

As such I think we should discuss which testing frameworks we should use and where we should use them.

Right now we use:

• Cypress for e2e, which means we use Mocha when writing those tests
• Mocha in test-challenges.js
• Jest everywhere else (I think)
• Enzyme for challenge tests (the tests that run on user submitted code)
• React Testing Library for some component testing
• react-test-renderer for others
• redux-saga-test-plan for one Redux Saga

I think that covers it!

@freeCodeCamp/dev-team does anyone want to chime in with things we should or should not be doing?

[ahmadabdolsaheb]

A quick update on getting rid of redux. Although hooks and context could replace redux’s state management, we use redux actions for handling impure functions as well.

We could useEffect for some of those functions; however, we should consider sticking with a library to manage application side effects such as redux-sage.

The more obvious way forward would be to rewrite epics to sagas, rewrite class components to functions, and use redux hooks.

That should considerably clean up our code base a lot and make it more readable.

We could also briefly explain how we use redux and sagas in our guidelines so it would be more obvious to new contributors.

[ojeytonwilliams]

I should have replied here in the first place:

https://www.browserstack.com/open-source

It looks like they’re happy to support OS projects, so we should be able to work something out.