Clean up

Author: mbareta

recipes/automated-testing.md

@@ -2,7 +2,7 @@
 
 ## Types of Automated Tests
 
-There are different approaches to testing and depending on the level of the
+There are different approaches to testing, and depending on the level of the
 entry point, we can split tests into following categories.
 
 - **Unit Tests**
@@ -18,8 +18,8 @@ internal purposes, this should be considered the naming convention.*
 
 These are the most isolated tests that we can write. They should take a specific
 function/service/helper/module and test its functionality. Unit tests will
-usually require mocked data, but since we're testing that specific input produces
-specific output, the mocked data set should be minimal.
+usually require mocked data, but since we're testing the case when specific
+input produces specific output, the mocked data set should be minimal.
 
 Unit testing is recommended for functions that contain a lot of logic and/or branching.
 It is convenient to test a specific function at the lowest level so if the logic
@@ -36,7 +36,7 @@ tests for the publically available endpoints.
 
 **TODO**: do we want to write anything about mocking the DB data/seeds?
 
-In these tests we should cover *at least* the following:
+In these tests we should cover **at least** the following:
 - **authorization** - make sure only logged in users with correct role/permissions
 can access this endpoint
 - **success** - if we send correct data, the endpoint should return response that
@@ -57,27 +57,29 @@ produces the expected result.
 
 Usually, these tests will cover a large portion of the codebase with least
 amount of code.
-Because of that, they can be the first tests to be added to a project that
+Because of that, they can be the first tests to be added to existing project that
 has no tests or has low test coverage.
 
 These tests should not cover all of the use cases because they are the slowest to
-execute. If we need to test edge cases, we should try to implement those at a
-lower level, like integration or unit tests.
+run. If we need to test edge cases, we should try to implement those at a lower
+level (integration or unit tests).
 
 ### Performance Tests
 
-These types of tests will reproduce a usual user scenario and then simulate a group
-of concurrent users and measure the server's response.
+These types of tests will reproduce a typical user scenario and then simulate a
+group of concurrent users and then measure the server's response time and overall
+performance.
 
 They are typically used to stress test the infrastructure and measure the throughput
-of the application.
+of the application. They can expose bottlenecks and identify endpoints that need
+optimization.
 
 
 ### Visual Tests
 
 The type of test where test runner navigates to browser page, takes screenshot
 and then compares the future screenshots with the reference screenshot.
 
-These types of tests will cover a lot of ground with the least effort and
-can indicate a change in the app. The downside is that they're not very precise
+These types of tests will cover a lot of ground with the least effort and can
+easily indicate a change in the app. The downside is that they're not very precise
 and the engineer needs to spend some time to determine the cause of the error.