SOFTWARE TESTING TOOL (TESTLINK)

Software Testing (SWE2005)

Review-1
Team Members:
• Srividya S - 20MIS0083
• Debdatta Ray - 20MIS0112

Tool Name: TestLink

Summary of the tool:
TestLink is a widely used open source web-based test management system that
facilitates software quality assurance. It is developed and maintained by Teamtest.
The platform synchronizes both requirements specification and test specification
together. TestLink offers support for test cases, test suites, test plans, test projects
and user management, as well as various reports and statistics.
User can create test project and document test cases using this tool. With TestLink
we can create an account for multiple users and assign different roles to each user.
The admin user can manage test cases assignment task. It supports both automated
and manual execution of Test cases. Testers can generate Test Plan and Test Report
very quickly with this tool. It supports test reports in various formats like Excel, MS
word, and HTML formats. Apart from these, it also supports integration with many
popular Defect tracking system like JIRA, MANTIS, BUGZILLA, TRAC, etc. Since it is
a web based tool, multiple users can access its functionality at the same time with
their credentials and assigned roles.
Software Requirements:
TestLink requires these following programs,

• MySQL 4.0.x or MariaDB or PostgreSQL

• PHP 4.3.x
• Webserver (Apache 1.3.x or 2.0.x and higher, IIS 3 and higher, etc.)
• Any Operating system
Hardware Requirements:
For a better efficiency of TestLink we need,

 2 x CPU 2GHz.
 4 GB RAM (but 16 GB is good for large sites)
 40 GB hard drive.

Installation Procedure
You can install all the requirements separately either manually or through an
automatic process to use TestLink.

Installation of System Requirements

There are many all-in-one packages available and can automatically install in the
system by exe file. Here, we will take the help of XAMPP to install the pre-
requisites easily.
Step 1 − Go to https://www.apachefriends.org/index.html and click XAMPP for
Windows as shown in the following screenshot.
Step 2 − A pop-up will be displayed to save the file. Click Save File. It will start to
download the file.

Step 3 − Run the .exe file to run the installation wizard. After clicking the .exe file,
the XAMPP Setup wizard is displayed as shown in the following screenshot. Click
Next.
Step 4 − Next, the wizard displays all the component files (shown in the following
screenshot) that will be installed. Click Next after selecting the components.

Step 5 − Provide a folder name where XAMPP will be installed and click Next.
Step 6 − Ready to Install wizard is displayed. Click Next to start the installation
Step 7 − After successful installation, it will prompt to start the control panel.
Select the checkbox and click Finish. It will open the XAMPP control panel as
displayed in the following screenshot.
Step 8 − Click the Start button for Apache and MySQL required for TestLink as
shown in the above screenshot.
Step 9 − To verify whether all the pre-requisites such as Apache, PHP and MySQL
are installed properly, navigate to any of the browser and type http://localhost.
Then, press Enter.
Step 10 − It will display the dashboard of XAMPP. Click phpAdmin at the right top
corner of the screenshot.

It will display General Settings, Application Settings, Details of Database, Web

Server and phpMyAdmin as shown in the following screenshot.
Install and Launch TestLink

After successful installation of XAMPP, we need to work with TestLink.

Step 1 − Go to https://sourceforge.net/projects/testlink/ and click Download.
Step 2 − Now unzip the downloaded .tar file and rename the folder name as
TestLink.
Step 3 − Go to XAMPP folder where it is installed and navigate to htdocs folder.
Place the TestLink folder here as shown in the following screenshot.

Step 4 − Go to TestLink package and open “config.inc.php” file, update path

“$tlCfg→log_path” and “$g_repositoryPath” as below −
$tlCfg→log_path = ‘D:/xampp/htdocs/testlink/logs/’;
$g_repositoryPath = ‘D:/xampp/htdocs/testlink/upload area/’;
Step 5 − Now open a browser and type http://localhost/Testlink in the navigation
bar and press Enter. It will display the installation page of TestLink.
Step 6 − Click New Installation.
Step 7 − Check the checkbox for Terms and Conditions and click the Continue
button.
Step 8 − Click Continue.
Step 9 − In the next step, Database Admin and Admin password is required to
define MySQL access. TestLink admin username/password can be anything given
by the user.
Database login/password: root/<empty> (Default login/password of MYSQL for
xampp)
Step 10 − Click “Process TestLink Setup” button. You should see the TestLink
“Installation was successful!” message being displayed.
Step 11 − Now again navigate to http://localhost/testlink
You will see the login page

Merits of TestLink

• It supports multiple projects

• Easy export and import of test cases
• Easy to integrate with many defect management tools
• Automated test cases execution through XML-RPC
• Easy filtration of test cases with version, keywords, test case ID and version
• Easy to assign test cases to multiple users
• Easy to generate test plan and test reports in various formats
• Provide credentials to multiple users and assign roles to them

Demerits of TestLink
• TestLink does not allow the provision to test mobile applications.
 • With the advancement of the web technologies and increased complexities,
sometimes the tester finds it difficult to use this tool for test management.
• There are other powerful tools available in the market with increased
flexibilities and options with which TestLink may not compete well.

References
1. https://www.guru99.com/testlink-tutorial-complete-guide.html
2. https://www.softwaretestingclass.com/tutorial-1-getting-started-with-
testlink-test-management-tool/
3. https://www.tutorialspoint.com/testlink/testlink_installation.htm
4. https://testlink.org/
5. https://en.wikipedia.org/wiki/TestLink
 SOFTWARE TESTING PROJECT
Software Testing (SWE2005)
Review-2
Team Members:
• Srividya S - 20MIS0083
• Debdatta Ray - 20MIS0112

Tool Name: TestLink

Application Name: Gmail webpage, its login functionality, compose mail, spam
folder, sent and trash folder.
Data input: We give manual real time data and test the functionality of the
gmail login, compose mail, spam folder, sent and trash folder.
Test Cases:
1. Gmail compose
• Test Suite: Gmail Compose mail
GTC-1: Enter mail id details
Preconditions
1. User should have acess to internet.
2. User should have valid email id and password.

#: Step actions: Expected Results: Execution notes: Execution

Status:
When valid username and
1 open gmail gmail should be password are entered it navigates Passed
opened. to the homepage

2 Click on It should open a New window opens on clicking the Passed

Compose tab.
window to compose tab
compose mail.

Enter the reciever The textbox should

3 email id accept the entered The textbox accepts the entered Passed
data data

4 Enter 'cc' and The textbox should The textbox accepts the entered Passed
'bcc' fields. accept the entered data
 data

5 Enter subject. The textbox should The textbox accepts the entered Passed
accept the entered data
data

6 Enter contents of The textbox should The textbox accepts the entered Passed
mail accept the entered data
data

7 click on send mail should be The email is send. Passed

send to the
reciever

GTC-2: send mail with confidential mode

Preconditions
1. User should have acess to internet.
2. User should have valid email id and password.

#: Step actions: Expected Results: Execution notes: Executi

on
Status:

1 click on A window should be opened New window opens Passed

compose. to compose a mail on clicking compose
tab

2 Click on 'Turn Confidential mode should be Confidential mode is Passed

on turned on. turned on
confidential
mode'.
Recipients
3 Set an If you choose "SMS receive the Passed
expiration passcode," recipients will get passcode by text
date and a passcode by text message. manual message
passcode

4 Click Save The details should be saved The changes are saved Passed

GTC-3: Unsend mail

Preconditions
 1. User should have acess to internet.
2. User should have valid email id and password.

#: Step Expected Results: Execution notes: Executi

actions: on
Status:

Compose In the bottom left, you'll see A message pops up

1 a mail "Message sent" and the option to after successfully Passed
and send "Undo" or "View message". sending the mail
it.

2 Click Undo The mail should be unsend. The mail is unsend Passed

• Test Suite : Gmail draft save

GTC-4: Automatic saving
Preconditions
1. User should have acess to internet.
2. User should have valid email id and password.

#: Step actions: Expected Results: Execution Execution

notes: Status:

1 Stop typing or editing a Gmail automatically The mail is Passed

mail for 3 seconds. saves the mail as saved as a
draft. draft.

GTC-5: Esc key method

#: Step actions: Expected Results: Execution notes: Executi

on
Status:

1 While The mail is saved as The mail is saved as a Passed

composing a draft and the draft and the window
mail, click on composition window is is closed
Esc closed.

• Test Suite : Gmail draft delete

GTC-7: Deleting a draft mail
 Preconditions
1. User should have acess to internet.
2. User should have valid email id and password.

#: Step actions: Expected Results: Execution notes: Execution

Status:

1 Click on the 'Drafts" option List of saved All the drafts Passed
on left side panel drafts appear saved appear

2 Check the box next to the The draft gets The desired Passed
draft to be deleted selected draft is
selected

3 Click on 'Discarded drafts' The draft is The draft is Passed

on top of the page. deleted. deleted

2. Sent folder:
• Test Suite : Sent tab
GTC-8: Access sent folder
Preconditions
1. User should have acess to internet.
2. User should have valid email id and password.

#: Step actions: Expected Results: Execution notes: Execution

Status:

1 log into the the user must be user is directed to Passed

gmail directed to the homepage
account. homepage
all the emails send by
2 click on the list of mails send appears. the user appears Passed
sent tab.

3 click on the the contents of the the selected mail send Passed
required mail. selected mail should opens.
open.

GTC-9: Archive sent mail

 Preconditions
1. User should have acess to internet.
2. User should have valid email id and password.

#: Step actions: Expected Results: Execution notes: Execution

Status:

1 Cick on the 'sent' tab A list of emails all the emails Passed
send appears send by the user
appears

2 click on the box along The email specific email gets Passed
the email to be selected. should get selected
selected.
3 the selected email is Passed
Click on the archive icon The email archived
should get
archived
GTC-10: delete send mails from folder
Preconditions
1. User should have acess to internet.
2. User should have valid email id and password.

#: Step actions: Expected Results: Execution notes: Execution

Status:

1 Click on 'send' tab List of emails send all the emails send by Passed
should appear. the user appear

2 Check the box The email the specific mail is Passed

along the should get selected
required email selected

3 Click on the trash icon The email the selected email is Passed
should get deleted.
deleted
3. Spam folder:
• Test Suite : Gmail spam filter
Test Case GTC-1: Source IP check
Preconditions:

1. The reciever/user should be connected to internet

2. The user mail id should be valid

Step actions: Expected Results: Execution Status:

Open Gmail Gmail should be opened Passed

If IP reputation is not good direct

Check IP warmup
Check IP server configuration
Check for TLS Authentication
Check for Return Path Certificate
Check for 'reply to' email address
Test Case GTC-2: Domain reputation
Preconditions:
Passed
it to spam
If the backend of the ESP is not
configured with proper email
header, authentication
Passed
parameters, and encryption then
the emails will get rejected and
moved to spam
If TLS authentication not present,
lower the IP reputation and move Passed
the email to spam
If the email is not return path
Passed
approved, direct it to spam
If the header is "no-reply" and has
been reported spam in the past or
Passed
blacklisted, reject the email and
send it to spam

1. The reciever/user should be connected to internet

2. The user mail id should be valid

Step actions: Expected Results: Execution Status:

Open Gmail Gmail should be opened Passed

DMARC check If DMARC check failed send the email to spam Passed
If the email contains inconsistent volume direct it to
Email volume check Passed
spam
Check with previously marked as spam If an address is already marked as spam send it to Passed
list spam
Test Case GTC-3: Sending rate
Preconditions:

1. The user should be connected to internet

Step actions: Expected Results: Execution Status:

Open Gmail Gmail should be opened Passed

If throttling and spreading is not Passed

Check with rate control algorithm
working, send it to spam

Test Case GTC-4: Content and authentication

Preconditions:

1. The user should be connected to the internet

2. The domain should be valid

Step actions: Expected Results: Execution Status:

Open Gmail Gmail should be opened Passed

Check for trigger words in email If spam words found, redirect the
Passed
body and subject line email to spam

Grammar errors, poorly written

email copy, big fonts and flashy Is this condition is satisfied, send
Passed
color, a lot of exclamations and the email to spam
symbols

If many links or shortened URLs are

Links and shortened URL Passed
used in the email, direct it to spam

If the email doesn't follow the

Email design protocols Passed
protocols send it to spam

Missing key elements and spam

Key elements and spam laws check laws violation then move the mail to Passed
spam
Flag the email and send warning
Unsafe OR binary attachment Passed
note

• Test Suite : Gmail mark as spam

Test Case GTC-5: Mark as spam
Preconditions:

1. The user should be connected to internet

2. User should be logged into gmail with valid address

Step actions: Expected Results: Execution Status:

Open gmail Gmail should be opened Passed

Select one or more emails The emails should be selected Passed

The emails should be marked as

Click report spam Passed
spam

The emails should be stored and

Send copy of emails to server Passed
analysed

• Test Suite : Gmail unmark as spam

Test Case GTC-6: Unmark as spam

Preconditions:

1. The user should be connected to internet

2. User should be logged into gmail with valid address

Step actions: Expected Results: Execution Status:

Open Gmail Gmail should be opened Passed

On the left, navigate to "spam" Spam folder should be opened Passed

Open the required email The email should be opened Passed

• Test Suite : Gmail delete spam

Test Case GTC-7: Deleting emails in spam

Preconditions:

1. The user should be connected to internet

2. User should be logged into gmail with valid address

Step actions: Expected Results: Execution Status:

Open Gmail Gmail should be opened Passed

On the left, navigate to "spam" Spam folder should be opened Passed

Select specific emails Emails should be selected Passed

The selected emails should be

Now click Delete forever Passed
deleted

At the top, click Delete all spam

All mails should be deleted Passed
messages now

• Test Case GTC-8: Deleting long term spam emails

Preconditions:

1. The user should be connected to internet

2. User should be logged into gmail with valid address

Step actions: Expected Results: Execution Status:

Open Gmail Gmail should be opened Passed

Check date of email for checking

The term in spam is calculated Passed
number of days on spam

Check if the count exceeds or

Delete the emails Passed
equals 30

4. Trash folder:

• Test Suite : Gmail delete mail

Test Case GTC-9: Deleting a single mail

 Preconditions:

1. The user should be connected to internet

2. User should be logged into gmail with valid address

Step actions: Expected Results: Execution Status:

Open Gmail Gmail should be opened Passed

Open the required email from The selected email should be

Passed
the email thread opened

Next to 'Report spam' button, click

The selected email should be
'Delete' button represented by a Passed
moved to trash
trash can.

Test Case GTC-10: Deleting multiple emails

Preconditions:

1. The user should be connected to internet

2. User should be logged into gmail with valid address

Step actions: Expected Results: Execution Status:

Open Gmail Gmail should be opened Passed

Check the boxers to the left of the The emails that are clicked on
Passed
emails should be selected

At the navigation bar we can find All the selected emails should be
Passed
delete button, click on it moved to trash

Test Case GTC-11: Deleting all emails in a category

Preconditions:

1. The user should be connected to internet

2. User should be logged into gmail with valid email address

Step actions: Expected Results: Execution Status:

On your computer, open Gmail Gmail should be opened Passed

At the top left, check the box to

select all messages. If you have
Chosen emails should be selected Passed
more than one page of messages,
click Select all conversations.

All the selected emails should be

At the top, click delete button Passed
moved to trash

Test Case GTC-12: Empty trash

Preconditions:

1. The user should be connected to internet

2. User should be logged into gmail with valid email address

Step actions: Expected Results: Execution Status:

On your computer, open Gmail Gmail should be opened Passed

On the left side of the page, click

More options should be displayed Passed
More

Scroll to trash and open it Trash folder should be opened Passed

Check the box next to messages

All the selected emails should be
you want to permanently delete. Passed
deleted from trash
Then click Delete forever

To delete all messages in your All the emails in trash should be

Passed
trash, click Empty Trash now deleted forever

• Test Suite : Gmail recover email

Test Case GTC-13: Check emails in trash

Preconditions:

1. The user should be connected to internet

2. User should be logged into gmail with valid email address

Step actions: Expected Results: Execution Status:

On your computer, open
Gmail should be opened Passed
Gmail

On the left side of the More options should be

Passed
page, click More displayed

Select Trash Trash should be opened Passed

Click on an email that you Selected email should be

Passed
want to check opened

Test Case GTC-14: Recover emails from trash

Preconditions:

1. The user should be connected to internet

2. User should be logged into gmail with valid email address

Step actions: Expected Results: Execution Status:

On your computer, open
Gmail should be opened Passed
Gmail

On the left side of the More options should be

Passed
page, click More displayed

Open Trash Trash should be opened Passed

Check the box next to the Checked emails should be

Passed
emails you want to move. selected

Click Move to menu on the top A list of possible destinations

right corner of the navigation for the email to be moved Passed
bar should be displayed.

Choose where you want to The emails should be moved

Passed
move the emails to the selected destination
Test Report:
TestPlan:
Test Plan: Compose folder Testplan
This testplan is to test the compose folder testplan.
This includes testing the following features:

• Compose a mail.
• Saving the mail as draft
• Acessing the draft folder and editing them.
• Deleting the drafts.
• Accessing the sent folder
• Archiving or deleting the send emails from inbox.

Test Plan: Spam folder Testplan

This testplan is to check the spam folder functionality in gmail. This includes
testing for the following features

• Gmail spam filter feature

• Marking an email as spam
• Unmarking an email as spam
• Deleting a spam email

Test Plan: Trash folder Testplan

This testplan is to check the trash folder functionality in gmail.

This includes testing for the following features

• Deleting one or more emails

• Deleting emails from trash
• Checking emails in trash
• Recover emails from trash
Testing Methodology:
We use Manual testing for this project. We test the gmail webpage with no
prior knowledge of its internal workings. The tester provides an input, and
observes the output generated by the system under testing. This makes it
possible to identify how the system responds to expected and unexpected user
actions, its response time, usability issues and reliability issues.
Project screenshot:
For spam folder module:
Creating a Test Project:
Creating a Test Plan:

Build Creation:
Creating Test suite:
Creating a Testcase:
Assigning test case to test plan:

Creating Users and Assigning Roles:

Writing Requirements:
Assigning requirement to test-cases:

Executing a test case:

Generating Test Reports:
Export Test case/ Test Suite:
References
1. https://www.guru99.com/testlink-tutorial-complete-guide.html
2. https://www.softwaretestingclass.com/tutorial-1-getting-started-with-
testlink-test-management-tool/
3. https://www.tutorialspoint.com/testlink/testlink_installation.htm
4. https://testlink.org/
5. https://en.wikipedia.org/wiki/TestLink
 SOFTWARE TESTING TOOL (TESTLINK)
Software Testing (SWE2005)
Review-3

Members:
• Srividya S (20MIS0083)
• Debdatta Ray (20MIS0112)

Project Description:
To test the functionalities of gmail homepage

Module Description:
The project tests the following functions of gmail homepage:
1. Compose folder
2. Spam folder
3. Trash folder
4. Send folder
Compose folder:
The compose tab is used to compose emails by the user. The project contains the
following test suits-
1.1. Gmail Compose mail

• GTC-1: Enter mail id details

• GTC-2: send mail with confidential mode
• GTC-3: Unsend mail
1.2.Gmail draft save
• GTC-4: Automatic saving
• GTC-5: Esc key method
1.3.Gmail draft delete
• GTC-7: Deleting a draft mail
Spam folder:
The spam folder is the storage space in gmail where the unwanted emails or the emails
that fail to reach the inbox and are flagged as spam by ESPs.
This module contains the following test suites
• Gmail spam filter
 GTC-1: Source IP check
 GTC-2: Domain reputation
 GTC-3: Sending rate
 GTC-4: Content and authentication
• Gmail mark as spam
 GTC-5: Mark as spam
• Gmail unmark as spam
 GTC-6: Unmark as spam
• Gmail delete spam
 GTC-7: Deleting emails
 GTC-8: Deleting long term spam emails
Trash folder:
Whenever we delete any email from inbox or different categories, the email
automatically is transferred to the Trash folder. That is, the deleted emails are not
deleted permanently at the time of deletion but can be found in Trash folder.
If the email stays for over 30 days in Trash folder it gets permanently deleted.
This module contains the following test suites
• Gmail delete mail
 GTC-9: Deleting a single mail
 GTC-10: Deleting multiple emails
 GTC-11: Delete all emails in a category
 GTC-12: Empty Trash
• Gmail recover email
 GTC-13: Check mails in Trash
 GTC-14: Recover emails from Trash
Send folder:
The send tab is used to access emails send by the users. The project contains the
following test suits-
1.1 Sent tab

• GTC-8: Access sent folder

• GTC-9: Archive sent mail
• GTC-10: delete send mails from folder

Demo and Screenshots:

Login to TestLink
Step 1 : Open the Testlink home-page and enter the login details

1. Enter the userID – admin

2. Enter the password
3. Click on the login tab
Creating a Test Project
Step 1: In the main window click on Test Project Management, it will open
another window

Step 2: Click on the tab “create” to create a new project.

Step 3: Enter all the required fields in the window like a category for a test
project, name of the project, prefix, description, etc. After filling all necessary
details, click on tab “Create” at the end of the window.
This will create your project “Gmail functionality testing” successfully.

Build Creation
A build is a specific release of a software

Step 1: Click on Builds/Releases under Test Plan from the home page

Step 2: In the next window, fill all necessary details for a software release and
click on create to save your release
 1. Enter the title name
2. Enter the description about the software release
3. Mark the check-box for status- Active
4. Mark the check-box for status- Open
5. Choose the date of release
6. Click on create a button

Creating Testsuite
Test suite is a collection of test cases which may be testing or validating the same
component. Following steps will explain how to create test suite for your project.

Step 1: Click on test specification option from the home page.

Step 2: On the right-hand side of the panel, click on the setting icon . It will
display a series of test operation.

Step 3: Click on the “create” tab for the test suite

Step 4: Fill-up all the details for test-suite and click on save it tab.

1. Enter the test suite name

2. Enter the details about your test suite
3. Click on save button to save the details of test-suite
Creating a Testcase
Testcase holds a sequence of test steps to test a specific scenario with an
expected result. Below steps will explain how to create a test-case along with test
steps.

Step 1: Click on the test suite folder on the left side of the panel under a folder
tree structure

Step 2: Click on the setting icon in the right side panel. List of test case operations
will be displayed on the right side panel
Step 3: New window will open, to create test cases click on create a button in
test-case operations
Step 4: Enter the details in the test case specification page
Step 5: After entering the details, click on “create” button to save the details. The
test-case for ‘Gmail compose mail’ is created successfully
Step 6: Click on test-case from the folder, as shown above, it will open a window.
Click on “create steps” button in a test case. It will open a test case step editor
Step 7: It will open another window on the same page, in that window you have
to enter the following details

1. Enter the step-action for your test case

2. Enter the details about the step action
3. Click save it and add another step action OR click save and exit tab if there
is no more test step to add

Step 8) Once you save and exit the test step, it will appear like this
Assigning test case to test plan
For test case to get executed, it should be assigned to test plan. Here we will see
how we can assign a test-case to test plan.

Step 1) Click on the setting icon on the test panel. It will show the list of
operations.

Step 2) Click on “Add to Test Plans”

Step 3) New window will open, search your project

1. Mark the checkbox against your test plan

2. Click on add button
This will add your test case to your Test Plan.

Writing Requirements:
Step 1: From the navigation bar select the “Requirements Link”, it opens the
Requirement page.

Step 2: From the requirement page, on the right side of the panel click on
“create” button

Step 3: A new window will open, enter all the details like

1. Document ID
2. Title name
3. Requirement Description
4. And Click “Save” button

For the type, you can choose the option from the drop-down- here we
chose “User Requirement Specification”

Step 4: It should create Requirement specification and displayed on the left side
panel under the project title.

Step 5: Select the setting button from requirements specification home-page. It

will open another window.

Step 6Click “Create” tab under Requirement Operations.

Step 7: Fill out all the specified details and click the “Save” button

1. Enter the document ID

2. Enter the title name
 3. Enter the description
4. Enter the status-whether it’s in draft, rework, review, not testable, etc.
Here we chose valid
5. Enter the type – user interface, non-functional, informational, feature, etc.
Here we chose use case
6. Enter the number of test cases needed
7. Enter “Save” button at the end

Assigning requirement to test-cases

In Testlink, Requirement can be connected to test cases. It is a very crucial feature

in order to track test coverage based on requirements. In test reports, you can
verify which requirements are not covered and act on them to append in test
suites for maximum test coverage

Step 1: From the test specification section open any single test case and click on
requirement icon
Step 2: To assign requirements specification to test case you have to follow the
following steps

1. Scroll the drop down box to select the requirements specification

2. Mark the requirement checkbox
3. Click on “assign” tab

Executing a test case

Step 1: From the navigation bar click on the “Test Execution” link. It will direct you
to the Test Execution Panel.

Step 2: Pick the Test case you want to run from the left side panel

Step 3: Once you have selected the test cases, it will open a window.

Step 4: Follow the following steps

1. Enter the notes related to test case executed

2. Select its status

Step 5: On the same page, you have to fill similar detail about the execution of
test-case. Fill the details, select the status and then click on “save execution”.
Generating Test Reports
Step 1: From the navigation bar, click on Test Reports option

Step 2: From the left side panel, select “Test Report” link

Step 3: To generate a report follow the following steps

1. Mark and unmark the option you want to highlight in your test report
2. click on your project folder
Test Report:
11/15/21, 8:24 PM testreport Compose folder Testplan

TestLink Community [configure $tlCfg->document_generator->company_name]

Test Plan Execution Report

Test Project: Gmail functionality testing

Test Plan: Compose folder Testplan

Printed by TestLink on 11/15/2021

2012 © TestLink Community

127.0.0.1:81/testlink/index.php 1/9
11/15/21, 8:24 PM testreport Compose folder Testplan

Table Of Contents

1.1. Gmail Compose mail

GTC-1: Enter mail id details

GTC-2: send mail with confidential mode

GTC-3: Unsend mail

1.2. Gmail draft save

GTC-4: Automatic saving

GTC-5: Esc key method

1.3. Gmail draft delete

GTC-7: Deleting a draft mail

1.4. Sent tab

GTC-8: Access sent folder

GTC-9: Archive sent mail

GTC-10: delete send mails from folder

127.0.0.1:81/testlink/index.php 2/9
11/15/21, 8:24 PM testreport Compose folder Testplan

Test Project: Gmail functionality testing

This project is to test the functionality of gmail login,compose and spam component.

Test Plan: Compose folder Testplan

This testplan is to test the compose folder testplan.

This includes testing the following features:

Compose a mail.
Saving the mail as draft
Acessing the draft folder and editing them.
Deleting the drafts.
Accessing the sent folder
Archiving or deleting the send emails from inbox.

127.0.0.1:81/testlink/index.php 3/9
11/15/21, 8:24 PM testreport Compose folder Testplan

1.1. Test Suite : Gmail Compose mail

This test suit contains test cases to compose a mail.

Test Case GTC-1: Enter mail id details [Version : 1]

Author: debdatta
Preconditions:

1. The user should be connected to internet.

2. User should vave valid email id of reciever.

Execution
#: Step actions: Expected Results: Execution notes:
Status:

When valid username and password are entered

1 open gmail gmail should be opened. Passed
it navigates to the homepage

Click on It should open a window to

2 New window opens on clicking the compose tab Passed
Compose tab. compose mail.

Enter the
The textbox should accept
3 reciever email The textbox accepts the entered data Passed
the entered data
id

Enter 'cc' and The textbox should accept

4 The textbox accepts the entered data Passed
'bcc' fields. the entered data

The textbox should accept

5 Enter subject. The textbox accepts the entered data Passed
the entered data

Enter contents The textbox should accept

6 The textbox accepts the entered data Passed
of mail the entered data

mail should be send to the

7 click on send The email is send. Passed
reciever

Execution type: Manual

Estimated exec. duration
(min):
Priority: Medium
Requirements 02: Gmail compose [Version: 1]
Keywords: None
Execution Details
Build Compose folder- build 1
Tester debdatta
Execution Result: Passed
Execution Mode: Manual
Execution duration (min):

Test Case GTC-2: send mail with confidential mode [Version : 1]

Author: debdatta
Summary:

Confidential Mode works by storing your email in a secure space on Google servers in the cloud.
127.0.0.1:81/testlink/index.php 4/9
11/15/21, 8:24 PM testreport Compose folder Testplan

Preconditions:

The user should be connected to internet.

Execution
#: Step actions: Expected Results: Execution notes:
Status:

A window should be opened to compose a New window opens on clicking

1 click on compose. Passed
mail compose tab

Click on 'Turn on
2 Confidential mode should be turned on. Confidential mode is turned on Passed
confidential mode'.

Recipients receive the

Set an expiration If you choose "SMS passcode," recipients
3 passcode by text manual Passed
date and passcode will get a passcode by text message.
message

4 Click Save The details should be saved The changes are saved Passed

Execution type: Manual

Estimated exec. duration
(min):
Priority: Medium
Requirements 02: Gmail compose [Version: 1]
Keywords: None
Execution Details
Build Compose folder- build 1
Tester debdatta
Execution Result: Passed
Execution Mode: Manual
Execution duration (min):

Test Case GTC-3: Unsend mail [Version : 1]

Author: debdatta
Preconditions:

The user sould be connected to internet

It should be done within a short duration after the mail is sent.

Execution
#: Step actions: Expected Results: Execution notes:
Status:

Compose a
In the bottom left, you'll see "Message sent" and A message pops up after
1 mail and send Passed
the option to "Undo" or "View message". successfully sending the mail
it.

2 Click Undo The mail should be unsend. The mail is unsend Passed

Execution type: Manual

Estimated exec. duration
(min):
Priority: Medium
Requirements 02: Gmail compose [Version: 1]
Keywords: None
Execution Details
Build Compose folder- build 1
Tester debdatta
Execution Result: Passed
Execution Mode: Manual
Execution duration (min):

127.0.0.1:81/testlink/index.php 5/9
11/15/21, 8:24 PM testreport Compose folder Testplan

1.2. Test Suite : Gmail draft save

This test suit contains test cases to save the mail as draft.

Test Case GTC-4: Automatic saving [Version : 1]

Author: debdatta
Preconditions:

The user should be connected to the internet.

Execution
#: Step actions: Expected Results: Execution notes:
Status:

Stop typing or editing a mail for 3 Gmail automatically saves the The mail is saved as
1 Passed
seconds. mail as draft. a draft.

Execution type: Manual

Estimated exec. duration
(min):
Priority: Medium
Requirements 03: Gmail draft [Version: 1]
Keywords: None
Execution Details
Build Compose folder- build 1
Tester debdatta
Execution Result: Passed
Execution Mode: Manual
Execution duration (min):

Test Case GTC-5: Esc key method [Version : 1]

Author: debdatta
Preconditions:

The user should be connected to internet.

Execution
#: Step actions: Expected Results: Execution notes:
Status:

While composing a The mail is saved as draft and the The mail is saved as a draft and
1 Passed
mail, click on Esc composition window is closed. the window is closed

Execution type: Manual

Estimated exec. duration
(min):
Priority: Medium
Requirements 03: Gmail draft [Version: 1]
Keywords: None
Execution Details
Build Compose folder- build 1
Tester debdatta
Execution Result: Passed
Execution Mode: Manual
Execution duration (min):

127.0.0.1:81/testlink/index.php 6/9
11/15/21, 8:24 PM testreport Compose folder Testplan

1.3. Test Suite : Gmail draft delete

This test suit contains test cases to delete drafts.

Test Case GTC-7: Deleting a draft mail [Version : 1]

Author: debdatta
Preconditions:

The user should be connected to internet

The email must be saved as a draft.

Execution
#: Step actions: Expected Results: Execution notes:
Status:

Click on the 'Drafts" option on left side List of saved drafts All the drafts saved
1 Passed
panel appear appear

Check the box next to the draft to be The desired draft is

2 The draft gets selected Passed
deleted selected

Click on 'Discarded drafts' on top of the

3 The draft is deleted. The draft is deleted Passed
page.

Execution type: Manual

Estimated exec. duration
(min):
Priority: Medium
Requirements 03: Gmail draft [Version: 1]
Keywords: None
Execution Details
Build Compose folder- build 1
Tester debdatta
Execution Result: Passed
Execution Mode: Manual
Execution duration (min):

127.0.0.1:81/testlink/index.php 7/9
11/15/21, 8:24 PM testreport Compose folder Testplan

1.4. Test Suite : Sent tab

This test suit contains test cases to acess, archive and delete send mails from inbox.

Test Case GTC-8: Access sent folder [Version : 1]

Author: debdatta
Preconditions:

1. The user must be connected to internet.

2. The user must be logged into their gmail account.

Execution
#: Step actions: Expected Results: Execution notes:
Status:

log into the gmail the user must be directed to the

1 user is directed to homepage Passed
account. homepage

all the emails send by the user

2 click on the sent tab. list of mails send appears. Passed
appears

click on the required the contents of the selected mail

3 the selected mail send opens. Passed
mail. should open.

Execution type: Manual

Estimated exec. duration
(min):
Priority: Medium
Requirements 04: Gmail sent tab [Version: 1]
Keywords: None
Execution Details
Build Compose folder- build 1
Tester debdatta
Execution Result: Passed
Execution Mode: Manual
Execution duration (min):

Test Case GTC-9: Archive sent mail [Version : 1]

Author: debdatta
Preconditions:

The user must be connected to internet

The user must be logged into their gmail account

Execution
#: Step actions: Expected Results: Execution notes:
Status:

A list of emails send all the emails send by the

1 Cick on the 'sent' tab Passed
appears user appears

click on the box along the email to The email should get
2 specific email gets selected Passed
be selected. selected.

3 the selected email is archived Passed

Click on the archive icon The email should get
archived

127.0.0.1:81/testlink/index.php 8/9
11/15/21, 8:24 PM testreport Compose folder Testplan

Execution type: Manual

Estimated exec. duration
(min):
Priority: Medium
Requirements 04: Gmail sent tab [Version: 1]
Keywords: None
Execution Details
Build Compose folder- build 1
Tester debdatta
Execution Result: Passed
Execution Mode: Manual
Execution duration (min):

Test Case GTC-10: delete send mails from folder [Version : 1]

Author: debdatta
Preconditions:

The user must be connected to internet.

The user must be logged into their gmail account.

Execution
#: Step actions: Expected Results: Execution notes:
Status:

List of emails send should all the emails send by the user
1 Click on 'send' tab Passed
appear. appear

Check the box along the The email should get

2 the specific mail is selected Passed
required email selected

The email should get

3 Click on the trash icon the selected email is deleted. Passed
deleted

Execution type: Manual

Estimated exec. duration
(min):
Priority: Medium
Requirements 04: Gmail sent tab [Version: 1]
Keywords: None
Execution Details
Build Compose folder- build 1
Tester debdatta
Execution Result: Passed
Execution Mode: Manual
Execution duration (min):

127.0.0.1:81/testlink/index.php 9/9
Conclusion

 TestLink is a web-based test management system that facilitates software

quality assurance. The platform offers support for test cases, test suites,
test plans, test projects and user management, as well as various reports
and statistics. Here we have tested the performance of Gmail web
application and explained the process in detail.
 Test/Project Report attached.

References
1. https://www.guru99.com/testlink-tutorial-complete-guide.html
2. https://www.softwaretestingclass.com/tutorial-1-getting-started-with-
testlink-test-management-tool/
3. https://www.tutorialspoint.com/testlink/testlink_installation.htm
4. https://testlink.org/
5. https://en.wikipedia.org/wiki/TestLink