docs(why-automated-testing): change image and add Resource Saving p…

…oint

apps/archive/docs/engineering-playbook/testing/why-automated-testing.mdx

@@ -6,15 +6,7 @@ title: Why Automated Testing?
 
 ## Why should we use automated testing?
 
-```mermaid
-mindmap
-  root((Testing))
-    Documentation as a Code
-    Fast Defect Feedback
-    Design and Code Quality
-    Decrease bugs repetition
-    Confidence
-```
+![Why Automated Testing](/img/why-automated-testing.png)
 
 ### Documentation as Code
 
@@ -102,6 +94,21 @@ Why a separate `describe` block? Given the first point (Documentation as Code),
 from the main body of test cases, as they might not carry any significant information. These cases could be so specific 
 that they aren’t worth paying attention to when studying the module’s functionality or requirements.
 
+### Resource Saving
+
+The **Resource** is money and time:
+- Time of the engineers work = Money.
+- Time of the QA work = Money.
+
+It might seem that writing tests takes a lot of time. But in reality, it saves you time:
+- Less time spent on understanding the code due to the documentation in the tests.
+- Less time spent on code change due to better design and code quality.
+- Less time spent on debugging and manual testing due to fast defect feedback.
+- Less time spent on fixing new bugs due to confidence in the code.
+- Less time spent on fixing the same bugs due to bug repetition reduction.
+
+Less Time spent = Less Money spent = Resource Saving.
+
 ## Statistics
 
 To understand what other engineers think about test automation, let's look at some statistics: