This is a Performance Testing technique, also called Soak Testing or Longevity Testing. Checks for memory leaks or other performance issues that may occur with prolonged execution under expected load on continual basis or without load staying idle.
Testing the software for end-to-end functional flows in a complete application environment that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
This is also known as Equivalence Class Partitioning. This is software testing technique but not a type of testing. This technique is used in black and grey box testing. This technique classifies test data into positive and negative equivalence classes ensuring both positive and negative scenarios are tested.
This focuses on error handling capabilities of the software, response of the software on exceptions, messages it renders to users in case of expected and unexpected errors. This is called Yellow-Box Testing.
Testing which covers all combinations of input values and preconditions for an element of the software under test.
Exploratory testing is an informal type of testing conducted to learn the software at the same time looking for errors or application behavior that seems non-obvious. Exploratory testing is usually done by testers but can be done by other stake holders as well like Business Analysts, developers, end users etc. who are interested in learning functions of the software and at the same time looking for errors or behavior is seems non-obvious.