07-09-2015, 01:30 PM
Hi
Need test case scenario on Gmail login page
|
integration test scenarios for gmail login page
|
Hi
Need test case scenario on Gmail login page
15-04-2017, 02:15 PM
In integration tests, individual software modules are logically integrated and tested as a group. A typical software project consists of several software modules, coded by different programmers. The integration tests focus on verifying the communication of data between these modules.
Integration test case:
The integration test case differs from other test cases in the sense that it focuses primarily on interfaces and data / information flow between modules. Here priority should be given to integration links rather than to the unit functions that have already been tested.
Examples of integration test cases for the following scenario: The Gmail application has three modules: 'Login page', 'Mailbox' and 'Delete mails', and each of them is logically integrated.
Here, do not focus too much on the proof of the Home Page, since it has already been done in the Unitary Test. But check how it is linked to the mailbox page.
To find integration testing scenarios in the Gmail application, we must know the integration of turm in software testing.
So let's know about the turm integration test and its purpose.
Integration tests: -
The test of data flow between two modules is the integration test.
Example 1:-
Look at the image
![[Image: main-qimg-dba2017d930be55b1097d7bde643e5f0.webp]](https://qph.ec.quoracdn.net/main-qimg-dba2017d930be55b1097d7bde643e5f0.webp)
This is a basic prototype of data flow between different modules of Gmail backend scripts.
As the Interation test is to verify the flow of data between two modules, the scenarios are as follows:
Scenarios: -
1. If a mail in Inbox is reported as spam, the email will appear on the spam link. Check the same email in Spam Link. Mail will now not be displayed in Inbox.
2. The same mail (from inbox to Spam) in Spam will be moved back to Inbox.
3. If an email in Inbox will be deleted. It will pass to Bin.
4. Again, the same mail (from the Inbox to the Tray) in the Tray can be moved to Inbox.
Soon……
As we observe that each scenario contains the data flow (mail) between two modules (folder).
Integration test case:
The integration test case differs from other test cases in the sense that it focuses primarily on interfaces and data / information flow between modules. Here priority should be given to integration links rather than to the unit functions that have already been tested.
Examples of integration test cases for the following scenario: The Gmail application has three modules: 'Login page', 'Mailbox' and 'Delete mails', and each of them is logically integrated.
Here, do not focus too much on the proof of the Home Page, since it has already been done in the Unitary Test. But check how it is linked to the mailbox page.
To find integration testing scenarios in the Gmail application, we must know the integration of turm in software testing.
So let's know about the turm integration test and its purpose.
Integration tests: -
The test of data flow between two modules is the integration test.
Example 1:-
Look at the image
This is a basic prototype of data flow between different modules of Gmail backend scripts.
As the Interation test is to verify the flow of data between two modules, the scenarios are as follows:
Scenarios: -
1. If a mail in Inbox is reported as spam, the email will appear on the spam link. Check the same email in Spam Link. Mail will now not be displayed in Inbox.
2. The same mail (from inbox to Spam) in Spam will be moved back to Inbox.
3. If an email in Inbox will be deleted. It will pass to Bin.
4. Again, the same mail (from the Inbox to the Tray) in the Tray can be moved to Inbox.
Soon……
As we observe that each scenario contains the data flow (mail) between two modules (folder).
|
« Next Oldest | Next Newest »
|
