Software Testing Practical

B.TECH

IN

COMPUTER SCIENCE AND INFORMATION TECHNOLOGY

BY

SHUBHAM LAKHMANI
(ID. No : 20BTCSE020)

UNDER THE SUPERVISION OF

Dr. Shashi Prabha

DEPARTMENT OF COMPUTER SCIENCE AND IT

VAUGH INSTITUTE OF AGRICULTURAL ENGINEERING AND
TECHNOLOGY

SAM HIGGINBOTTOM UNIVERSITY OF AGRICULTURE,

TECHNOLOGY AND SCIENCES
NAINI, PRAYAGRAJ-211007
 Contents

Experiment No. Title Page No.

1 Write programs in C language in demonstration of the working of the
following constructs (i). do..while (ii) while..do (iii) if…else (iv) switch
(v) for

2 Write the test cases for FACEBOOK, TWITTER etc.

3 Take any system (e.g. ATM system) and study its system
specifications and report the various bugs.

4 Write the test cases for GMAIL.

5 Create a test plan document for any application (e.g. Library

Management System)

6 Study of any testing tool (e.g. Win runner)

7 Study of any web testing tool (e.g. Selenium)

8 Study of any bug tracking tool (e.g. Bugzilla, bugbit)

9 Study of any test management tool (e.g. Test Director)

10 Study of any open source-testing tool (e.g. Test Link)

1. Write a programs in C language in demonstration the working of the following constructs

(i). do..while (ii) while..do (iii) if…else (iv) switch (v) for

(i) do..while

include <stdio.h>

int main() {

int count = 1;

// do..while loop

do {

printf("Count: %d\n", count);

count++;

} while (count <= 5);

return 0;

(ii) while..do

include <stdio.h>

int main() {

int count = 1;

// while..do loop

while (count <= 5) {

printf("Count: %d\n", count);

 count++;

return 0;

(iii) if…else

include <stdio.h>

int main() {

int number = 10;

// if…else construct

if (number % 2 == 0) {

printf("%d is even.\n", number);

} else {

printf("%d is odd.\n", number);

return 0;

(iv) switch

include <stdio.h>

int main() {
 int day = 3;

switch (day) {

case 1:

printf("Monday\n");

break;

case 2:

printf("Tuesday\n");

break;

case 3:

printf("Wednesday\n");

break;

case 4:

printf("Thursday\n");

break;

case 5:

printf("Friday\n");

break;

case 6:

printf("Saturday\n");

break;

case 7:

printf("Sunday\n");

break;

default:

printf("Invalid day\n");

return 0;

}
(v) for

include <stdio.h>

int main() {

int i;

// for loop

for (i = 1; i <= 5; i++) {

printf("Iteration: %d\n", i);

return 0;

}
2. Write the test cases for FACEBOOK, TWITTER etc.

Testing social media platforms like Facebook and Twitter involves a comprehensive approach

covering various functionalities. Below are some general test cases that can be applied to

such platforms. These test cases are divided into categories for better organization:

User Registration and Login

Facebook

1. Test Case ID: FB_REG_001

- Description: Verify that a user can successfully register with valid details.

- Steps:

1. Go to the Facebook registration page.

2. Enter valid name, email, password, birth date, and gender.

3. Click on the "Sign Up" button.

- Expected Result: User receives a verification email and can complete registration.

2. Test Case ID: FB_LOGIN_001

- Description: Verify that a user can log in with valid credentials.

- Steps:

1. Go to the Facebook login page.

2. Enter registered email and password.

3. Click on the "Log In" button.

- Expected Result: User is successfully logged in and redirected to their homepage.

Twitter

1. Test Case ID: TW_REG_001

- Description: Verify that a user can successfully register with valid details.

- Steps:
 1. Go to the Twitter registration page.

2. Enter valid name, phone number/email, and password.

3. Click on the "Sign Up" button.

- Expected Result: User receives a verification email/SMS and can complete registration.

2. Test Case ID: TW_LOGIN_001

- Description: Verify that a user can log in with valid credentials.

- Steps:

1. Go to the Twitter login page.

2. Enter registered email/phone number and password.

3. Click on the "Log In" button.

- Expected Result: User is successfully logged in and redirected to their homepage.

Profile Management

Facebook

1. Test Case ID: FB_PROFILE_001

- Description: Verify that a user can update their profile information.

- Steps:

1. Log in to Facebook.

2. Navigate to the profile page.

3. Click on the "Edit Profile" button.

4. Update information like bio, work, education, etc.

5. Save changes.

- Expected Result: Profile information is updated and displayed correctly.

2. Test Case ID: FB_PROFILE_PIC_001

- Description: Verify that a user can upload and change their profile picture.

- Steps:

1. Log in to Facebook.
 2. Navigate to the profile page.

3. Click on the profile picture area.

4. Upload a new picture and save.

- Expected Result: Profile picture is updated and displayed correctly.

Twitter

1. Test Case ID: TW_PROFILE_001

- Description: Verify that a user can update their profile information.

- Steps:

1. Log in to Twitter.

2. Navigate to the profile page.

3. Click on the "Edit Profile" button.

4. Update information like bio, location, website, etc.

5. Save changes.

- Expected Result: Profile information is updated and displayed correctly.

2. Test Case ID: TW_PROFILE_PIC_001

- Description: Verify that a user can upload and change their profile picture.

- Steps:

1. Log in to Twitter.

2. Navigate to the profile page.

3. Click on the profile picture area.

4. Upload a new picture and save.

- Expected Result: Profile picture is updated and displayed correctly.

Posting and Interactions

Facebook

1. Test Case ID: FB_POST_001

- Description: Verify that a user can create a new post.

 - Steps:

1. Log in to Facebook.

2. Go to the homepage.

3. Click on the "What's on your mind?" text box.

4. Enter a message and click on the "Post" button.

- Expected Result: Post is created and displayed on the timeline.

2. Test Case ID: FB_COMMENT_001

- Description: Verify that a user can comment on a post.

- Steps:

1. Log in to Facebook.

2. Find a post on the timeline.

3. Click on the "Comment" button.

4. Enter a comment and submit.

- Expected Result: Comment is added to the post.

3. Test Case ID: FB_LIKE_001

- Description: Verify that a user can like a post.

- Steps:

1. Log in to Facebook.

2. Find a post on the timeline.

3. Click on the "Like" button.

- Expected Result: Post is liked and the like count increases.

Twitter

1. Test Case ID: TW_TWEET_001

- Description: Verify that a user can create a new tweet.

- Steps:

1. Log in to Twitter.

2. Click on the "Tweet" button.

 3. Enter a message and click on the "Tweet" button.

- Expected Result: Tweet is created and displayed on the timeline.

2. Test Case ID: TW_REPLY_001

- Description: Verify that a user can reply to a tweet.

- Steps:

1. Log in to Twitter.

2. Find a tweet on the timeline.

3. Click on the "Reply" button.

4. Enter a reply message and submit.

- Expected Result: Reply is added to the tweet.

3. Test Case ID: TW_LIKE_001

- Description: Verify that a user can like a tweet.

- Steps:

1. Log in to Twitter.

2. Find a tweet on the timeline.

3. Click on the "Like" button.

- Expected Result: Tweet is liked and the like count increases.

Notifications

Facebook

1. Test Case ID: FB_NOTIFY_001

- Description: Verify that a user receives a notification when someone likes their post.

- Steps:

1. Log in to Facebook.

2. Create a post.

3. Have another user like the post.

- Expected Result: Notification is received for the like.

Twitter

1. Test Case ID: TW_NOTIFY_001

- Description: Verify that a user receives a notification when someone likes their tweet.

- Steps:

1. Log in to Twitter.

2. Create a tweet.

3. Have another user like the tweet.

- Expected Result: Notification is received for the like.

Direct Messaging

Facebook

1. Test Case ID: FB_DM_001

- Description: Verify that a user can send a direct message to another user.

- Steps:

1. Log in to Facebook.

2. Go to the Messages section.

3. Select a contact and send a message.

- Expected Result: Message is sent and appears in the conversation.

Twitter

1. Test Case ID: TW_DM_001

- Description: Verify that a user can send a direct message to another user.

- Steps:

1. Log in to Twitter.

2. Go to the Messages section.

3. Select a contact and send a message.

- Expected Result: Message is sent and appears in the conversation.

These test cases cover a broad spectrum of functionalities typical of social media platforms

like Facebook and Twitter. Each test case includes a unique ID, a description, steps to

execute the test, and the expected result. This structured approach ensures comprehensive

testing and helps identify any issues within the platform.

3. System Specifications and Bug Report for an ATM System

System Specifications:

1. User Authentication:

- Card insertion and PIN entry.

2. Balance Inquiry:

- Display current balance.

3. Cash Withdrawal:

- Allow withdrawal up to available balance and daily limit.

4. Deposit:

- Accept cash or checks and update balance.

5. Mini Statement:

- Print or display recent transactions.

6. Fund Transfer:

- Transfer funds between accounts.

7. Account Services:

- Change PIN, request checkbook, etc.

Bug Report:

1. Bug ID: ATM_001

- Description: System crashes after entering the correct PIN.

- Steps to Reproduce:

1. Insert card.

2. Enter correct PIN.

- Expected Result: User should be logged in and directed to the main menu.

- Actual Result: System crashes.

2. Bug ID: ATM_002

- Description: Incorrect balance shown after cash withdrawal.

 - Steps to Reproduce:

1. Insert card and enter PIN.

2. Withdraw cash.

3. Check balance.

- Expected Result: Balance should be reduced by the withdrawal amount.

- Actual Result: Balance remains unchanged.

3. Bug ID: ATM_003

- Description: Unable to change PIN.

- Steps to Reproduce:

1. Insert card and enter PIN.

2. Go to Account Services.

3. Attempt to change PIN.

- Expected Result: PIN should be updated.

- Actual Result: Error message displayed, PIN remains unchanged.

4. Test Cases for GMAIL

1. Test Case ID: GM_REG_001

- Description: Verify that a user can register with valid details.

- Steps:

1. Go to Gmail registration page.

2. Enter valid name, email, password, and other details.

3. Click on the "Next" button.

- Expected Result: User should receive a verification email and complete registration.

2. Test Case ID: GM_LOGIN_001

- Description: Verify that a user can log in with valid credentials.

- Steps:

1. Go to Gmail login page.

2. Enter registered email and password.

3. Click on the "Next" button.

- Expected Result: User should be logged in and redirected to their inbox.

3. Test Case ID: GM_SEND_001

- Description: Verify that a user can send an email.

- Steps:

1. Log in to Gmail.

2. Click on "Compose" button.

3. Enter recipient's email, subject, and body.

4. Click on "Send" button.

- Expected Result: Email should be sent and appear in the Sent folder.

4. Test Case ID: GM_RECV_001

- Description: Verify that a user can receive an email.

 - Steps:

1. Log in to Gmail.

2. Send an email to the logged-in email address from another account.

- Expected Result: Email should appear in the inbox.

5. Test Case ID: GM_DEL_001

- Description: Verify that a user can delete an email.

- Steps:

1. Log in to Gmail.

2. Select an email from the inbox.

3. Click on the "Delete" button.

- Expected Result: Email should be moved to the Trash folder.

5. Test Plan Document for Library Management System

Test Plan Document

1. Introduction

- 1.1 Purpose: To define the test strategy, objectives, schedule, and resources required to

test the Library Management System (LMS).

- 1.2 Scope: Covers functionality, performance, security, and usability testing of LMS.

2. Test Objectives

- Verify that all functionalities work as expected.

- Ensure system performance under load.

- Validate data security and user access controls.

- Assess system usability and user interface.

3. Test Scope

- In Scope: User registration, book search, borrowing/returning books, fine calculation, user

management, and report generation.

- Out of Scope: Hardware-related issues, third-party integrations not controlled by LMS.

4. Test Strategy

- 4.1 Testing Types: Functional, Integration, System, Regression, Performance, Security,

and Usability testing.

- 4.2 Testing Levels: Unit Testing, Integration Testing, System Testing, User Acceptance

Testing (UAT).

5. Test Environment

- 5.1 Hardware: Servers, client machines, network infrastructure.

- 5.2 Software: Operating System, Database, Web Server, Browsers.

- 5.3 Test Data: Sample data for books, users, transactions.

6. Test Schedule

- 6.1 Milestones:

- Test Planning: [Start Date] to [End Date]

- Test Case Development: [Start Date] to [End Date]

- Test Execution: [Start Date] to [End Date]

- Test Closure: [Start Date] to [End Date]

7. Resources

- 7.1 Personnel: Test Manager, Test Leads, Testers, Developers, Database Administrators.

- 7.2 Tools: Test management tool, automation tools, performance testing tools.

8. Risk Management

- 8.1 Risks: Delay in development, insufficient test data, environmental issues.

- 8.2 Mitigation: Regular progress reviews, backup test data, maintaining a stable test

environment.

9. Deliverables

- Test Plan, Test Cases, Test Scripts, Test Reports, Defect Reports, Test Summary Report.

10. Approval

- Sign-off from stakeholders including Project Manager, Development Lead, QA Lead.

6. Study of WinRunner Testing Tool

WinRunner is an automated functional GUI testing tool that was developed by Mercury

Interactive (now part of Micro Focus). Here’s a brief study:

Key Features:

- Record and Playback: Records user actions on the application and plays them back during

test execution.

- Test Script Language (TSL): A C-like scripting language to customize test scripts.

- Synchronization: Handles timing issues with synchronization points.

- Checkpoints: Validates the properties of GUI objects and application behavior.

- Data-Driven Testing: Executes the same test with multiple sets of data.

- Integration: Works well with TestDirector (now Quality Center) for test management.
7. Study of Selenium Web Testing Tool

Selenium is an open-source tool for automating web browsers. Here’s a brief study:

Key Features:

- Supports Multiple Browsers: Firefox, Chrome, Safari, Internet Explorer, etc.

- Cross-Platform: Runs on Windows, macOS, and Linux.

- Language Support: Allows writing test scripts in various languages like Java, C, Python,

Ruby, JavaScript, and Kotlin.

- Selenium WebDriver: A programming interface to create and execute test cases.

- Selenium IDE: A Chrome and Firefox plugin for recording and playback of tests.

- Selenium Grid: Allows running tests on different machines and browsers simultaneously.
8. Study of Bugzilla Bug Tracking Tool

Bugzilla is an open-source bug tracking system developed by Mozilla. Here’s a brief study:

Key Features:

- Bug Tracking: Tracks and manages bugs and issues.

- Email Notifications: Sends updates to stakeholders via email.

- Customizable Workflow: Adapts to various workflows and project needs.

- Reports and Charts: Generates detailed bug reports and visual charts.

- Access Control: Provides fine-grained control over who can view and modify bugs.

- Search and Filter: Powerful search and filtering capabilities for bugs.
9. Study of Test Director (now HP ALM/Quality Center)

Test Director, now known as HP ALM (Application Lifecycle Management), is a test

management tool. Here’s a brief study:

Key Features:

- Requirements Management: Tracks and manages project requirements.

- Test Plan: Develops and manages test plans and cases.

- Test Lab: Executes tests and tracks execution status.

- Defects Management: Captures, tracks, and manages defects.

- Dashboard: Provides real-time data and analytics through reports and graphs.

- Integration: Integrates with various development and testing tools.

10. Study of TestLink Open Source Testing Tool

TestLink is an open-source test management tool. Here’s a brief study:

Key Features:

- Test Case Management: Creates, manages, and organizes test cases.

- Test Plans: Develops test plans and assigns test cases to testers.

- Execution: Executes test cases and records results.

- Reporting: Generates detailed reports on test execution and metrics.

- Requirements Management: Links test cases to requirements.

- Integration: Integrates with various bug tracking tools like Bugzilla, JIRA, and others.

Each of these tools plays