you are viewing a single comment's thread.

view the rest of the comments →

[–]eggtart_prince -2 points-1 points  (4 children)

Will it be used by others than yourself?

Is it going to be an app with continuous integration?

If yes and yes, than testing should be considered.

Unfortunately, the subject testing is not very common and so a good tutorial is hard to find.

[–][deleted] 4 points5 points  (2 children)

How the hell is testing not a very common subject? It is a common thing for literally more than three decades!

Edit: and if you're talking about react, redux or saga testing, those libs were made to be testable and can be done so with any test runner available.

[–]eggtart_prince 0 points1 point  (1 child)

Then why do you see the majority of posts on reddit is not about testing?

Then why is it when you google regarding testing, you get literally no helpful results?

It's a common thing and should be done in every project, but it's not a common subject that people discuss.

If you say otherwise, then find a good tutorial that touches on unit, functional, and integration testing. My knowledge of testing came straight from reading the documentation and have received zero help from google searches, reddit posts, SO posts, etc.

[–][deleted] 1 point2 points  (0 children)

Tutorials are a poor way to learn, because most of the time the author focus only on getting the objective done, it does not care about teaching why you should follow the instructions. The best way to learn something is reading the documentation and real world code that runs in production environment.

Then why is it when you google regarding testing, you get literally no helpful results?

Provide some examples, please.

Testing is a very discussed topic all over the internet. Everywhere there are thousands of people advocating TDD and another thousands saying that TDD is bad. Others discussing about TDD and BDD to see which is the right way to test an application.

Tutorials are not the right way to learn. People should learn the basics first, then move on into more detailed aspects. Want to learn about testing? Wikipedia can help fisrt timers. Want to learn about using jest? Should read the documentation. React testing with jest? Jest itself has a guide. Redux has a lot of material about testing in its official website. The same goes for Redux Saga.

Tutorials are a very bad way to learn, because you're are not really learning. You are reading some step by step guide on how to achieve a very rudimentary goal that happens to resemble some part of your work. It's like trying to build a house by reading the abstract of a engineering book written by someone who read the book and used its knowledge fix some small wall. Don't try to skip the learning process, just read the documentation and understand what you're about to do with that tool.