Test Case Requirement/Section Test Type Test Level Actor Test Objective Precondit
No ID ions
2 Report Requirenments
2.1 Report Access
1 2.1 Report Access Functional P1 Client Verify the users with the
report access
2.2 General Report Specifications
2 2.2.2 Currency and Functional P1 Client Verify all currency data in
lookup data reports
3 2.2.3 Fiscal Vs Functional P1 Client Verify Store budget
Calender month report
grouping
4 2.2.3 Fiscal Vs Functional P1 Client Verify monthly
Calender month aggregations reports
grouping
5 2.2.4 Changes orders Functional P1 Client Verify change orders
reports
6 2.2.5 Parameter Functional P1 Client Verify Parameter sheet
sheets style
7 2.2.6 Report Layout Functional P1 Client Verify Report header
layout
8 2.2.6 Report Layout Functional P1 Client Verify Report Footer
layout
9 2.2.7 Report Paging Functional P1 Client Verify Report page
10 2.2.7 Report Paging Functional P1 Client Verify Report format
11 2.2.8 Bealls ORG IDs Functional P1 Client Verify bealls Parent Org
ID
12 2.2.8 Bealls ORG IDs Functional P1 Client Verify bealls sub Org IDs
Verify that user is able to
generate report for all
the above org and sub-
orgs
2.3 Store Budget Report
13 2.3.2 Report Functional P1 Client Verify report Paremeter
Parameters sheet
14 2.3.2 Report Functional P1 Client Verify the submit button
Parameters
15 2.3.2 Report Functional P1 Client Verify if no data found in
Parameters Fiscal calender table
16 2.3.2 Report Functional P1 Client Verify the value in
Parameters parameter sheet report
17 2.3.3 Scope of data Functional P1 Client Verify cardinality for
and cardinality report
18 2.3.3 Scope of data Functional P1 Client Verify the store location
and cardinality scope for report
19 2.3.3 Scope of data Functional P1 Client
and cardinality
20 2.3.3 Scope of data Functional P1 Client Verify Store numbers in
and cardinality Budget report order
21 2.3.4 Report Header Functional P1 Client Verify report Sort Order
specification
22 2.3.4 Report Header Functional P1 Client Verify report title
specification
23 2.3.4 Report Header Functional P1 Client Verify Parameter label in
specification budget report sheet
24 2.3.5 Report Table Functional P1 Client Verify the values of fiscal
specification year
25 2.3.5 Report Table Functional P1 Client Verify the Period Start
specification Date and Period End Date
26 2.3.5 Report Table Functional P1 Client Verify the Report Table
specification Specification Columns
2.5 Order Summary by Month Repo
27 2.5.2 Report Functional P1 Client Verify the report
Paremeters parameter sheet
28 2.5.2 Report Functional P1 Client Verify Organization
Paremeters Paremeter in Monthly
report sheet
29 2.5.2 Report Functional P1 Client Verify Beginning Order
Paremeters date Paremeter in
Monthly report sheet
30 2.5.2 Report Functional P1 Client Verify Ending Order date
Paremeters Paremeter in Monthly
report sheet
31 2.5.3 Scope of data Functional P1 Client Verify monthly report
and Cardinality sheet cardinality
32 2.5.3 Scope of data Functional P1 Client Verify The mothly report
and Cardinality sheet po statuses
33 2.5.3 Scope of data Functional P1 Client Verify Report sort Order
and Cardinality
34 2.5.4 Report Header Functional P1 Client Verify Report title name
Specification
35 2.5.4 Report Header Functional P1 Client Verify Paremeter sheet
Specification Values
36 2.5.5 Report Table Functional P1 Client Verify Report Columns
Specification
2.6 PO (Purchase Order) Aging Repo
37 2.6.2 Enhancement Functional P1 Client Verify New Column
Specification 'Release Date' added to
existing Po Aging report
2.7 Item Status report
38 2.7.2 Report Functional P1 Client Verify the report
Parameters Selection criteria
39 2.7.2 Report Functional P1 Client Verify Organization select
Parameters List
40 2.7.3 Scope of Date Functional P1 Client Verify Item Status report
and Cardinality Cardinality
41 2.7.3 Scope of Date Functional P1 Client Verify Date Selection
and Cardinality logic
42 2.7.3 Scope of Date Functional P1 Client Verify report sort Order
and Cardinality
43 2.7.4 Report Header Functional P1 Client Verify report Title
Specification
44 2.7.4 Report Header Functional P1 Client Verify parameter Sheet
Specification value
45 2.7.5 Report Table Functional P1 Client Verify Report Columns in
Specification Item status Report sheet
2.8 Supplier Order Item History Repo
46 2.8.3 Report Functional P1 Client Verify the report
Parameters Parameters
47 2.8.3 Report Functional P1 Client Verify Organization select
Parameters List
48 2.8.3 Report Functional P1 Client Verify Month select List
Parameters
49 2.8.4 Scope of Date Functional P1 Client Verify Order item History
and Cardinality report Cardinality
50 2.8.4 Scope of Date Functional P1 Client Verify Data Selection
and Cardinality logic
51 2.8.4 Scope of Date Functional P1 Client Verify report Sort Order
and Cardinality
52 2.8.5 Report Header Functional P1 Client Verify report Title
Specification
53 2.8.5 Report Header Functional P1 Client Verify parameter Sheet
Specification value
54 2.7.5 Report Table Functional P1 Client Verify Report Columns in
Specification Vendor Items Store
Ordering Report
2.4 Budget Maintainance Page Issu
55 2.4 Budget Functional P1 Client Verify Year Select List On
Maintainance Page Budget Maintainance
Issue Page
Test Steps Expected Result Execution
Result
ort Requirenments
2.1 Report Access
Below users should be able to access the bealls
analytic reports data
•Alicia Ose
•Avery Ruff-Harris
•Kristen Hunt
•McKenna Scelp
ral Report Specifications
All Currency data should be in US dollars($).
The Store budget report data should be group by
the Fiscal period
The monthly aggregations report data should be
group into calender month
The reports should be stored into account apprved
change orders
Below Observations should be present
1. It should have 'Report Title' field
2. It should have 'Parameter Input' Select list For
Account and Project
3. It should have 'Submit' button field
4. It should not have Clients name on the sheet
The Report Header layout should have below fields
1.It should have the Report Title
2. It should have Parameter sheet input field
3. It should have the label for their respective
values.
The Report Should display following footer on all
the pages
1. Left Side footer : ‘© <yyyy> Copyright
LogicSource, Inc. All Rights Reserved.'
2.Right side footer : Report generated timestamp
(for e.g., Report generated at Apr 24, 2024
10:22:27 PM).
Note : where 'yyyy' the calender year at runtime
Below Observartions should be displayed
1.Each report should display all rows and columns
on single page
2.Report page should be displayed in landscape
mode only
3.Height of page should be 8.5"
4.Page should contain between 50 to 70 rows of
data for each report
Each report format should be PDF or .XSLX
Below parent Id should be Assigned for reports
Parent Org ID = 29824
Below Sub Org IDs should be Assigned for reports
29942 Advertising-Marketing Svcs
31121 Loss Prevention
31122 Supplies
29824 Bealls
29825 Advertising-Marketing Print
29826 Information Technology
29827 Real Estate-FF&E
29828 Packaging
29829 Corporate Services
29830 Distribution & Logistics
29831 Facilities
33530 Store Supplies
User should be able to generate the report for
bealls below all the orgs and sub-orgs
Parent Org ID = 29824
Sub Orgs:
29942 Advertising-Marketing Svcs
31121 Loss Prevention
31122 Supplies
29824 Bealls
29825 Advertising-Marketing Print
29826 Information Technology
29827 Real Estate-FF&E
29828 Packaging
29829 Corporate Services
29830 Distribution & Logistics
29831 Facilities
33530 Store Supplies
Store Budget Report
Report Paremeter sheet should require a selection
of Fiscal year
After selecting a value of Fiscal year user should
able to submit
Following observations should be displayed
1. The list should be empty
2. user should not able to submit the page
The values should be pre-pended with '20' as fiscal
year values are 2 digits of year
One row should be present for bealls store
locations
Below all the Store location should be included in
report
1. All Active and Inactive Stores
2. Store with or without budget for the selected
financial year
3.Store with or without single order transctions
All the store numbers should be in ascending
orders
Store Budget Report Should be sort by Bealls Store
Number in ascending order
Report title should be ' Store Budget Report'
Parameter lable should be as " Fiscal year:',
+Paremeter sheet value year (four digit)
The values should be the last two digit of the fiscal
year
It represent the First and Last day of given fiscal
Period
Report should have following columns in sheet
Location Number
Location Name
Location Status
Aug YYYY
Aug Actual
Difference
Over Y/N
Sep YYYY
Sep Actual
Difference
Over Y/N
Oct YYYY
Oct Actual
Difference
Over Y/N
Nov YYYY
Nov Actual
Difference
Over Y/N
Dec YYYY
Dec Actual
Difference
Over Y/N
Jan YYYY
Jan Actual
Difference
Over Y/N
Feb YYYYY
Feb Actual
Difference
Over Y/N
Mar YYYY
Mar Actual
Difference
Over Y/N
Apr YYYY
Summary by Month Report
The monthly report parameter sheet should have
below parameters
1. Organization
2. Begining Order Date
3. Ending Orde Date
Organization select list should have the
suborgnizatin name of parent Org ID for Org
mapped to logged in user (VPM)
This select list should be selected to 'Null' By
default
After click operation It should display Calender date
picker
This select list should be selected to 'Null' By
default
After click operation It should display Calender date
picker
Monthly report sheet should have One row per
month for the periods in the parameter sheet
range
Below Po statuses should be excluded from the
report
• CANC - Cancelled
• IMCP – Incomplete
• INRP – Incomplete Requestor Pending
• OREJ – Rejected
Report sort order should be like year number +
month number in ascending order For Example :
11/2022 ,12/2022,10/2023
Report title name should be " Order Summary By
Month"
The monthly report parameter sheet should have
below parameters
1. Organization
2. Begining Order Date in mm/dd/yyyy
3. Ending Orde Date in mm/dd/yyyy
Report should have following columns in sheet
Organization
year
month
Number of Pos submitted
Number of items
Total item Quantity
Net Amount
rchase Order) Aging Report
New Column 'Release Date' Should be added in
existing Po aging report After #Po and Before
Status Column
Item Status report
Report should have following two selection Criteria
Organization
Ending Order Date
It should contain Sub Organization names of parent
Org Id for Org mapped logged user
Item status report should display one row per
catlog item with order data
Below Po statuses should be excluded from the
report
• CANC - Cancelled
• IMCP – Incomplete
• INRP – Incomplete Requestor Pending
• OREJ – Rejected
Report should have Following Sort Order
1. prefered Supplier name in Ascending Order
2. Item ID In ascending order
Report Title should be 'Item Status Report'
Below paremeter values should be displayed
1. Organization
2. Ending Order Date In mm/dd/yyyy
Report should have following columns in sheet
Ending Order date
Organization
Prefered Supplier ID
Prefered Supplier
Supplier
Item Sub Category/GL account
GL Account Des
Item ID
Item Descreption
UOM
Pack Qty
Unit Cost
Last 60 Days Units Ordered
Rolling 1 Year Units Ordered
Supplier Part ID
Loc Types
WH pick ID
WH Pick Slot
Item Status
Barcode
QTY Upto
Last Saved Dates
r Order Item History Report
Report should have following Paremeters
Organization
Month
It should contain Sub Organization names of parent
Org Id for Org mapped logged user(VPM)
It should be selected by default to 'Today'
After click Operation Should display Calender Picker
Calender Picker Should have format as mmm-YYYY
For example Jan-2022 , Oct-2023 in decending
order
Item status report should display one row per
supplier, catlog item, store location, month-year
with order data
Below Po statuses should be excluded from the
report
• CANC - Cancelled
• IMCP – Incomplete
• INRP – Incomplete Requestor Pending
• OREJ – Rejected
Report should have below list Displayed
1. Name In acsending order
2. catlog Item ID in ascnding order
3. Store Number/Name I ascending order
Report Title should be 'Vendor Items Store
Ordering Report'
Below paremeter values should be displayed
1. Organization
2. Month <month/year>
Report should have following columns in sheet
Org name
Preferred Supplier
Supplier
Item ID
Item Descripition
UOM
Pack QTY
Store
Year
Month
Nbr POs Submitted
Nbr Units Ordered
Unit Cost
PO Amount
t Maintainance Page Issue
Login Into Application with Bealls user
(711287)
Go to Administration---> Procure To User should navigate to Budget page
Pay---->Budget Maintainance Page
Now Select 2023 Year in Year select Below actions should takes place :
List 1. Year 2023 should be selected in year select list
2. After selecting User should see Budget
Maintainance Data for the financial year 2023 only
Now Again select 2024 Year in year Below actions should takes place :
select list 1. Year 2024 should be selected in year select list
2. After selecting User should see Budget
Maintainance Data for the financial year 2024 only
