This is the abridged summary of team tech talk ;-)

Type of Testing

Amount of tests from high to low:

Unit tests: functions in your code, you use Mock/Fake for external dependencies, focus on good coverage.
Functional tests: isolated functionality of single component, whthin its boundaries, focus on business logic, every path should have a test.
Integration tests:** components are being actively developed are involved, focus on different combinations, not all the functions.
E2E tests: often the first “real” env being tested, inevitable for a product, need to exercise main product features(happy path), for example: create, update, delete a PC, focus on main use cases.
CUJ(critical user journey) tests: usually manual process, like UAT(user acceptance test), focus on common user cases, for example, not just only create a PC but also deploy and run the workload.

CUJ can help to improve the user experience, while UAT can help to ensure that the system meets the user’s requirements.

Regression test(can be of anyone above) ensure new feature does not break exsiting code.