Project alone. How?

Question

Software testing

Sooner or later, anyone sometimes has to take on a project that you have to write yourself. Those. I write alone, I document alone, I test alone. So. Now I am writing a library alone. The library implies some kind of functionality, logic. Not a primitive bridge between native APIs to conveniently provided classes. I don’t have a very clear idea of ​​​​how to do this whole process correctly , because any of these stages is important. It is important to test the product correctly .
Let's say I'm starting a class, where do I start? What to be guided by?

PS
I write in C++.

Answer 1

Well, write in the test something like
result = MySuperClass::runSuperAction();
assertEqual(result, 'Expected result');
then you implement the function itself (empty) so that the tests compile, run the tests and see that they do not pass, then change the function so that the test passes and, consider, you have implemented the functionality, testing this functionality and documentation.

Answer 2

I would advise you to get out of your head all the tinsel like unit tests, kosher architecture and abstract factories. The main thing is not tests, not documentation, and not mana from heaven that descended on you after writing charitable code. The main thing is the code itself, which performs the task. Here also write the code, being guided by common sense. If later you feel that you need tests, write tests. And no, it's not.

Answer 3

> project alone. How?
Complicated. But good luck!

Answer 4

TDD is the best way for a loner.
First tests, then functionality.
According to the same tests and documentation at any time.
I started differently, now I regret it.
And going back to tests is unbearable. But apparently it will.

Answer 5

For me, another important point is the measurability of the result.
If you just sit down to fence the code, then you can be blown away somewhere in the process, purely because of the loss of "enthusiasm". And then either the project rushes halfway, or I start to drive a blizzard.
From these positions, the same tests help a little - you can more or less see which part of the tests I have already managed to complete.
It also helps me a lot to schedule small tasks in hours, I got the idea from Joel Spolsky: russian.joelonsoftware.com/Articles/PainlessSoftwareSchedules.html