Jest Unit Tests MASTER CASE

[GeorgeCiesinski]

Note: This issue is still being built. Currently, existing files need to be checked for testable functions. Some files need to be refactored to improve unit testing. I will update this message once the MASTER CASE and child cases are complete.

Describe the new feature

The project needs functional unit tests for core features in order to prevent future contributions from breaking anything. In addition to this, a testing standard would be helpful to guide future collaborators to create their own tests for their new features.

Planning

Please create a case for any file you create unit tests for and mention this master case.

Ready for Unit Test

These files are probably ready for unit tests and may require minor refactoring.

• commands
• language
• setupCommands
• util

Prepare for Unit Test

These files contain large async functions which are difficult to test, and may require major refactoring before tests can be created.

• catch
• championship
• delay
• explore
• help
• index
• leaderboard
• mod
• reveal
• score
• settings
• timeout

Before Creating Unit Tests

The above two lists are just for guidance and to gather all of the existing modules in the program. Each of these should be gone through to determine the most vital functions which must be tested before tests are created.

Goals

The main goal of this master case is to decouple the code and make it more modular. This way if a change needs to be made we can avoid having to refactor an old module that we hardly remember, and a more specific, smaller module, can be altered instead. In short this should reduce technical debt down the line.