What tests are most important at what stages of project development?

Question

Software testing

http://www.softwaretestinghelp.com/types-of-softwa...
https://www.testingexcellence.com/types-of-softwar...
After reading, as I understand it, it can be divided into 2 stages if you run tests at the 4th stage or the 3rd, everything will fall into the database;)
1 - Alpha (dev)
2 - Beta (dev)
3 - Stage (dev, but hosted)
4 - Production
So, according to the link above, 46 types tests, however, as I understand it, there are more than 100+ of them, and I'm a little confused about which and when to apply.
Can you please tell me what other tests are there, types?
How best to group and organize them at what stages of project development?
What tests and when should you pay more attention?
I have a Unit test that checks the creation of a user.Where to shove it? And as I understand it, you need to file another half a hundred tests of various types for user registration?)

Answer 1

I don't know how about those 46, but to begin with, run at least a mandatory program:
1. unit tests that check that the module is generally ok - run before the commit or in the developer's branch;
2. smoke tests that check that the assembly is generally ale - run before the merge to the master;
3. integration and functional tests to check the assembly for regress - run immediately after the commit to the master;
4. security tests to check for typical vulnerabilities - run if the master branch assembly passed the previous tests;
5. fuzzy and manual tests before release to production - making sure that the main scenarios and new functionality work as intended.
This should be enough for the next year, then ask about other types of tests :)