From 90bd26623c2f43002873b532049491303cf5c2e4 Mon Sep 17 00:00:00 2001 From: Grzegorz Karaluch Date: Mon, 5 Feb 2024 08:50:47 +0100 Subject: [PATCH] Apply suggestions from code review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Michał 'Disper' Drzewiecki --- docs/contributor/testing-strategy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/contributor/testing-strategy.md b/docs/contributor/testing-strategy.md index 884f576f..6b6598f7 100644 --- a/docs/contributor/testing-strategy.md +++ b/docs/contributor/testing-strategy.md @@ -14,7 +14,7 @@ We investigate the product by separating it into layers: 2. Business Features - Combines the business logic into feature which is consumed by our customers. + Combines the code into feature which is consumed by our customers. 3. Product Integration @@ -22,7 +22,7 @@ We investigate the product by separating it into layers: For each layer, there is a dedicated testing approach used: -1. **Unit Testing for Business Logic:** Writing and executing tests for individual functions, methods, and components to verify their behavior and correctness in isolation. +1. **Unit Testing for Code:** Writing and executing tests for individual functions, methods, and components to verify their behavior and correctness in isolation. 2. **Integration Testing for Business Features:** Validating the integration and interaction between different components, modules, and services in the project. 3. **End-to-End Testing:** Testing the application as a whole in a production-like environment, mimicking real-world scenarios to ensure the entire system functions correctly, is performing well and secure.