How to do tests correctly?

Question

go

Good day.

I am a beginner programmer, I decided to make a project for my resume and learn the go language accordingly.

I took a topic that has been of interest to me for a long time: a neural network, and everything else I wanted to immediately lay the foundation for various architectures of neural networks (this is me to the fact that there is probably an overabundance of objects, interfaces).

I repeat, I didn’t try to reinvent the wheel, I just wanted to learn the language, plus the topic is interesting, so please don’t judge strictly.

Tests!
I sorted out the topic, sort of understood it (I re-read and reviewed a bunch of training material), and generated test files in goland, but it literally generated all the functions and methods!
Shock!
Really it is necessary to do to all functions and methods or there is some criterion?
Point the beginner in the right direction.

Thanks in advance to all who respond! Link to the project

on github.com Additionally, my question (my request) is addressed to practicing seniors and middles of the Golang language: is it possible to send CVs to juniors with this project?

Answer 1

Avoid the Cargo Cult.
Tests should be
* Sufficient and reasonable
* Every bug in the git should be covered by a test and closed
That's enough, test coverage moves are 100% ridiculous