Software Testing (FC 5463)

Practical No. 1

Aim: Identify system specification & design test cases for purchase order
management.

Theoretical Background:
Testing is completely guided by software requirement specifications and design
specification and supported by test strategy and test approach depending on
assumptions and risks of development, testing and usages. A purchase order (PO)
is a commercial document and first official offer Issued by a buyer to a seller
indicating types, quantities, and agreed prices for products or services It is used to
control the purchasing of products and services from external suppliers, Since the
retailer and wholesalers will rely heavily on such applications one need to check
and validate purchase order system thoroughly $0 'that any defects that are leftover
can be resolve in given period of time and perfect system can be delivered.

Specifications for Purchase Orders Management:

1. PO Number: This is one of the key elements of a standard purchase order. It
helps to keep Purchase order in a systematic way and track down any order
status efficiently.
2. Business Name: Name of the business and its address
3. Business Logo: Any standard Purchase order would have this option where
business logo could be inserted.
4. Supplier’s details: Business name of the suppliers and its physical address
should be there on a Purchase order to be treated as a valid document.
5. Shipping details: Exact location of the address where products or goods should
be delivered.
6. Product details: All product specification, quantity, preferred price, description
and total value should be added to the Purchase order.
7. The shipping terms: If the buyer wants to give any special instruction to the
supplier then he must include it in the shipping terms segment.

Practical 1
Software Testing (FC 5463)

Test Cases for Purchase Order Management:

Test Rema
N Test Case Expected Actual
Case Prerequisite Steps Input data rks/St
o. Objective Result Result
ID atus

Verify that
the home Application
Opening the The home The home
page is must be Login Id and
1 TC1 application home page is page is Pass
visible after started and password.
page after login. visible. visible.
the login or logged in.
not.

Verify that
the featured
Application Checking the The
products The featured
must be availability of featured
2 TC2 are visible Null products are Pass
started and featured products products are
on available.
logged in. on the homepage. available.
homepage
or not.

Verify that Enter the search Input the The search The search
Application
the search object in search search object field will field
must be
3. TC3 field field. you want to accept the accepted the Pass
started and
accepts search in the alphabets alphabets
logged in.
alphabets Check that the application. and and

Practical 1
Software Testing (FC 5463)

Test Rema
N Test Case Expected Actual
Case Prerequisite Steps Input data rks/St
o. Objective Result Result
ID atus

numbers. search field numbers. numbers.

accepts
alphabets,
numbers.

Verify that Sort the objects

sorting Application using present Select
Objects/pro Objects/prod
option is must be attribute such as: available
4. TC4 ducts must ucts must be Pass
available started and price, date/time, sorting
be sorted. sorted.
and logged in. quality, quantity, options.
working. etc.

Verify that
the user can Select
select the Select desired objects/produ
Application Objects
desired objects/products. cts available Objects are
must be must be
5 TC5 product on homepage added into
started and added into
with Select desired and choose cart.
logged in. cart.
desired output. desired
attributes attributes.
e.g. size,

Practical 1
Software Testing (FC 5463)

Test Rema
N Test Case Expected Actual
Case Prerequisite Steps Input data rks/St
o. Objective Result Result
ID atus

color, etc.

Verify that
Application
there Navigation Navigation
must be
should be buttons/opti buttons/opti
started and Click or enter the Select
navigation ons work ons worked
there should navigation available
6 TC6 buttons/opti properly to properly to Pass
be enough buttons or navigation
ons to navigate navigate
products/obje options. options.
navigate products/ob products/obj
cts to
products or jects/pages. ects/pages.
navigate.
objects.

Resources Require:
Sr. Name of
Specifications Quantity Remarks
No. Resources
Hardware: Computer (i3 or i5), Ram (Minimum 2GB),
1
Computer System HDD (Free Space 1GB)
As per batch For All Practicals of Text
2 Operating System Windows 7 or latest, Linux 5.0 or later. size Case Generation.
3 Software https//: www.testlodge.com/

Practical 1
Software Testing (FC 5463)

Result/Output:
TC1: The home page is visible.

TC2: The featured products are available.

Practical 1
Software Testing (FC 5463)

TC3: The search field accepted the alphabets and numbers.

TC4: Objects/products must be sorted.

Practical 1
Software Testing (FC 5463)

TC5: Objects are added into cart.

Practical 1
Software Testing (FC 5463)

TC6: Navigation buttons/options worked properly to navigate products/objects/pages.

Scroll to navigate

Practical 1
Software Testing (FC 5463)

Exercise:

1. What are the Objectives of software testing?

a) To evaluate the work products such as requirements, design, user stories, and
code.
b) To verify the fulfillment of all specified requirements.
c) To validate if the test object is complete and works as per the expectation of
the users and the stakeholders.
d) To build confidence in the quality level of the test object.
e) To prevent defects in the software product.
f) To find defects in the software product.
g) To provide sufficient information to stakeholders to allow them to make
informed decisions, especially regarding the level of quality of the test object.
h) To reduce the level of risk of insufficient software quality.
i) To comply with contractual, legal, or regulatory requirements or standards,
and to verify the test object’s compliance with such requirements or standards.

2. How can we design test cases from requirements?

a) Use a Strong Title.

b) Include a Strong D1escription.
c) Include Assumptions and Preconditions.
d) Keep the Test Steps Clear and Concise.
e) Include the Expected result.
f) Make it Reusable.
g) Title: Login Page - Authenticate Successfully on gmail.com.
h) Description: A registered user should be able to successfully login at
gmail.com.

Practical 1
Software Testing (FC 5463)

3. Compare Static and Dynamic testing.

Static Testing Dynamic Testing

1. Testing was done without executing 1. Testing is done by executing the
the program program
2. This testing does the verification 2. Dynamic testing does the validation
process process
3. Static testing is about prevention of 3. Dynamic testing is about finding and
defects fixing the defects
4. Static testing gives an assessment of 4. Dynamic testing gives
code and documentation bugs/bottlenecks in the software
system.
5. Static testing involves a checklist and 5. Dynamic testing involves test cases
process to be followed for execution
6. This testing can be performed before 6. Dynamic testing is performed after
compilation compilation
7. Static testing covers the structural 7. Dynamic testing techniques are
and statement coverage testing Boundary Value Analysis &
Equivalence Partitioning.

Conclusion: Identify system specification & design test cases for purchase order
management.

Practical 1