Skip to content

Commit 71f7918

Browse files
Update testing_types.en.md (#1506)[deploy site]
Updated the page with integration and system testing details Co-authored-by: Sri Harsha <12621691+harsha509@users.noreply.github.com>
1 parent 6920715 commit 71f7918

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

website_and_docs/content/documentation/test_practices/testing_types.en.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,16 @@ done directly with Selenium by simulating expected returns.
4242
This simulation could be done by record/playback or through
4343
the different supported languages as explained in this documentation.
4444

45+
### Integration Tests
46+
47+
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.
48+
>For example, **_Testing the flow of placing the order for an item in an ecommerce website along with payment._**
49+
50+
### System Tests
51+
52+
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.
53+
>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._**
54+
4555
### Performance testing
4656
As its name indicates, performance tests are done
4757
to measure how well an application is performing.

0 commit comments

Comments
 (0)