diff --git a/website_and_docs/content/documentation/test_practices/testing_types.en.md b/website_and_docs/content/documentation/test_practices/testing_types.en.md
index 849dc00860fb..14dcd78c6d94 100644
--- a/website_and_docs/content/documentation/test_practices/testing_types.en.md
+++ b/website_and_docs/content/documentation/test_practices/testing_types.en.md
@@ -42,6 +42,16 @@ done directly with Selenium by simulating expected returns.
 This simulation could be done by record/playback or through 
 the different supported languages as explained in this documentation.
 
+### Integration Tests
+
+Integration tests verify the interactions between different components or modules of a system. Several modules are together tested. The purpose of Integration tests is to make sure that all modules integrate and work together as expected. Automated integration tests help ensure that these interactions work as expected and that integrated components function properly together.
+>For example,  **_Testing the flow of placing the order for an item in an ecommerce website along with payment._**
+
+### System Tests
+
+System Testing is a complete fully integrated product Testing. It is an end-to-end testing where in testing environment is similar to the production environment. Here, we navigate through all the features of the software and test if the end business / end feature works. We just test the end feature and don’t check for data flow or do functional testing and all.
+>For example,  **_Testing the end to end flow from login to placing and order and rechecking the order in My Orders page and logoff from an ecommerce website._**
+
 ### Performance testing
 As its name indicates, performance tests are done 
 to measure how well an application is performing.