What is the sequence of performing functional and non-functional types of software testing?

Question

Software testing

For example, there are the following types of testing:

1. Functional testing
   
2. User Interface Testing (GUI Testing)
   
3. Security and Access Control Testing
   
4. Interoperability Testing
   
5. All types of performance testing:
   • load testing (Performance and Load Testing)
     
   • stress testing
     
   • stability or reliability testing (Stability / Reliability Testing)
     
   • Volume Testing
   
   
6. Installation testing
   
7. Usability Testing
   
8. Failover and Recovery Testing
   
9. Configuration Testing
   
10. Smoke Testing
    
11. Regression Testing
    
12. Re-testing
    
13. Build Verification Test
    
14. Sanity testing or consistency/health testing (Sanity Testing)
    

Cases:
1) There is a product, the assembly of which was released for testing for the first time and it is necessary to use the maximum possible number of types of testing for this case.
2) The bug was fixed, the build was sent for testing
3) The functionality was improved, the build was sent for testing

Are my answers correct?

Case #1:

1. Assembly testing - with unit tests we check all application modules, whether everything works as planned
   
2. Installation Testing - Checking Successful Rollout
   
3. Smoke testing - checking the basic functionality without going deep
   
4. Sanitary testing - checking the main functionality, going a little deeper, but checking the most important (small amount of time to check)
   
5. Functional testing - we check the direct functionality of the application (it can be deep), we are looking for non-standard cases
   
6. Interaction testing - we check the interaction between different modules (partially implemented in unit tests, partly we check the work on the UI)
   
7. User interface testing - we check the presence of all buttons, fields, lists, pictures, notifications, etc. in accordance with the requirements, the correct behavior when changing the browser scale
   and in other situations
   
8. Security Testing
   
9. Configuration testing - testing the behavior of a web application in different browsers, for example
   
10. Testing for failure and recovery
    
11. All kinds of performance testing
    
12. Usability testing (optional, with focus group, metrics and report analysis)
    

Case #2:

1. Build testing
   
2. Installation testing
   
3. Retesting a fixed bug
   
4. Smoke testing
   
5. Regression Testing
   

Case #3:

1. Build testing
   
2. Installation testing
   
3. Functional testing
   
4. Smoke testing
   
5. Regression Testing
   

Answer 1

Svyatoslav Kulikov "Software Testing. Basic Course"
Sam Kaner "Software Testing" Go for it
!

Answer 2

The question does not have a clear answer, these are questions from interviews "to speculate"