'There is nothing called positive or negative when your intention is to deliver a quality product. In Modern Testing there is nothing called as Test scenarios, test cases, positive/negative.'
Quality is ensuring the agreed upon quality factors between the vendor and client. which implicitly means Customer satisfaction.
Focus during delivery of the product is quality(as is the agreement). Client is least bothered about the metrics which we supply to ensure the quality(in your terms test execution results). For client it's Software FIT for use with his expectation.
For Example:
Everyone of us are using Windows OS, we know that Microsoft is the manufacturer. From our point of view we are least bothered about the number of defect reported, test cases executed, pass/fail etc etc(metrics in OS development @ MS). We want a OS FIT for use.
IF users have a problem(s) while using, MS provides FIX/Update/Patch/Service pack(for licensed users ;)). What all MS goes through during this, END-Users are least bothered/worried. Few fixes land MS in COURT
Now imagine, why Users are interested in MS-OS only? when there are other OS available as well. The answer is simple Customer Satisfaction, nothing but Quality.
If MS were focused on Metrics/Measures was this possible?
Delivering a product/app is easy, delivering a QUALITY product is challenging.
In Manual testing of an application- we should go through all these kinds of testing, but if we need the documentation for testing activity - we have to prepare the test case of - positive testing, negative testing , test scenario etc