1.

a
#include <stdio.h> int
main() {
int i;
printf("Even numbers from 1 to 10 are:\n");
for (i = 1; i <= 10; i++) { if (i % 2 == 0)
{ printf("%d ", i);
}
}
return 0;
}

Test Cases :

Test Objective Input Data Expected Result Actual Result Status

Case No.

TC1 Check even Numbers 1 to 10 2, 4, 6, 8, 10 2, 4, 6, 8, 10 Pass

numbers from 1 to
10

TC2 Check for no input No input Program runs Program runs Pass
successfully successfully
without
specifying the
numbers

TC3 Check for negative Numbers -10 to -1 No output No output has been Pass
numbers should be displayed
displayed

Test Objective Input Data Expected Result Actual Result Status

Case No.

TC04 Checking with Characters (A-Z) Error or invalid Error Pass

characters input

TC05 Check behavior with Numbers 1 to 2, 4, 6, 8, 10 2, 4, 6, 8, 10 Pass

large integers 1000000 (partial)

1.b
Test Cases for Login Form

Test Objective Input Data Expected Result Actual Status

Case No. Result

TC1 Login with valid Username: user1, Login successful Login Pass
credentials Password: pass123 successful

TC2 Leave both fields Username: (empty), Error: "Fields Error Pass
empty Password: (empty) required"

TC3 Leave password Username: user1, Error: "Password Error Pass

empty Password: (empty) required"

TC4 Use special Username: user1, Error: "Invalid Error Pass

characters Password: %pass# input"

2.

Online Mobile Recharge Form

Test Objective Input Data Expected Result Actual Status

Case Result
No.

TC1 All valid inputs Enter the details : Recharge Recharge Pass
Mobile: 9876543210, successful successful
State: MH,
Email
ritisha.bale@gmail.com ,
Amount: 200
TC2 Invalid mobile number Mobile: 123, Error: "Invalid Error Pass
State: MH, mobile number"
Email:
ritisha.bale@gmail.com ,
Amount: 200

TC3 Invalid email Mobile: 9876543210, Error: "Invalid Error Pass

State: MH, email"
Email: test.gmail.com,
Amount: 200

TC4 Leave recharge amount Mobile: 9876543210, Error: "Amount Error Pass
blank State: MH, required"
Email:
ritisha.bale@gmail.com,
Amount: (empty)

Test Objective Input Data Expected Result Actual Status

Case Result
No.

TC5 Invalid recharge Mobile: 9876543210, Error: "Invalid Error Pass

amount State: MH, amount"
Email:
ritisha.bale@gmail.com,
Amount: -200

TC6 Leave all fields blank Mobile: (empty), Error: "Fields Error Pass
State: (empty), required"
Email: (empty),
Amount: (empty)
TC7 Invalid state code Mobile: 9876543210, Error: "Invalid Error Pass
State: XYZ, state code"
Email:
ritisha.bale@gmail.com,
Amount: 200

TC8 Valid inputs with Mobile: 9876543210, Recharge Recharge Pass

minimum recharge State: MH, Email: successful successful
amount ritisha.bale@gmail.com
, Amount: 20

TC9 Valid inputs with Mobile: 9876543210, Recharge Recharge Pass

maximum recharge State: MH, successful successful
amount Email:
ritisha.bale@gmail.com
Amount: 3000

Test Objective Input Data Expected Result Actual Status

Case Result
No.

TC10 Mobile number with Mobile: 98765ABCD1, Error: "Invalid Error Pass
invalid characters State: MH, mobile number"
Email:
ritisha.bale@gmail.com,
Amount: 200

TC11 Valid inputs without Mobile: 9876543210, Error: "Email Error Pass
email required"
State: MH, Email: (empty),
Amount: 200
TC12 Attempt to recharge Mobile: 9999999999, Error: "Mobile Error Pass
for unregistered State: MH, number not
number Email: registered"
ritisha.bale@gmail.com,
Amount: 200

3.
Test Cases for Hostel Admission Form
Test Objective Input Data Expected Result Actual Status
Case Result
No.

TC1 All valid inputs Name: Ritisha bale Admission form Submitted Pass
Age: 18, submitted successfully
successfully
Gender: Female ,
Address: ABC Street,

Test Input Data

Case Expected Result Actual Status
Objective Result
No.

State: MH,
Email:ritisha.bale@gmail.com,

TC2 Invalid email Name: Ritisha , Age: 18, Error: "Invalid Error Pass
format Gender: Female, Address: ABC email"
Street, State: MH, Email:
test.gmail.com
TC3 Missing Name: (empty), Age: 18, Error: "Name is Error Pass
mandatory field Gender: Female, Address: ABC required"
(Name ) Street, State: MH, Email:
ritisha.bale@gmail.com

TC4 Missing Name: Ritisha , Age: (empty), Error: minimum Error Pass
mandatory field Gender: Female, Address: ABC "Age is
(Age) Street, State: MH, Email: required"
ritisha.bale@gmail.com

TC5 Invalid age (below Name: Ritisha , Age: 10, Error: "Age must Error Pass
minimum) Gender: Female, Address: ABC be at least 16"
Street, State: MH, Email:
ritisha.bale@gmail.com

TC6 Invalid age (above Name: Ritisha , Age:75, Error: "Age must Error Pass
maximum) Gender: Female, Address: ABC not exceed 25"
Street, State: MH, Email:
ritisha.bale@gmail.com

TC7 Invalid gender Name: Ritisha , Age: 18, Error: "Invalid Error Pass
input Gender: ABC, Address: ABC gender selection"
Street, State: MH, Email:
ritisha.bale@gmail.com

TC8 Leave all fields Name: (empty), Age: (empty), Error: "All fields Error Pass
blank Gender: (empty), Address: are required"
(empty), State: (empty),
Email: (empty)

Test Objective Input Data Expected Result Actual Statu

Case Result s
No.

TC9 Address field Name: Ritisha , Age: 18, Gender: Error: "Address Error Pass
exceeding Female, Address: (500 is too long"
character characters), State: MH, Email:
limit ritisha.bale@gmail.com

TC10 Valid inputs with Name: Ritisha , Age: 18, Gender: Admission form Submitted Pass
state dropdown Female, Address: ABC Street, submitted successfully
selection State: Selected, Email: successfully
ritisha.bale@gmail.com
 TC11 Special characters Name: ritu@123%, Age: 18, Error: "Name Error Pass
in name Gender: Female, Address: ABC contains invalid
Street, State: MH, Email: characters"
ritisha.bale@gmail.com

TC12 Valid inputs with Name: Ritisha , Age: 18, Gender: Admission form Submitted Pass
alternate address Female, Address: submitted successfully
format House No. 12, State: MH, successfully
Email: ritisha.bale@gmail.com

4. Railway reservation system :

5.
Test Cases for GUI Testing of Amazon Login Form

Test Objective Input Data Expected Actual Status

Case Result Result
No.

TC1 Login with valid Username: Login Login Pass

email and password ritisha.bale@gmail.com, Password: successful successful
Pass@123
TC2 Login with invalid Username: test.gmail.com, Error: "Invalid Error Pass
email Password: Pass@123 email format"

TC3 Login with valid Username: 9876543210, Password: Login Login Pass
phone and Pass@123 successful successful
password

TC4 Login with invalid Username: 123, Password: Error: "Invalid Error Pass
phone number Pass@123 phone number"

TC5 Login with empty Username: (empty), Password: Error: Error Pass
username Pass@123 "Username
required"

TC6 Login with empty Username: Error: Error Pass

password ritisha.bale@gmail.com, Password: "Password
(empty) required"

TC7 Attempt login with Username: Error: "Account Error Pass

unregistered unregistered@gmail.com, not found"
account Password: Pass@123

TC8 Login with Username: Error: "Invalid Error Pass

password ritisha.bale@gmail.com, Password: password"
containing spaces "Pass @123"

TC9 Login with special Username: Login Login Pass

characters ritisha.bale@gmail.com, Password: successful successful
P@$$123!

TC10 SQL injection in Username: admin';--, Password: Error: "Invalid Error Pass
username pass123 input"

TC11 Password length Username: Error: Error Pass

less than 8 ritisha.bale@gmail.com, Password: "Password too
characters Pass short"

Test Objective Input Data Expected Actual Status

Case Result Result
No.

TC12 Login with Username: Login Login Pass

numeric-only ritisha.bale@gmail.com, Password: successful successful
password 12345678
6.
Test Cases for Creating a Savings Account at Bank
Fields: Name, Age, Mobile Number, Email, Initial Deposit
Test Objective Input Data Expected Actual Statu
Cas Result Result s
e
No.

TC1 Successful Name: Ritisha , Age: 18, Mobile: 9876543210, Account Accoun Pass
account Email: ritisha.bale@gmail.com, Deposit: 5000 created t
creation successfull created
y

TC2 Invalid Mobile: 123456 Error: Error Pass

mobile "Invalid
number mobile
number"

TC3 Age less than Name: Ritisha, Age: 15, Mobile: 9876543210, Email: Error: "Age Error Pass
required ritisha.bale@gmail.com, Deposit: 5000 must be 18
(below 18) or older"

TC4 Invalid email Email: test.gmail.com Error: Error Pass

format "Invalid
email"

TC5 Initial Deposit: 4999 Error: Error Pass

deposit below "Minimum
minimum deposit is
limit 5000"

Test Objective Input Data Expected Actual Statu

Cas Result Result s
e
No.

TC6 Missing name Name: (empty), Age: 18 Error: Error Pass

, Mobile: 9876543210, Email: "Name
ritisha.bale@gmail.com, Deposit: 5000 required"
TC7 Invalid Name: r1tish@ Error: Error Pass
characters in "Invalid
name characters in
name"

TC8 Missing Deposit: (empty) Error: Error Pass

deposit "Deposit
amount required"

TC9 Valid inputs Name:ritisha, Age: 65, Mobile: 9876543210, Email: Account Accoun Pass
for senior ritisha.bale@gmail.com, Deposit: 5000 created t
citizen (age successfull created
60) y

TC1 Missing Mobile: (empty) Error: Error Pass

0 mobile "Mobile
number number
required"

TC1 Name with Name: Error: Error Pass

1 long length ritishabaleWithVeryLongNameExceedingFiftyCha "Name too
(>50 racters long"
characters)

TC1 Valid inputs Deposit: 1000000 Account Accoun Pass

2 with created t
maximum successfull created
deposit y
amount

7. MS word

Test Objective Input Data Expected Result Actual Status

Case Result
No.

TC001 Verify saving a new New file, text added, Document is saved successfully As Pass
document save button clicked in the specified location expected
TC002 Verify overwriting Existing file, text Existing file is updated with new As Pass
an existing modified, save button content expected
document clicked

TC003 Verify "Save As" Existing file, "Save Document is saved as a PDF file As Pass
functionality for As" selected, PDF in the specified location expected
PDF format format chosen

TC004 Verify auto-save Open file, make changes, Changes are saved As Pass
functionality wait for autosave automatically at defined expected
intervals

TC005 Verify saving a New file, text added, Document is saved with As Pass
document with a password set during password protection expected
password save

TC006 Verify saving with an New file, invalid file Error message displayed As Pass
invalid file name name (e.g., special indicating invalid file name expected
characters)

TC007 Verify saving to a New file, directory Error message displayed As Pass
non-existent directory path does not exist indicating invalid directory expected
path

TC008 Verify saving a Open file, no changes No changes are saved; file As Pass
document without made, save button remains the same expected
changes clicked

TC009 Verify saving a very New file, large File is saved successfully As Pass
large file content (e.g., >1GB), without performance issues expected
save button clicked

TC010 Verify save New file, text added, Error message displayed As Pass
functionality when disk space insufficient indicating insufficient disk expected
disk is full space

TC011 Verify "Save As" Existing file, "Save As" Document is saved in the As Pass
functionality for selected, different specified format expected
different formats formats chosen (e.g.,
.txt, .docx)
TC012 Verify saving a New file, select save Document is saved As Pass
document in location as successfully to the cloud expected
OneDrive/Cloud OneDrive/Cloud location

8
.test Cases for ATM Withdrawal Functionality
Test Objective Input Data Expected Result Actual Result Status
Case
No.

TC001 Verify successful Valid card, valid Cash is dispensed, Pass

cash withdrawal PIN, valid amount receipt is printed, As expected
balance updated Cash is dispensed,
receipt is printed,
balance updated

TC002 Verify insufficient Valid card, valid "Insufficient funds" As expected Pass
funds error PIN, amount > message is displayed “Insufficient funds"
balance message is displayed

TC003 Verify error for Valid card, invalid "Invalid PIN" error As expected Pass
invalid PIN PIN message is displayed Invalid PIN" error
message is displayed
9.

TEST PLAN

Sr. no. Test plan Identifier TP_01

1 Introduction The purpose of this document is to create a

test plan for the message delivery, edit,
attachment, and reaction features of a
messaging application.
The purpose of testing is to ensure the
correct operation, usability, and
functionality of these features.

2 Test Items - Message delivery

- Editing messages
- Sending attachments
- Reacting to messages

3 Features to be Tested -Message delivery functionality

-Message editing capabilities

-Sending various types of attachments
-Adding reactions to messages

4 Approach - Functional testing: Focus on the

correct functioning of each feature.
- Positive and negative testing:
Verify normal and adverse conditions. -
Ad-hoc testing

5 Item Pass/Fail Criteria - All high-priority test cases must

pass. - Test coverage should be at least
99% of requirements.
- Test report must be approved by
the team lead.
6 Suspension Criteria & Resumption - Suspend testing if blocking bugs are
Criteria found.
- Resume testing once blocking bugs
are resolved in the bug-tracking system.

7 Test Deliverables - Test plan

- Test case specification
- Test cases
- Test summary report

8 Test Tasks - Writing the test plan

- Writing test cases
- Developing success criteria for testing
- Conducting tests
- Creating and reviewing test reports

9 Environmental Needs - Messaging application

- Computer or mobile device
- Internet connectivity

10 Responsibilities Functionality and Responsible

Responsibilities

Message delivery Test Engineer 1

Editing messages Test Engineer 1

Sending attachments Test Engineer 1

Reacting to Test Engineer 2

messages
 11 Staffing and Training Needs To perform the tasks, you need to have the
following knowledge and skills:

• knowledge of practical application

of the notepad.
• knowledge and ability to apply in
practice the basic techniques of test
design.
• Knowledge of various types of
testing including functional and
non-functional.

12 Schedule The deadline for completion of all works

and delivery of the project is 06/12/2023 by
5.00pm

13 Risks and Contingencies Insufficient human resources for testing the

application in deadlines.
Changing the requirements for the product

14 Approvals Lead
Test engineer 1
Test engineer 2
Test engineer 3
Test engineer 4

10.
TEST PLAN save
functionality of Ms word

Sr. no. Test plan Identifier TP_01

1 Introduction The purpose of this document is to create a
test plan for Save functionality of
Microsoft Word. The testing will ensure
that the feature operates correctly under all
conditions, is userfriendly, and meets
functionality requirements
The purpose of testing is to ensure the
correct operation, usability, and
functionality of these features.

2 Test Items Save file with a new name.

Save file with an existing name .
Save file in different formats
Save file on different storage locations

3 Features to be Tested -Save As functionality

-Overwrite Save functionality
Save file in different format functionality
Save location options

4 Approach - Functional testing: Focus on the

correct functioning of each feature.
- Positive and negative testing:
Verify normal and adverse conditions. -
Ad-hoc testing

5 Item Pass/Fail Criteria - All high-priority test cases must

pass.
- Test coverage should be at least
99% of requirements.
- Test report must be approved by
the team lead.

6 Suspension Criteria & Resumption - Suspend testing if blocking bugs are

Criteria found.
- Resume testing once blocking bugs
are resolved in the bug-tracking system.
7 Test Deliverables - Test plan
- Test case specification
- Test cases
- Test summary report

8 Test Tasks - Writing the test plan

- Writing test cases
- Developing success criteria for testing
- Conducting tests
- Creating and reviewing test reports

9 Environmental Needs Microsoft Word application.

Desktop or laptop computer.
Network connectivity for cloud saves.

10 Responsibilities Functionality and Responsible

Responsibilities

Save as new file Test Engineer 1

Save with overwrite Test Engineer 1

Save in multiple Test Engineer 1

formats

Save in different Test Engineer 2

storage locations

11 Staffing and Training Needs To perform the tasks, you need to have the
following knowledge and skills:

• knowledge of practical application

of the MS Word.
• knowledge and ability to apply in
practice the basic techniques of test
design.

• Knowledge of various types of

testing including functional and
non-functional.

12 Schedule The deadline for completion of all works

and delivery of the project is 06/12/2024 by
5.00pm
13 Risks and Contingencies Insufficient human resources for testing the
application in deadlines.
Changing the requirements for the product

14 Approvals Lead
Test engineer 1
Test engineer 2
Test engineer 3
Test engineer 4