What about testing this project?

[KarlHeitmann]

Hello Everybody!

On PR#92 I put on some test files.

Can you take a look at these files, please? Would somebody help me by testing all the functions inside the folder src/utils/ I think this is the core of the project, and is by far the most difficult part to understand in the project. It is very abstract, you have a lot of recursion, and is complex. I needed to create these tests because I needed some support to compare the output I was expecting with the current output the functions generated.

Some things to take on consideration for people who wants to help me:

• We can put a goal to cover all files inside src/utils/ folder, once the folder is covered, we can think if it is necessary to test the rest of the project.
• This will be great source of documentation. A new contributor can see the tests, read the I/O, and figure out what each function does. No need to write manuals.
• Creating the test is easy. I changed this file: src/constants/data.ts put on a very simple JSON, and then put some breakpoint right after the function I wanted to test, copy the input I was sending through the pipe of function chained together, and copied the output as expectation to the test file. Very simple to do, but an annoying and boring task. Let's divide the boring tasks between people who want to contribute.
• All the private functions I've exported them, I know this is not the best way to do it. But it's the workaround I found. I read on many stackoverflow threads that you can use rewire package to access private functions inside a file. But I couldn't make it work.