Book 4

Test Scenario Description
Applicatio Test cases

S.No n Project Retailer Story Id
Verify Rule No 1 -Customer PO pattern
(DN debit) for EDI file from BOOMI
interface data
GopuffCustomers- PO should starts
CREME – with GUS and have 6 char SMTM
130 Website US SMTM – 18 _18_01
Verify Rule No 1 -Customer PO does not
meet pattern (DN debit) for EDI file
from BOOMI interface data
CREME – GopuffCustomers- if Customer PO does SMTM
131 Website US SMTM – 18 not starts with GUS _18_02
meet pattern (DN debit ) for EDI file
CREME – AEFIS(Banner group)Customers - PO SMTM
132 Website US SMTM – 18 should starts with VON and have 9 char _18_03
meet pattern (DN debit ) for EDI file
133 Website US SMTM – 18 should not start with VON and have 9 _18_04
char
meet pattern (DN Credit) for EDI file
CREME – NormalCustomers - it should accept SMTM
134 Website US SMTM – 18 with/without any data inCustomer PO _18_05
field
Verify Rule No 2 -Customer PO length
(DN debit) for EDI file from BOOMI
interface data
CREME – GopuffCustomers- IfCustomer PO has SMTM
135 Website US SMTM – 18 less than 6 char _18_06
Verify Rule No 2 -Customer PO larger
than maximum length (DN debit) for
EDI file from BOOMI interface data
136 Website US SMTM – 18 more than 6 char _18_07
CREME – AEFIS(Banner group)Customers - if SMTM
137 Website US SMTM – 18 Customer PO has less than 9 characters _18_08
138 Website US SMTM – 18 Customer PO has more than 9 _18_09
characters
Verify Rule No 3 -Customer PO
mandatory for Go Puff (DN debit) for
CREME – GopuffCustomers- if Customer PO field SMTM
139 Website US SMTM – 18 is empty _18_10
mandatory for AFEES (DN debit) for EDI
file from BOOMI interface data
140 Website US SMTM – 18 Customer PO field is empty _18_11
Verify Rule No 3 -Customer PO not
mandatory (DN debit) for EDI file from
BOOMI interface data (Except Go puff/
CREME – AFEES/Doordash) SMTM
141 Website US SMTM – 18 NormalCustomers - it should accept _18_12
with/without
Verify Rule Noany4 - data
Date inCustomer
outside PO
field
retailer's operation date (DN Debit) for
CREME – Delivery date - if Delivery date is less SMTM
142 Website US SMTM – 18 than start date fromCustomer _18_13
hierarchy
Verify Rule No 4 - Date outside
CREME – Delivery date - if Delivery date is SMTM
143 Website US SMTM – 18 greater than end date fromCustomer _18_14
hierarchy
CREME – Delivery date - In between start and SMTM
144 Website US SMTM – 18 end date ofCustomer Hierarchy. _18_15
Verify Rule No 5 - Delivery date in the
future (DN Debit) for EDI file from
BOOMI interface data
CREME – Delivery date - Future Delivery date (it SMTM
145 Website US SMTM – 18 should not be greater/Future than _18_16
system date.)
future (DN Debit) for EDI file from
CREME – Delivery date - it should accept less SMTM
146 Website US SMTM – 18 than or equal to system date . _18_17
Verify Rule No 6 - Delivery date less
than allowable days of current date (DN
Debit) for EDI file from BOOMI
CREME – interface data SMTM
147 Website US SMTM – 18 Delivery date - if Delivery date is older _18_18
than
Verify90Rule
days
Nofrom current date.
6 - Delivery date less
Debit) for EDI file from BOOMI
148 Website US SMTM – 18 Delivery date - if Delivery date is in _18_19
between
Verify Rule90No
days
7 - from current
Delivery date.
ticket no
missing (DN Debit) from BOOMi for EDI
Delivery ticket number - if Delivery
CREME – ticket number field is empty SMTM
Verify Rule No 7 - Delivery ticket no
missing (DN Debit) from BOOMi for EDI
Delivery ticket number - if Debit DN
CREME – has the Delivery ticket number SMTM
Verify Rule No 8 - DuplicateCustomer
PO (DN Debit) for sameCustomer from
BOOMi for EDI
CREME – Customer PO - ExistedCustomer PO for SMTM
151 Website US SMTM – 18 sameCustomer. _18_22
BOOMi for EDI
152 Website US SMTM – 18 differentCustomer. _18_23
BOOMi for EDI
CREME – Customer PO - It should be Unique for SMTM
Verify Rule No 9 - Duplicate delivery
ticket no (DN Debit) from BOOMi for
EDI
CREME – Delivery ticket number - Existed SMTM
154 Website US SMTM – 18 delivery ticket number _18_25
Verify Rule No 9 - by receving Unique
delivery ticket no (DN Debit) from
BOOMi for EDI
CREME – SMTM
Verify Rule No 10 - Duplicate Line
Item(DN Debit) from BOOMi for EDI
Product code - Same product as 2nd
CREME – line item SMTM
Item(DN Debit) from BOOMi for EDI
Product code - Should not be Same
CREME – product SMTM
Verify Rule No 11 -Eaches not in full
boxes (DN Debit) from BOOMi for EDI
Eaches - Eaches other than multiples of
CREME – "eaches per box" SMTM
Verify Rule No 11 - Eaches in full boxes
(DN Debit) from BOOMi for EDI
Eaches - Eaches should accept multiples
CREME – of "eaches per box" SMTM
Verify Rule No 12 - InvalidCustomer(DN
Debit) from BOOMi for EDI
DUNS number - InvalidCustomer DUNS
CREME – number SMTM
DUNS number - DUNS number field is
CREME – empty SMTM
DUNS number - ValidCustomer DUNS
Verify Rule No 13 - Invalid Product (DN
Product code - Invalid Product code
CREME – SMTM
Product code - Product code field is
Verify Rule No 13 - by receiving valid
Product (DN Debit) from BOOMi for EDI
Product code - Valid Product code
CREME – SMTM
Verify Rule No 14 -No delivery date (DN
Delivery date - if delivery date field is
Verify Rule No 14 - Delivery date (DN
CREME – has valid dalivery date SMTM
Verify Rule No 15 - No line item (DN
Product Code - if product code field is
CREME – has any products SMTM
Verify Rule No 16 -Product not
listed(DN Debit) from BOOMi for EDI
Product code - if Product that is not
CREME – mapped to the Customer SMTM
listed(DN Debit) from BOOMi for EDI
Product code - if Product are mapped
CREME – to the Customer SMTM
Verify Rule No 17 -Quantity exceeds
box Threshold - requires verification
CREME – GopuffCustomers - eaches more than 5 SMTM
172 Website US SMTM – 18 box's _18_43
CREME – GopuffCustomers - It should be 5 boxes SMTM
CREME – Food Service migration - eaches more SMTM
174 Website US SMTM – 18 than 5 box's _18_45
CREME – Food Service migration - It should be 5 SMTM
175 Website US SMTM – 18 boxes _18_46
176 Website US SMTM – 18 any value _18_47
(DN Credit) for EDI file from BOOMI
interface data
CREME – GopuffCustomers- PO should starts SMTM
177 Website US SMTM – 18 with GUS and have 6 char _18_48
field
(DN Credit) for EDI file from BOOMI
interface data
than maximum length (DN Credit) for
characters
mandatory for Go Puff (DN Credit)for
mandatory for AFEES (DN Credit)for EDI
file from BOOMI interface data
mandatory (DN Credit) for EDI file from
BOOMI interface data (Except Go puff/
CREME – AFEES/Doordash) SMTM
with/without
Verify Rule Noany5 - data inCustomer
Delivery PO
date in the
field
future (DN Credit)for EDI file from
system date.)
future (DN Credit)for EDI file from
Credit)for EDI file from BOOMI
than
Verify90Rule
days
Credit)for EDI file from BOOMI
between
Verify Rule90No
days
7 - from current
Delivery date.
ticket no
missing (DN Credit)from BOOMi for EDI
Delivery ticket number - if Delivery
CREME – ticket number field is empty SMTM
missing (DN Credit)from BOOMi for EDI
Delivery ticket number - if Credit DN
CREME – has the Delivery ticket number SMTM
PO (DN Credit)for sameCustomer from
BOOMi for EDI
BOOMi for EDI
BOOMi for EDI
CREME – Customer PO - It should be SMTM
197 Website US SMTM – 18 UniqueCustomer PO for _18_68
sameCustomer.
ticket no (DN Credit)from BOOMi for
EDI
delivery ticket no (DN Credit)from
BOOMi for EDI
CREME – SMTM
Item(DN Credit)from BOOMi for EDI
Product code - Same product as 2nd
CREME – line item SMTM
Item(DN Credit)from BOOMi for EDI
Product code - Should not be Same
CREME – product SMTM
Credit)from BOOMi for EDI
Verify Rule NO 19 - Total quantity
exceeds total eaches threshold -
Requires
CREME – Verification (DN Credit) from BOOMi SMTM
209 Website US SMTM – 18 for EDI _18_80
Eaches - more
Verify Rule NOthan 50 eaches
19 - Total quantity
Requires
CREME – Verification (DN Credit) from BOOMi SMTM
210 Website US SMTM – 18 for EDI _18_81
Eaches - Less
Verify Rule Nothan or equalsPO
1 -Customer to 50
pattern
eaches
(DN debit) for Flat file from MuleSoft
interface data
meet pattern (DN debit) for Flat file
from MuleSoft interface data
meet pattern (DN debit ) for Flat file
meet pattern (DN debit ) for Flat file
meet pattern (DN Credit) for Flat file
field
(DN debit) for Flat file from MuleSoft
interface data
Flat file from MuleSoft interface data
characters
mandatory for Go Puff (DN debit) for
mandatory for AFEES (DN debit) for Flat
file from MuleSoft interface data
mandatory (DN debit) for Flat file from
MuleSoft interface data (Except Go
CREME – puff/ AFEES/Doordash) SMTM
with/without
Verify Rule Noany
4 - data
Date inCustomer
outside PO
field
CREME – Delivery date - if Delivery date is less SMTM
223 Website US SMTM – 18 than start date fromCustomer _18_94
hierarchy
CREME – Delivery date - if Delivery date is SMTM
224 Website US SMTM – 18 greater than end date fromCustomer _18_95
hierarchy
CREME – Delivery date - In between start and SMTM
225 Website US SMTM – 18 end date ofCustomer Hierarchy. _18_96
future (DN Debit) for Flat file from
MuleSoft interface data
system date.)
future (DN Debit) for Flat file from
Debit) for Flat file from MuleSoft
than
Verify90Rule
days
Debit) for Flat file from MuleSoft
between
Verify Rule90No
days
7 - from current
Delivery date.
ticket no
missing (DN Debit) from MuleSoft for
Flat file
CREME – Delivery ticket number - if Delivery SMTM
230 Website US SMTM – 18 ticket number field is empty _18_101
missing (DN Debit) from MuleSoft for
Flat file
CREME – Delivery ticket number - if Debit DN SMTM
231 Website US SMTM – 18 has the Delivery ticket number _18_102
MuleSoft for Flat file
sameCustomer.
ticket no (DN Debit) from MuleSoft for
Flat file
delivery ticket no (DN Debit) from
CREME – SMTM
Item(DN Debit) from MuleSoft for Flat
file
CREME – Product code - Same product as 2nd SMTM
237 Website US SMTM – 18 line item _18_108
Item(DN Debit) from MuleSoft for Flat
file
CREME – Product code - Should not be Same SMTM
238 Website US SMTM – 18 product _18_109
boxes (DN Debit) from MuleSoft for Flat
file
CREME – Eaches - Eaches other than multiples of SMTM
239 Website US SMTM – 18 "eaches per box" _18_110
(DN Debit) from MuleSoft for Flat file
Debit) from MuleSoft for Flat file
CREME – SMTM
Product code - Product code field is
Verify Rule No 13 - by receiving valid
Product (DN Debit) from MuleSoft for
Flat file
CREME – Product code - Valid Product code SMTM
listed(DN Debit) from MuleSoft for Flat
file
CREME – Product code - if Product that is not SMTM
251 Website US SMTM – 18 mapped to the Customer _18_122
listed(DN Debit) from MuleSoft for Flat
file
CREME – Product code - if Product are mapped SMTM
252 Website US SMTM – 18 to the Customer _18_123
CREME – GopuffCustomers - It should be 5 box's SMTM
(DN Credit) for Flat file from MuleSoft
interface data
field
(DN Credit) for Flat file from MuleSoft
interface data
characters
mandatory for Go Puff (DN Credit)for
mandatory for AFEES (DN Credit)for
mandatory (DN Credit) for Flat file
from MuleSoft interface data (Except
CREME – Go puff/ AFEES/Doordash) SMTM
with/without
Verify Rule Noany
5 - data inCustomer
Delivery PO
date in the
field
future (DN Credit)for Flat file from
system date.)
future (DN Credit)for Flat file from
Credit)for Flat file from MuleSoft
than
Verify90Rule
days
Credit)for Flat file from MuleSoft
between
Verify Rule90No
days
7 - from current
Delivery date.
ticket no
missing (DN Credit)from MuleSoft for
Flat file
CREME – Delivery ticket number - if Delivery SMTM
274 Website US SMTM – 18 ticket number field is empty _18_145
missing (DN Credit)from MuleSoft for
Flat file
CREME – Delivery ticket number - if Credit DN SMTM
275 Website US SMTM – 18 has the Delivery ticket number _18_146
sameCustomer.
ticket no (DN Credit)from MuleSoft for
Flat file
delivery ticket no (DN Credit)from
CREME – SMTM
Item(DN Credit)from MuleSoft for Flat
file
CREME – Product code - Same product as 2nd SMTM
281 Website US SMTM – 18 line item _18_152
Item(DN Credit)from MuleSoft for Flat
file
CREME – Product code - Should not be Same SMTM
282 Website US SMTM – 18 product _18_153
Credit)from MuleSoft for Flat file
Verify Rule NO 19 - Total quantity
Requires
CREME – Verification (DN Credit) from MuleSoft SMTM
290 Website US SMTM – 18 for Flat file _18_161
Eaches - more
Verify Rule NOthan 50 eaches
19 - Total quantity
Requires
CREME – Verification (DN Credit) from MuleSoft SMTM
291 Website US SMTM – 18 for Flat file _18_162
Eaches - Less
Verify user than to
is able or launch
equals DT
to 50
site.
eaches
CREME – SMTM
Verify DT user is able to directly login
to DT dashboard
CREME – SMTM
Verify DT administrative is able to
login to the site
CREME – SMTM
Verify by clicking on any DT on account
to proceed page
CREME – SMTM
Verify by clicking on Create DN Debit
under My tasks or TODOs section
CREME – SMTM
meet pattern (DN Debit) - IfCustomer
groups have prefix (pattern)
CREME – SMTM
groups have prefix (pattern) with
CREME – Invalid pattern for GopuffCustomers. SMTM
groups have prefix (pattern) with valid
CREME – pattern for GopuffCustomers. SMTM
groups have prefix (pattern) - Without
CREME – data for GopuffCustomers. SMTM
CREME – Invalid pattern for AEFIS(Banner group) SMTM
301 Website US SMTM – 18 (Banner group)Customers. _18_172
CREME – pattern for AEFIS(Banner group) SMTM
302 Website US SMTM – 18 Customers. _18_173
CREME – data for AEFIS(Banner group) SMTM
303 Website US SMTM – 18 Customers. _18_174
Verify Rule No 1 - IfCustomer groups
dont have prefix (pattern)
CREME – SMTM
than maximum length (DN Debit)
(TheCustomer PO filed should follow
CREME – certain Length as below) SMTM
305 Website US SMTM – 18 Length of PO should be certain _18_176
ex.AEFIS
Verify Rule- 9No
digit
2 -Customer PO larger
Go Puff - 6 Digits
than maximum length(DN Debit) -
IfCustomer groups have prefix (pattern)
CREME – - By giving less than 6 char inCustomer SMTM
306 Website US SMTM – 18 PO filed for GopuffCustomers. _18_177
than maximum length (DN Debit) -
CREME – - By giving greater than 6 char SMTM
307 Website US SMTM – 18 inCustomer PO filed for _18_178
GopuffCustomers.
than maximum length(DN Debit) -
308 Website US SMTM – 18 PO filed for AEFIS(Banner group) _18_179
Customers.
than maximum length (DN Debit) -
309 Website US SMTM – 18 inCustomer PO filed for AEFIS(Banner _18_180
group) Customers.
Verify Rule No 2 - IfCustomer PO
doesn't have any specific length
CREME – SMTM
retailer's operation date (DN Debit)
CREME – SMTM
retailer's operation date (DN Debit) -
Select any less than start ofCustomer
CREME – Hierarchy SMTM
Select any greater than end date
CREME – ofCustomer Hierarchy SMTM
Verify by selecting any in between start
CREME – or end date SMTM
future (DN Debit)
CREME – SMTM
Debit)
CREME – SMTM
missing (DN Debit)
CREME – SMTM
PO (DN Debit) for sameCustomer
CREME – SMTM
PO (DN Debit) for differentCustomer
CREME – SMTM
Verify Rule No 9 -Duplicate delivery
ticket no (DN Debit)
CREME – SMTM
Verify Rule No 9 - by giving Unique
delivery ticket no (DN Debit)
CREME – SMTM
Verify Rule No 10 -Duplicate Line
Item(DN Debit)
CREME – SMTM
boxes (DN Debit)
CREME – SMTM
Verify Rule No 11 -by giving Eaches in
full boxes (DN Debit)
CREME – SMTM
(DN Debit)
Verify Rule No 12 -InvalidCustomer(DN
Debit)
CREME – SMTM
Debit)
Verify Rule No 12 - by giving
validCustomer(DN Debit)
CREME – SMTM
Verify Rule No 13 -Invalid Product (DN
Debit)
CREME – SMTM
Verify Rule No 13 - by giving valid
Product (DN Debit)
CREME – SMTM
Debit)
CREME – SMTM
Verify Rule No 14 - by selecting delivery
date (DN Debit)
CREME – SMTM
Debit)
CREME – SMTM
Verify Rule No 15 - by giving any line
item (DN Debit)
CREME – SMTM
listed(DN Debit)
CREME – SMTM
(DN Debit)
(DN Debit)
CREME – GopuffCustomers - It should be 5 boxes SMTM
(DN Debit)
(DN Debit)
339 Website US SMTM – 18 boxes _18_46
(DN Debit)
Verify Rule No 18 - Sub - Distributor
Missing
(DN Debit)
CREME – SMTM
Verify Rule No 18 - if Sub - Distributor is
mapped (DN Debit)
CREME – SMTM
meet pattern (DN Credit) - IfCustomer
CREME – Invalid pattern for AEFIS(Banner group) SMTM
343 Website US SMTM – 18 (Banner group)Customers. _18_208
CREME – pattern for AEFIS(Banner SMTM
344 Website US SMTM – 18 group) Customers. _18_209
CREME – data for AEFIS(Banner SMTM
345 Website US SMTM – 18 group) Customers. _18_210
Verify Rule No 1 - IfCustomer groups
dont have prefix (pattern)
CREME – SMTM
than maximum length (DN Credit)
(TheCustomer PO filed should follow
CREME – certain Length as below) SMTM
347 Website US SMTM – 18 Length of PO should be certain _18_212
ex.AEFIS
Verify Rule- 9No
digit
2 -Customer PO larger
Go Puff - 6 Digits
than maximum length(DN Credit) -
348 Website US SMTM – 18 PO filed for GopuffCustomers. _18_213
than maximum length (DN Credit) -
349 Website US SMTM – 18 inCustomer PO filed for _18_214
GopuffCustomers.
missing (DN Credit)
CREME – SMTM
PO (DN Debit) for sameCustomer
CREME – SMTM
PO (DN Debit) for differentCustomer
CREME – SMTM
Verify Rule No 9 -Duplicate delivery
ticket no (DN Credit)
CREME – SMTM
Verify Rule No 9 - by giving Unique
delivery ticket no (DN Credit)
CREME – SMTM
Verify Rule No 10 -Duplicate Line
Item(DN Credit )
CREME – SMTM
Verify Rule No 12 -InvalidCustomer(DN
Credit)
CREME – SMTM
Verify Rule No 12 - by giving
validCustomer(DN Credit)
CREME – SMTM
Credit)
CREME – SMTM
Verify Rule No 14 - by selecting delivery
date (DN Credit)
CREME – SMTM
Credit)
CREME – SMTM
Verify Rule No 15 - by giving any line
item (DN Credit)
CREME – SMTM
Verify Rule NO 19- Total quantity
exceeds
total eaches threshold - Requires
CREME – Verification (DN Credit) SMTM
Verify Rule NO 19- Total quantity not
exceeding total eaches threshold - Does
not require verification (DN Credit)
CREME – SMTM
Verify by clicking Save button after
clicking on validate and submit button
with errors for DN Debit form
CREME – SMTM
does not meet pattern (DN Debit)
for EDI file from BOOMI.
Customer GopuffCustomers- PO should starts
Banner - with
VerifyGUSRule No 1 -Customer PO
Go Puff 1. Magento
does not meet willpattern
recevice (DNEDIDebit)
810
Customer
Customer file from BOOMI for Go
for EDI file from BOOMI interface
DUNS
Banner- - puffCustomers
data havingCustomer PO
05749904
Go Puff starting
GopuffCustomers-and
with GUS 6 char PO
if Customer
90069
Customer 2. Launch
does not DT
startssite and Login with Actual
DT Verify Rule No 1with GUS PO
-Customer
Test- BK
ForCusto
DUNS Data
- valid
Test
1. data
case
Magento
does description
not meet willpattern
recevice (DN 810 Expected Result
EDI) for Result Status
PO
mer -
05749904 3. Navigate
file from to that
BOOMI forparticuar
Go DT
Should
Banner - EDI file frompage
dashboard BOOMI interface data It should not show any error
90102
Customer puffCustomers
AEFIS(Banner havingCustomer -PO
group)Customers
start
AAFES
DT - BKwith 4.
notClick on
starting DN Debit
with GUS(Open)
and 6 link
char message inCustomer PO field
Banner
GUS - PO should starts with VON
PO
AAFES - and under
2.
1. LaunchMy
Magento
dashboard
DTwill
siterecevice
and Login with
EDIPO
if we receive vaildCustomer
810 PO number from BOOMI for
have
Distributo
Should 6 5. Search
Verify
valid Rule forNothat
1 Customer
-Customer
dataBOOMI for AEFIS(Banner PO
Customer
rdigits(GU file from
number notusing
have
DUNS
-A3 6
-
does
3. Navigate meet
group)Customers to delivery
pattern
that ticket
(DN ) for
particuar
havingCustomer DT EDI
S334567)
Customer
digits but number
EDI file
dashboard /DUNS
from BOOMINumber interface data Working asPass
69556810
DUNS - PO starting page
AEFIS(Banner with VON and 9 char-
group)Customers
should
32216 4.
2. Click
Launch onDT DNsiteDebit(Open)
and Login link It should show a "Customer
69556810
not PO should starts with VON with PO does not meet pattern."
DT
32216 -start
A3 under
valid
1.
My dashboard
data will recevice EDI 810
Magento
with
PO - 5. Search
Verify
3. RuleforNo
Navigate tothat
1 - Customer
that ForCustomer
particuar PO
DT error message inCustomer PO
Delivery
'GUS'(QW file fromthat
number BOOMI
using for AEFIS(Banner
Should
Date -
groups
dashboard
group)Customers page havingCustomer field if we receive invaild
delivery
dont have ticket
any PO
E789654)
start with number
pattern
4. Click /DUNS
for
on DN Number
EDI(Open)
file fromlinkBOOMI
under pattern from BOOMI for EDI Working asPass
MM-DD- PO starting
interface datawith VON and 9 char
'VON'
YYYY and My
2. dashboard
Launch DT site and It should not show any error
ForCusto
have 9 NormalCustomers
5. Search for that - it Login
shouldwith
Customer PO message inCustomer PO field
PO
mer - valid
accept data
with/without any data
char(VON
Should number
3. using
Navigate to delivery ticket if we receive vaildCustomer
Banner
09876543 - inCustomer
number
Verify /DUNS
Rule POthat
No 2field particuar DT
Number
-Customer PO PO number from BOOMI for
not
Family start dashboard
1. Magento page
will DN
recevice EDI 810 EDI
2)
with 6. Click
larger
4. on
than that
Click onBOOMI maximum and observe
length for
DN (Open) link under Working asPass
Dollar
Customer file
EDI from
file from BOOMI interface data It should show a "Customer
'VON'
DT - BKand My
2. dashboard
Launch DT site and Login with
Banner
have 9 - GopuffCustomers-
5. Search IfCustomer
for that Customer POPO PO does not meet pattern."
Customer
Go Puff valid
has data
less than 6 char
char(HJK0
DUNS - number
3. Navigate usingto delivery ticket DT error message inCustomer PO
Customer
98765675
Customer 1. Magento
number
Verify /DUNS
Rule willthat
No 2
particuar
recevice
Number
-Customer EDIPO810 field if we receive invaild
24472631 dashboard page for Go
)DUNS
Banner
12614
-- file
6. from
Click
larger
4. Click on
than
on
BOOMI
that
DNmaximumDN and
debit observe
link PO pattern from BOOMI for EDI
length for
(Open) Working asPass
05749904
Go Puff puffCustomers
EDI fileMy havingCustomer
PO
90102- With under
less than 6dashboard
char IfCustomer PO
Customer
any GopuffCustomers-
DT
DUNS - value
BK- 5.
2.
has
Search
Launch
more
for
DT
than
that
site Customer
and PO
Login with
6 -Customer
char
or
PO - number
Verify
valid using
Rule No delivery
1
data will recevice EDI 810 ticketPO
05749904
without 1. Magento
number not/DUNS Number
Should
90102
does
3. Navigate
file from
meet pattern
to that
BOOMI for
(DN) for
particuar
Go observe DT EDI It should not show any error
value
Customer
start with 6. Click
file from
dashboard on that
pagehavingCustomer PO message inCustomer PO field.
BOOMI DN and
interface data Working asPass
DT - BK
Banner - puffCustomers
AEFIS(Banner group)Customers
'GUS'
PO - but 4. Clickthan
more on DN Debit(Open) link - if It should show a "Customer
6 char
AAFES
have less Customer
under
Verify My
RuleDTPO has
dashboard
Nosite less than 9PO
2 -Customer char. PO smaller than length."
Should
Customer 2.
1. Launch
Magento will and Login
recevice EDIwith
810
than
start 6with 5. Search
larger
valid than
data formaximum
that Customer PO
length for error message inCustomer PO
DUNS
digits(GU
Customer - file
EDI from
number
file BOOMI
using
from for AEFIS(Banner
delivery
BOOMI ticket
interface data field if we receive invaild
GUS
69556810but 3. Navigate to thathavingCustomer
group)Customers particuar DT
S7654)
Banner
have - number
AEFIS(Banner
dashboard /DUNS
page Number
group)Customers - if pattern
It shouldfrom
showBOOMI for EDI
a "Customer Working asPass
63710
AAFES PO with
Customer less
PO than
length 9 char..
is more than 9 PO larger than maximum
more
DT - ARC 4.
2. Click
and Login linkwith
Customer
than char
PO
DUNS - 6- under
valid
1.
My
Verifydata.
Magento
dashboard
Rule No 1 -Customer PO
will recevice EDIDebit)
length" error message
810 inCustomer PO field if we
digits(GU
Should 5.
3. Search
does not
Navigate for
meet that Customer
pattern
to that (DN PO
69556810
S7865432 file fromfile
number
for EDI BOOMI
using
from forparticuar
delivery
BOOMI AEFIS(Banner
ticket
DT
interface receive invaild pattern from
start
63710 with dashboard
group)Customers page havingCustomer BOOMI for EDI
)'VON' and number
data
4. Click on/DUNS
DNthan Number
(Open) link under It should show a "Customer Working asPass
DT - A3 PO with less
GopuffCustomers- 9ifchar..
Customer PO PO smaller than required
have
PO - less My
2. dashboard
Customer
than 9 is
5. empty
Search
Should
DUNS - valid
1. data.forwill
Magento
that Customer PO
recevice
length" error message
EDI 810 inCustomer PO field if we
char
start with number
3. Navigate using delivery
to that ticket
05749904
(VON987 file from/DUNS
number BOOMI forparticuar
Number Go DT
receive invaild pattern from
'VON'
90069(Go and dashboard
puffCustomers page havingCustomer PO BOOMI for EDI
6544)
have 6.
4. Click
Click on
on that
DN DN andlink
(Open) observe
under It should show a "Customer Working asPass
Puff) empty
more
DT - BK My
2. Launch DT site and Login with PO larger than maximum
dashboard
than 9
Customer 5. Search
valid datafor that Customer PO length" error message
char
PO - number using delivery
3. Navigate to that particuar DT ticket inCustomer PO field if we
(VON987
empty(It number /DUNS
dashboard page Number receive invaild pattern from
6544569)
should 6.
4. Click
Click on
on that
DN debitDN and (Open)observe
link BOOMI for EDI Working asPass
not under My dashboard It should show a "Customer
accept if 5. Search for that Customer PO PO required." error message
Customer number using delivery ticket inCustomer PO field if we
PO field is number /DUNS Number receive empty PO from
empty) 6. Click on that DN and observe BOOMI for EDI for go puff
DUNS interface operation
data
DT - BK- retailer's
2. Launch DT site and
NormalCustomers
date (DNwith
- it Login
should
Debit)
24472631
Customer valid for EDI file
data from BOOMI interface
05608 accept
data with/without any data
PO - 3. Navigate
inCustomer to
PO that particuar DT
DT - A3 Delivery
empty(It dashboard datepage- field
if Delivery date is
Delivery 1.
lessMagento
than will
start recevice
date EDI 810
fromCustomer
should 4.
fileClick
from on DN
BOOMI (Open) link under
date
not - 12- hierarchy
Customer My dashboard
Verify RuleDT Nosite4 - and
DateLoginoutside It should show a "Customer
08- 2. Launch EDIwith
accept-if 1.
DUNS 5. Magento
Search
retailer's
valid for will
that
operation
dataBOOMI
recevice
Customer
date (DN 810
PO
Debit) PO required" error message
2013(MM
Customer
24472631 file
for from
number
EDI using
file from delivery
BOOMI ticket
interface inCustomer PO field if we
Customer
-DD- 3.
2. Navigate
Launch DT tosite
thatand particuar
Login DT
with
PO field is
05608 - dashboard
DUNS number
data /DUNS
page Number receive empty PO from
YYYY
empty) )
DT - A3 4. valid
6. data
Click
Delivery on that
date DN
-debit and observe is BOOMI for EDI.
24472631
(Start 3. Click
Verify on
Rule
Navigate DN
No
toend4if- Delivery
that Date(Open) date
outside
particuar link
DT
Delivery
12614 greater than
under Myoperation
retailer's dashboard datedate (DN Debit)
date
date 12-
- 12- dashboard
fromCustomer pagehierarchy
DT -
07-2013BK 5.
for Search
EDI for
file fromthat Customer
BOOMI PO
interface It should not show any error
31-9999 it 4.
Customer 1. Click
number
data
on DN
Magento using
debit
willdelivery (Open)
recevice EDIlink
ticket 810 message inCustomer PO field.
Should
(MM-DD- under
file fromMyBOOMI
dashboard It should show a " Date
PO
DUNS
not - any - number
Delivery
5. Search /DUNS
date
for - In
that Number
betweendate
Delivery start Customer PO will operation
outside retailer's be same as
YYYY)
data
24472631 which 2.
6. Launch
Click
and end on DT
thatsiteDN and
and Login
observewith DN ticket number
accept
(End date valid wedate
data
ofCustomer
receive less than start date " error message on
05608
less than Hierarchy.
date fromCustomer Hierarchy delivery date field if we
12-31-
DT - A3 3.
1. Navigate
Magento to that
willticket particuar
recevice EDI DT810 receive delivery date less than
start
9999 date using
it dashboard deliverypage number
Delivery
fromCust file fromNumber
/DUNS BOOMI start date(Customer
Should
date - 4.
2. Click
Launchon DN
DT debit
site and (Open)
Login link
with It should show a " Date
omer
not 6. Click on
Verify Rule
under that filtered DN Debit Hierarchy)
No 5 - Delivery date in outside retailer's
My dashboard from BOOMI for
operation
2013-12-
hierarchy) valid
and data
observe
theSearch
futurefor (DN Debit) for EDI EDI file.
file date " error message on
accept
08 and 5.
3. Navigate tothat
thatDelivery
particuar dateDT
greater from
which BOOMI
we interface
receive greater data than end delivery date field if we
9999-12-
Customer dashboard
Delivery datepage-ticket
Future Delivery
than
31 date
it - 4. using delivery number
Click on DN debit (Open) link receive delivery date greater
DUNS
fromCust date
/DUNS Number than end date(Customer
should
24472631 under 1. My dashboard
Magento will recevice EDI 810
omer
accept In 5.6. Click
Verify on that
RuleforNothat
Search filtered
5 - Delivery DN
Delivery date date in Hierarchy) from BOOMI for
Debit
05608
hierarchy) file
and from
observe
the future BOOMI
(DN Debit)for delivery
for EDI datefile EDI file. not show any error
between
DT - A3 which 2. we receive
Launch DT site inbetween
and Login start
with It should
start from
and Verify
and BOOMI
end date
Rule interface
Noof6 that data
Customer
- Delivery date message in Delivery date field
Delivery
Customer valid data
Delivery date - itdelivery
should accept less if we receive any date (old 90
end
date date Hierarchy
less than using
allowable days ticket
of current
DUNS - 3.
ofCustom thanNavigate
number
date or equal
(DN /DUNS
toto
Debit)
that particuar
system
Number
for date
EDI file
DT
.
from days from current date.) in
(MM-DD-
24472631 6. dashboard
1. Magento page
will recevice EDI 810
er
YYYY) it 4. Click
BOOMI
Click on that
interface
on filtered
data
DN Debit(Open) DN Debit
link between start and
It should show end date
a "Delivery
05608
Hierarchy. file
and from
observe
Delivery BOOMI for delivery date ofCustomer Hierarchy.
Should
DT - A3 under 2. Mydate
Launch DT
- if Delivery date is date should not be greater
dashboard
site and Login with
Customer
not older
5.
Verify than
Search
Rule 90
forNo days
that from
6 - delivery
Delivery current
date
date than system date.' error
Delivery
DUNS - date.valid data
accept
date using
less delivery
than ticket
allowable number
days of current message in Delivery date field
24472631 3.
future 1. Navigate
Magento
/DUNS
date (DNNumber
to
willthat
Debit) for
particuar
recevice
EDI file
DT
EDIfrom
810 if we receive any future date
(MM-DD-
05608 dashboard
file fromon page for older than 90
BOOMI
delivery
YYYY) it 6. Click
BOOMI
4. Click that
interface
on DebitDN
data andlink
DN Debit(Open) as delivery date from BOOMI
DT -
dates. A3 days
observeas
Delivery delivery date
- if Delivery date is in for EDI
should
Delivery under
2. Mydate
Launch dashboard
DT site and Login with
Customer
accept between
5. Search 90
for that from
days deliverycurrent
date
date
DUNS - date.valid data
less than
Customer
(MM-DD- using
3. delivery ticketparticuar
number It should not show any error
24472631
or equal
DUNS - 1. Navigate
Magento
/DUNS Number
to
willthat
recevice EDI DT 810 message in Delivery date field
YYYY)
05608 if dashboard
file from page for between 90 It should show a "Delivery
BOOMI
to system 6.
84734000
Delivery Click
Verify
4. Click on
Rule that 7DebitDN
No Debit(Open)
on current
DN - Delivery and ticket
link if we less
date receive
thanvalid delivery
allowable days
DT
date-
10001isA3 days
observefrom
no missing date.
(DN Debit) from BOOMi of current date " errorEDI
date from BOOMI for
date
Delivery under My dashboard
DT - BK 2.
older for
5.
Launch
EDI for
Search
that delivery date message in delivery date field
date
Delivery valid data
Delivery ticketticket
number - if Delivery If user receive delivery date
than
(MM-DD- 90 using delivery number
ticketfrom 3.
days
Navigate
ticket
/DUNS number
Number
to that
field particuar
is empty DT older than 90 days from
YYYY) if
number - 6. dashboard
1. Click
Magento page
willDebitDN
recevice and EDI 810 current date from BOOMI for
current
Delivery 4. Click on that
onBOOMI
DN Debit(Open) link
without
date. file from
observe
Verify Rule No 7 -for emptyticket
Delivery delivery EDI
date is
delivery date under My dashboard
older no
5. missingfor
Search (DN Debit) from BOOMi
ticket 2.
for Launch
EDI DT that
site anddelivery
Logindate with
than 90 using
number(it valid delivery ticket number
data It should not show any error
days from DeliveryNumber
/DUNS ticket number - if Debit message in Delivery date field
shpould
Customer 3. DNNavigate
has on
thethatto that particuar
Delivery ticket DT
number
current
not 6. Click
dashboard page DebitDN and if we receive valid delivery
DUNS
date. - 1. Magento
observe will recevice EDI 810 date from BOOMI for EDI
accept
84734000 if 4.fileClick
fromonBOOMI
DN Debit(Open) link If user receive empty delivery
delivery
10001 under
2. Launch DT site and Login with ticket number from BOOMI
My dashboard
ticket
DT - BK 5. Search
valid datafor that empty delivery for EDI then it should show
number ticket
Delivery 3. Navigate using toDUNSthatNumber
particuar DT "Delivery ticket no missing"
field
ticket is 6. Click on
dashboard page that filtered Debit DN error message in Delivery
empty) and observe
number - 4. Click on DN Debit(Open) link ticket field.
1232123 under My dashboard If user receive delivery ticket
(WIth 5. Search for that delivery ticket number from BOOMI for EDI
delivery using DUNS Number then it should not show any
ticket 6. Click on that filtered Debit DN error message in Delivery
number) and observe ticket field.
DUNS - for EDI
DuplicateCustomer PO (DN Debit)
32
84734000 3.
1. Navigate
Magento to
willthat particuar
recevice EDI DT810for
(It should for sameCustomer
dashboard page from BOOMi
10001 file
EDI from BOOMI for
not
DT - BK 4. Click on DN Debit(Open)
DuplicateCustomer PO be link
accept in Customer
under My DT PO - It should
dashboard
Customer 2. Launch
UniqueCustomer site and
PO for Login with If user receive any
case
PO - of 5. Search
valid data for that existingCustomer PO number
sameCust sameCustomer.
DuplicateCustomer PO using from BOOMi for EDI
GUS8893 3.
1. Navigate
Magento to
willthat particuar
recevice EDI DT810
omer
Customer
32 PO delivery
dashboard ticket number
page for /DUNS for sameCustomer then it
Customer
for
DUNS - file from
Number
Verify Rule BOOMI
No 9 -by receving should show
(It
DUNSshould 4. Click on DN Debit(Open) link
DUNS
sameCust
24472631
accept --in DuplicateCustomer
6. Click
Duplicate
under on that
My delivery
dashboardDebitDN PO and
ticket no (DN "DuplicateCustomer PO" error
Customer
84734000
24472631
omer) 2. Launch
observe DT site and Login with message
12614
case
DUNS
10001 of- Debit)
5. Search
valid
from forBOOMi
dataticket that for EDI If user receive any PO field
inCustomer
12614
DT - BK
sameCust Delivery
DuplicateCustomer number - Existed
PO using DT existingCustomer PO number
24472631
DT - BK 3. Navigate to that particuar
omer
12614 PO delivery
delivery ticket
ticket number
number /DUNS from BOOMi for EDI for
Customer
Delivery dashboard
1. Magentopage will recevice EDI 810 differentCustomer then it
for
DT
PO -
- BK Number
4.
ticket
diffCusto fileClick
6. fromon
Click
DN Debit(Open)
onBOOMI for existed
that DebitDN and
link
should not show any error
GUS009
product
number- under
delivery My dashboard
ticket number
mer)
Delivery
(It should observe
Verify
5. SearchRuleforNothat 9 - by receving message inCustomer PO field
code-
80622235
ticket 2. Launch
Unique DT siteticket
delivery and Loginno (DN with If user receive any
accept
(It in
07585603
03 DuplicateCustomer
valid data PO using uniqueCustomer PO number
number-
case
1140 of Debit)
delivery fromticketBOOMinumber for /DUNS
EDI from BOOMi for EDI for
should
80622231 3.
1. Navigate
Magento to
willthat particuar
recevice EDI DT810 existedCustomer then it
uniqueCu
Again
not Number
Verify
dashboard Rule No 10 -by receving
page for delivery ticket If user receives any existed
11
stomer file
6. from BOOMI
Click
same
accept
(It should in 4. Click on
Duplicate
number onLinethat DebitDNDebit)
Item(DN
DN Debit(Open) andlink should
deliverynot show
ticket any error
number from
PO)
product
case of observe
from BOOMi
under My for EDI
dashboard message
BOOMi inCustomer
for EDI in PO field
delivery
accept
Customer
code inin 2. Launchcode
Product DT site
- Same andproduct
Login with as
same
case of 5. Search
valid data for that delivery ticket ticket field then it should
DUNS
2nd line
existing - 2nd
numberline item
using delivery ticket shows a "Delivery ticket
Customer
unique 3. Navigate to
24472631
item
delivery- 1. Magento
number /DUNS willthat particuar
recevice EDI DT810
DUNS
delivery
05644
07585603
- Verify
dashboard
file from
Rule page for Duplicate Line number already used" error
No
BOOMI
10Number
- Duplicate Line
ticket
24472631
ticket 6. Click
Item(DN
4. on
Click onDebit)that DebitDN
from BOOMi
DN Debit(Open) andlinkfor message in Delivery ticket
1140
number)
12614 Item
observe
EDI number field. any unique
number
DTshould
(It - A3 under
2. LaunchMy DT dashboard
site and Login with If user receives
DT
in - BK
Product Product
5. Search code - Should not be Same
for that delivery ticket no delivery ticket number from
not valid
product data as 2ndticketline item
delivery
code
accept - using
3. delivery
Navigate to that number DT
particuar BOOMi for EDI in delivery
product
ticket
07756700 1. Magento
/DUNS
Verify Number
Rule will
No 11recevice
-Eaches EDI
not 810
in ticket field then it shouldn't
incase
code 1-of dashboard
file from page
BOOMI
number
2204
if we 6.
full
4. Click
boxes
Click on
onDT that
(DN
DNsite DebitDN
Debit) from BOOMi
Debit(Open) and link show
If userany errorsame
receives message in
product
Customer
07684010
field) 2. Launch
observe and Login with delivery ticket number field.
(Eaches
receive
DUNS - for EDIMy dashboard
under code as 2nd line item from
0125
Per Box is valid
Eaches data- Eaches other than Line
same
24472631
product 5.
3. Search
Navigate for tothat Duplicate
that particuar BOOMi for EDI in product
24)
product
05644 multiples
Item using ofdelivery
"eaches per box"DT
ticket code field then it show a
code 2- dashboard
1. Magento page
will11 recevice EDI 810 "Duplicate Line Item" error
code
07684048 as number
Verify
4. Click Rule/DUNS
onBOOMINo Number
-Eaches
DN Debit(Open) in full
link in
Eaches
DT - A3 -
second file
6.
boxesfrom
Click on dashboard
(DN that
Debit) for
DebitDN
from Eaches andnotfor
BOOMi message on product code
5116
Customer
50 under
full boxesMy
line
Product
(It item)
should observe
EDI
5. Search for field
DUNS
(It
codeshould -
- in 2. Launch
Eaches - DT that
Eaches
Duplicate
siteshould
and Login
be
Line
with If user receives different diff
accpet
24472631
not Item(Should
valid not be
dataof "eaches per box" Same product line item from BOOMi for EDI
07756700
case
01788 of in multiples
as 2nd line item) using delivery in product code field then it
accept
2204 3.
1. Navigate
Magento to
willthat particuar
recevice EDI DT810 should not show any error
diff
case line
of ticket
dashboard number /DUNS Number
page for Eaches in full
(Eaches
level file
6. fromonBOOMI
Click
DT - A6
eaches
Per Box is
Verify
4.
boxes on that
ClickRule DN DebitDN
No Debit(Open)
12 - andlink message on product code
items)
other observe
InvalidCustomer(DN
under My DT dashboard Debit) from field
24) 2. Launch
BOOMi for EDIsite and Login with
than
Customer 5. Search
valid data for that Eaches not in full if user receives eaches other
DUNS
multiples
DUNS -- DUNS
boxes number
using - InvalidCustomer
delivery ticket number than multiples of "eaches per
Eaches
number - 3.
DUNSNavigate
number to that particuar DT
of
24472631
48 /DUNS
dashboard Number page box" from BOOMi for EDI then
24472631
"eaches
01707 1.
6. Magento
Click
Verify on
Rule will
that recevice
filtered
No Debit(Open)
12 - EDI
DebitDN 810 it should show "Eaches not in
(It should
01788 4.
fileClick
from onBOOMI
DN for link
per
acceptbox") in and observe
InvalidCustomer(DN
under My dashboard Debit) from full boxes" on eaches box.
(It
DT should
- A6 InvalidCustomer
BOOMi for EDI DUNS number
case
not of 5.
2. Search
Launch for
DT that
site Eaches
and Login in full
with if user receives eaches
multiples DUNS
boxes number
using - DUNS
delivery number
ticket number multiples of "eaches per box"
accept valid
field isdata
empty
of
incase /DUNS Number form
userBOOMI for EDI then user
DUNS of
"eaches
3.
1. Navigate
6. Magento
Click on
to
willthat
that
particuar
recevice
filtered EDI DT
DebitDN 810 If reveives
shouldn't get show any error
invalid
number dashboard page InvalidCustomer DUNS
per
Duns box")- file
and
4.
from
observe BOOMI message.
Empty 2. Click
and Login link with number in DUNS number
number
(It should under
valid dataMy dashboard field from BOOMi for EDI then
in
notDUNS 5. Search for that InvalidCustomer
3. Navigate to that particuar DT it should show
number
accept using delivery
dashboard page ticket number "InvalidCustomer"
If user reveives error
filed)
incase of 6. Click on that DebitDN
4. Click on DN Debit(Open) link and message on DUNS
emptyCustomer DUNS number
empty observe
under My dashboard field
number in DUNS number
Duns 5. Search for that empty DUNs field from BOOMi for EDI then
number numberCustomer using delivery it should show
in DUNS ticket number "InvalidCustomer" error
number 6. Click on that DebitDN and message on DUNS number
filed) observe field
Customer DUNS number - Invalid Product
32216 valid data
DUNS
(It should - code 3.
Product
Magento to willthat particuar
recevice EDI DT
810
accept
code - dashboard
file from page
BOOMI for Invalid
01707
incase of 4. Click on DN Debit(Open) link
07756728 Product
Verify Rule No 12 - Invalid Product If user reveives validCustomer
valid
3030 under My DT dashboard
DT
Duns
Customer- A6 2. (DN
5.
Launch
Debit)for
Search
site and Login
from
thatBOOMi for with
validCustomer EDI DUNS number in DUNS
(It should valid DUNS data
number - Product code field number field from BOOMi for
number
DUNS
not - using
3. emptydelivery ticket number
Navigate to that particuar DT
in DUNS is
24472631
accept /DUNS
dashboard Numberpage EDI then it should not show
Product
number
05644 1.
6. Magento
Click on will
that recevice
DebitDN EDI
and 810 any error message on DUNS
incase
code - of 4. fileClick
from onBOOMI
DN Debit(Open) link
filed) observe
DT - A3 under My dashboard
invalid number field
Empty
Product 2. Launch
Verify Rule DT
No site
13 and
- by Login
receivingwith If user receives Invalid
Product
(It should 5. Search for that Invalid Product Product code in Product code
code
code -in valid Invalid
using
data
Productticket
delivery (DN Debit)
number from field from BOOMI for EDI then
not
BOOMi to that particuar
for EDI DT
product
accept /DUNS
dashboard Numberpage the it should show "Invalid
2204
code 1.
6. Magento
Click on will
that recevice
filtered EDI
DebitDN 810
incase
Valid of Verify
4.
fileClick
from
Rule No Debit(Open)
onBOOMI
DN 14 -No delivery
for valid linkdate product " error message on
Product
field)
empty and observe
(DN Debit) from BOOMi for EDI product code field.
Product under 2.
Delivery
My DT
Launch dashboard
date site
- if and Login
delivery datewithfield
Product
code 5. Search
valid datafor that empty Product If user reveives empty in
code in is empty
code using delivery ticket DT product code field from
(It should 3.
Customer 1. Navigate
Magento to
willthat particuar
recevice EDI 810 BOOMi for EDI then it should
product
accept number /DUNS Number
DUNS
code - dashboard
fileClick
from BOOMI page for no delivery
Customer
incase
24472631 of 6. 4.
dateClick on
on that filtered DebitDN
DN Debit(Open) link show "Invalid product" error
field)
DUNS
valid and observe
- under My dashboard message product code field.
02456
24472631 2. Launch DT site and Login with If user receives valid Product
Product
DT - A3 5. Search
valid data for that valid Product code in Product code field
02456
code in Verify
using Rule Noticket
delivery 14 - Delivery
number date from BOOMI for EDI then it
Delivery
DT - A3 3. (DN Navigate
Debit) to that
from particuar
BOOMi DT
for EDI
product
date field /DUNS
dashboard Numberpage should not show any error
Delivery
code 1.
6. Magento
Click on willfiltered
that receviceDebitDN
EDI 810 message on product code
-dateEmptyfield 4. fileClick
from onBOOMI
DN Debit(Open) link
field)
(It should and
Verify
under observe
Rule
My No 15for
dashboard
delivery
- No line itemdate field.
If user receive the form
- 2.
(DN Launch
Debit)forDT site
from and
BOOMi Login with
for EDI
not
Customer
(MM/DD/ valid 5. Search
data that no delivery date without any delivery date
accept
DUNS - if Product
using Code -ticket
delivery if product
number code from BOOMi for EDI then it
YYYY)
Customer 3. Navigate
field is epmpty to that particuar DT
delivery
24472631
(It should /DUNS
dashboard Numberpage should show "no delivery
Customer
DUNS
date -
field 1.
6. Magento
Click on will
that recevice
DebitDN EDI
and 810 date" error message on
05608
accep
DUNS if
- 4. Click onBOOMI
DN Debit(Open) link
24472631
is
DT empty)
- A3 Verify file from
observe Rule for No
No 15 - No line item line item delivery date field.
delivery
24472631
05608 under
2. My DT
Launch dashboard
siteBOOMiand Login with
Delivery
date
01707 field 5. (DN Debit)
Search from
for that delivery date for EDI If user receive the form with
DT
date - A3
- DT valid Product dataCode -ticketif product code
is has
Product using
3. delivery
Navigate to that number
particuar DT any valid delivery date from
08/30/20
valid
-Customer
A6 field
/DUNS
Verify isRule
has
Numberany
No products
16 -Product not BOOMi for EDI then it should
Code
22 - dashboard
1. Magento page
dalivery
Product 6. Click on that DebitDN and linkfor not show any error message
Empty
DUNS
(MM/DD/
Customer
date) - listed(DN
4.
fileClick
from
observe
Debit)
onBOOMI from BOOMi
DN Debit(Open)
for line items on delivery date field
code
(It -
should EDI
under My DT dashboard
69556810
YYYY)
DUNS
07756700 - 2. Launch
Product code site
- if and Login
Product is with If user receive the form
not
not
40307
Product 5. Search
valid datatoforthat
that No line item without any line items from
84734000
2887
accept if mapped
using delivery Customer
ticket number BOOMi for EDI then user
DT
Code - A6- 3. Navigate to
10001
(It should
product
Delivery 1. Magento
/DUNS Number willthat particuar
recevice EDI DT
810 should show " Product line
07756700
DT
not - A8 dashboard page for Product not
code
date
2228
Delivery-field file6. fromonBOOMI
Click
Verify
4. on that
ClickRule DebitDN
No Debit(Open)
DN 16 -Product andnot
link items are missing "error
accept
is empty
(MM/DD/ ) listed
observe from BOOMi for message
(It
date
incase - of listed(DN
should under
2. My Debit)
Launch dashboard
YYYY)
accept
(MM/DD/ if 5.EDI Search for that line items using If user receive the form
product
Product valid
Product datacode -number
if Product are
product
YYYY)
code is delivery
Verify
3. Navigateticket
Rule No 17
to that /DUNS
-Quantity
particuar DT without any line items from
code
code
Product -
field mapped
Number
exceeds to
box the Customer
Threshold - requires BOOMi for EDI then user
not exist dashboard
07585600 1. Magento page
is has
code -
in any 6. Click on
verification
4. Click that
onBOOMI
DN(DN DebitDN and
Debit) fromlink
Debit(Open) should not showproduct
If user receives any error
code
1600
products)
07756700 file
BOOMifrom
observe fordashboard
EDI message.
system/N
(It should 2. under My
Launch DT site and Loginmore with that is not mapped to the
1238
ot GopuffCustomers
5. Search for that -Product
eaches not retailer in the product code
accept
(Eaches valid
than data
5using
boxesdelivery ticket
mapped
incase listed field, from BOOMI for EDI
perthat
to Boxof- 3. 1. Navigate
Magento
number /DUNS
to
willthat particuar
recevice
Number EDI DT
810 then it should show “Product
product
6) dashboard
fileClick
from BOOMI page for Quantity
Customer
code is - 6. 4. Click on
on that DebitDN andlink
DNThreshold
Debit(Open) not listed” error message on
Eaches
)exist in exceeds
observe box product code field.
36 under
site and Login with If user receives product code
system/m
(GopuffCu 5. Search
valid datafor that Product is listed that is mapped to that retailer
apped to using
stomers - 3. Navigate delivery to ticket number DT
that particuar in the product code field from
that /DUNS
It should dashboard page Number BOOMI for EDI then it should
Customer
not 6. Click on that DebitDN
4. Click on DN Debit(Open) link and not show
If user any error
receives message
recives more
)accept in observeunder My dashboard on product code
than 5 boxes for field.
case of 5. Search for that Quantity exceeds GopuffCustomers from
eaches box using delivery ticket BOOMI for EDI then it should
more number /DUNS Number show "Quantity exceeds box
than 5 6. Click on that DebitDN and Threshold " error message in
box's) observe eaches box.
(Eaches
Delivery Food Service migration - It should
(GopuffCu
per Box valid data
date
stomers - - be -
3.
5 box's
Verify Rule No
Navigate to 17 -Quantity
that particuar
24)
(MM/DD/ 1. Magento
exceeds box will recevice
Threshold EDI DT810
- requires
It should
Eaches - dashboard
file from page
BOOMI for Quantity
YYYY)
accept in verification
4. Click on DN(DN Debit) fromlink
Debit(Open)
144
Product exceeds
BOOMi box
for Threshold
EDI
case
Customer
(It of
should under My dashboard with If user receives recives less
code
eaches
DUNS - - 2. 5.
Launch
Food
Search
DT migration
Service
for
site and Login
that Quantity - It should
exceeds than or equals 5 boxes for
not
07756700 valid
be data
5using
box's
are
21339648
accept 5 box
in 3. Navigate delivery
to ticket GopuffCustomers from
2228
box's
02300 or 1. Magento
number /DUNSwillthat particuar
recevice
Number EDI DT810 BOOMI for EDI then it should
case
(Eaches of dashboard
file fromonBOOMI page for Quantity
less
DT
Food - than
A8 6. Click
Verify
4. ClickRule
on that DebitDN
No Debit(Open)
DN 17 -Quantity andlink not show any error message
per
5 Box
boxs)
Delivery under - exceeds
observe
exceeds box Threshold
Threshold - requires in eaches box.
Service
24) 2. Launch Myboxdashboard
DT siteDebit)
and Login with If user receives recives more
date
migration - verification (DN from
Eaches
(MM/DD/ - 5. Search
valid data for that Quantity exceeds than 5 boxes for Food Service
-120eaches BOOMi box
3.
fordelivery
EDI
Navigate to thatticket
using migration from BOOMI for EDI
YYYY)
more NormalCustomers
number /DUNS -particuar
Numberit should DT then it should show "Quantity
(It should dashboard
Product accept any page
value
than
accept 5 6. Click
Verify on
Rule that DebitDN
No Debit(Open)
1 -Customer linkand PO exceeds box Threshold " error
code
box's) - in 4. 1. Click
Magento
observe
on DN will recevice EDI 810 message in eaches
case
07684010 of does not
under
file from
meet
MyBOOMI pattern (DN
dashboard If user receives lessbox.
than or
Food Credit)for
5. Search EDI
for file
that from
Quantity BOOMI.
exceeds equals 5 boxes for Food
0040(Eac
Customer 2. Launch DT site and
GopuffCustomers- PO Login
should with
starts Service migration from
Service
hes per box
valid using
data delivery ticket
Banner
migration - with
number
Verify GUS /DUNS
Rule No Number
1 -Customer PO BOOMI for EDI then it should
Box -6) 3. Navigate to that particuar DT
-Go Puff
eaches
Eaches
1.
6.
- does
Magento
Click on
not meet
dashboard
will
that recevice
DebitDN
pagepattern (DNEDI
and 810 not show any error message
Customer
is 5 box's) file from
observe BOOMI for Go
Customer 4.
120
DUNS
Credit)for
Click on EDI
- - puffCustomers DN file from BOOMI
Debit(Open)
havingCustomer link PO in eaches box.
Banner
NormalCu interface
under My data
dashboard
05749904
Go Puff - starting with
GopuffCustomers- GUS and 6 char PO If user receives eaches in
if Customer
stomers
90069 5.
2. Search
Verify
Launch Ruleusing
No
DT site1delivery
-Customer
andGUS ticket
Login with more than or less than 5
PO
Customer
it should does
number not starts with
DT
DUNS - BK- valid does
1. data will recevice EDI 810 boxes from BOOMI for EDI
not
Magento
/DUNS
meet Number
pattern (DN
accept
PO - 6.
3. Click
Credit)for
Navigateon EDI
that DebitDN
to file
that from and DT
BOOMI
particuar then should show any error
ForCusto
05749904
any value file from
observe BOOMI for Go
Should
mer
90102
interface data
dashboard
puffCustomers pagehavingCustomer PO message. It should not show any error
Customer
start
Banner with - AEFIS(Banner
4. Click on DN group)Customers
Credit (Open) link- message inCustomer PO field
DT - BK - not
Banner startingstarts
with with
GUS VONand 6 char
GUS
AFEES
PO - and PO under
2.
should
Verify
Launch My DT
Rule dashboard
Nosite
1 -Customer
and Login PO if we receive vaildCustomer
AFEES
have 6 1.
5. Magento
Search
does not for
meetwill
thatrecevice
Customer
pattern (DNEDIwith
810 PO number from BOOMI for
PO
Should
Customer valid
file dataBOOMI for AEFIS(Banner
from
digits(GU
have 6- number
Distributo Credit)for
3. Navigate using
EDI delivery
to file
thatfrom ticket
BOOMI
particuar DT EDI
DUNS
S897654) group)Customers
number
r - A3 but dashboard /DUNS
interface data havingCustomer
Number
digits
69556810 PO starting page
with VON and 9 char-
Customer
should AEFIS(Banner
4. Click onDT group)Customers
DNsite
Credit(Open) link It should show a "Customer
32216
DUNS - PO 2. Launch
should starts withand Login
VON with PO does not meet pattern."
not
DT start
- A3 valid under My dashboard
data will recevice EDI 810
69556810
with 1.
5. Magento
Search RuleforNo
PO
32216- Verify
3. Navigate
file from tothat
BOOMI
1 - Customer
that ForCustomer
forparticuar
AEFIS(Banner
PO
DT error message inCustomer PO
'GUS'(SU
Should number
groups
dashboard using
thatpage delivery
dont have any PO ticket field if we receive invaild
Delivery
G987654) group)Customers
number
pattern /DUNS
forDN havingCustomer
Number
EDI(Open)
file from pattern from BOOMI for EDI
start
Date with
- 08- 4. PO Click on
starting with VON and linkBOOMI
under
9 char
ForCusto
'VON' and My interface data
dashboard It should not show any error
10-2022
mer 2. Launch
NormalCustomersDT site and - it Login
shouldwith
have
PO 9
- - valid 5. Search
data for that Customer PO message inCustomer PO field
Banner
char(VON accept
number with/without
using delivery any data
ticket if we receive vaildCustomer
Should
Family 3. Navigate to
inCustomer PO that
field particuar DT
87654323
not number
start Verify
dashboard /DUNS
Rule page Number
No 2 -Customer PO PO number from BOOMI for
Dollar
4) 1.
6. Magento
Click
larger on
than will
that
maximumrecevice
DN and EDI
observe
length for 810 EDI
with 4. Click
file from onBOOMI
DN (Open) link under
Customer
'VON' EDI file from BOOMI interface data
DT - BKand
Banner
MyLaunch
- 2.
dashboardDT site and
GopuffCustomers- Login with
IfCustomer
It should show a "Customer
PO PO does not meet pattern."
have
Customer9 5. Search for that Customer PO
Go Puff valid
char(NOV has
number
data
less than
using 6delivery
char ticket error message inCustomer PO
DUNS
Customer - 3.
1. Navigate
Magento to
willthat particuar
recevice EDI DT
810
76545675
Customer
24472631 number
Verify
dashboard /DUNS
Rule page Number
No 2 -Customer PO field if we receive invaild
DUNS
4) - file
6. from
Click on BOOMI
that DNfor Go
and observe
Banner - 4.
12614
05749904
larger
Clickthan
on DN
puffCustomers
maximum
Credit length for
(Open)
havingCustomer link PO pattern from BOOMI for EDI
Go
PO Puff
- With underEDI file from BOOMI
My6dashboard interface data
90102
Customer less than
GopuffCustomers- char IfCustomer PO
any
DT - value
BK- 5. 2. Search
Launch for
DT that
site Customer
and Login withPO
DUNS
or has
numbermoreusingthan 6 char
delivery ticket
PO -
05749904 valid data will recevice EDI 810
1. Magento
without
Should number
3. Navigate /DUNS Number
to that particuar DT It should not show any error
90102
value file
6. from
Click on BOOMI
that forand
Go observe
start
DT - BK with dashboard
puffCustomers pagehavingCustomer PO message inCustomer PO field.
DN
'GUS'
PO - but 4. Clickthan
more on DN Credit(Open) link
6 char It should show a "Customer
have
Should less under
2. Launch DT site and Login with PO smaller than length."
My dashboard
than
start with 5.
6 Search
valid datafor that Customer PO error message inCustomer PO
digits(GU number using delivery
GUS but 3. Navigate to that particuar DT ticket field if we receive invaild
S7654)
have number /DUNS
dashboard page Number pattern
It shouldfrom
showBOOMI for EDI
a "Customer
more 4. Click on DN Credit(Open) link PO larger than maximum
than 6 under My dashboard length" error message
digits(GU 5. Search for that Customer PO inCustomer PO field if we
S9875432 number using delivery ticket receive invaild pattern from
4) number /DUNS Number BOOMI for EDI
AFEES Customer PO length is more than 9
63710
Customer 2.
charLaunch DT site and Login with
DT - A3- Verify
valid Rule No 1 -Customer PO
data.
DUNS 1.
doesMagento
not meetwillpattern
recevice (DNEDI 810
PO -
69556810 3.
fileNavigate
from to that
BOOMI for particuar
AEFIS(Banner DT
Should Credit)for
dashboard EDI
page file from BOOMI
63710 group)Customers
interface data havingCustomer
start
DT - A8with 4.
PO Click
withon DNthan
less (Open) link under
9ifchar.. It should show a "Customer
'VON' GopuffCustomers- Customer PO PO smaller than required
PO - and My
2.
is
dashboard
empty
have
Should less 5. Search
Verify
valid RuleforNothat
data. Customer PO
1 -Customer PO length" error message
than 9 1. Magento
number
does not using
meetwilldelivery
recevice
pattern EDI 810 inCustomer PO field if we
ticket
(DN
start with 3.
fileNavigate
from/DUNS to that
BOOMI for particuar
GoBOOMI DT
char(VON
'VON' and number
Credit)for
dashboard EDI
page Number
file from receive invaild pattern from
9876545) puffCustomers
6. Click on that havingCustomer
DN and observe PO BOOMI
have
Customer
interface
4. Click ondata
empty DN (Open) link under It shouldfor EDI a "Customer
show
more AEFIS(Banner
My dashboard group)Customers - if
Banner - 2. Launch
Customer DT site
fieldand
POthat Login with PO larger than maximum
is empty
than
Go Puff9 5. Search
valid data will recevice EDIPO
for Customer length" error message
char(VON 1. Magento
number
Verify using
Rule No delivery
1 - ticket
ForCustomer 810 inCustomer PO field if we
Customer 3.
fileNavigate
fromthat to that
BOOMI for particuar
AEFIS(Banner DT
67434678
DUNS - number
groups
dashboard /DUNSdontNumber
page have any PO receive invaild pattern from
9) group)Customers
6. Click
pattern on that
forDN DN
EDICredit havingCustomer
and
file from observe
BOOMI BOOMI for EDI
05749904
Customer 4.
PO Click
fieldonasdata
empty. (Open) link
Customer
90069 interface
under My DTdashboard It should show a "Customer
Banner
Banner - 2. Launch site and - it Login
shouldwith
DT - BK -
AFEES
NormalCustomers
5. Search
valid data for that Customer PO PO required." error message
Family
PO - accept
number with/without
using delivery any data
ticket inCustomer PO field if we
Customer
Dollar 3. Navigate to
inCustomer PO that
field particuar DT
Should
DUNS - be number
Verify
dashboard /DUNS
No 5 - Delivery date in receive empty PO from
Rule page Number
Customer
empty
Delivery 1.
6. Magento
Click
theClick on
future willCredit)for
that
(DN DNrecevice
andlink EDI
observe
EDI 810
file BOOMI for EDI for go puff
69556810
DUNS - 4.
file from onBOOMI
DN (Open) under
date
63710 from
My BOOMI
dashboard interface data
24472631
(MM-DD- 2. Launch
Delivery DT site
date - Futureand Login
Deliverywith It should show a "Customer
DT - A3
12614 5. Search
valid data for that Customer PO PO required" error message
Dalivery
YYYY)
PO date
DT
date-- BK
- be
Customer
number
3.
1. Navigate
Magento
usingto
will
delivery
that ticket
particuar
recevice EDI DT
810
inCustomer PO field if we
should number
Verify
dashboard /DUNS
Rule page Number
MM-DD-
DUNS
empty - file
6. from
Click onBOOMI
that DN foranddelivery
observe date
Delivery
YYYY(Syst theClick
4. future
onDT(DN
DNsite Credit)for
Credit (Open) file BOOMI for EDI.
EDIlink
84734000
date - 2.
fromLaunch
BOOMI interfaceand Login
data with
em
10001 under
Verify
valid My dashboard
Rule
data No 6 - Delivery date
MM-DD- PO- Delivery
5. Search date
for - it shoulddays accept less It should not show any error
should
DT
YYYY- A8 less
3.
than
than
Navigate
or equal tothat
allowable
tothat Customer
particuar
system date
PO
of current
DT
.
any
not data/
Delivery number
date using delivery
(DN Credit)for
dashboard page ticket
EDI file from message inCustomer PO field.
Customer
without
accept 1. Magento
number
BOOMI /DUNSwill
interface recevice
Number
data EDI 810 Customer PO will be same as
date
DUNS --it 4.
fileClick
from on DN Credit(Open)
BOOMI for delivery link
date It should show a "Delivery
data
the older
Should 6. Click
Delivery
under on that
Mydate DN and observe DN ticket number
- if Delivery date is date should not be greater
dashboard
84734000
than 90 2. Launch
older than DT
90 site
days and
fromLogin with
current
not
10001 5. Search
Verify
valid Rule
data for
No that
6 - delivery
Delivery date
date than system date.' error
days
accept from date.
using
less delivery
than ticket
allowable number
days of current message in Delivery date field
DT - A8
current 3.
1. Navigate
Magento to
willthat particuar
recevice DT
EDIfrom
810 if we receive any future date
future
Delivery /DUNS
date (DN
dashboard Number
Credit)for EDI file
page for older than 90
date)
delivery file
6. fromon
Click
BOOMI BOOMI
that
interface filtered
data Credit DN as delivery date from BOOMI
date
Customer- it 4.
daysClick
as on DN Credit(Open)
delivery date link
dates.
Delivery
Should and observe
Delivery
under Mydate - if Delivery date is in for EDI
dashboard
DUNS
date -- 2. Launch
between 90DT site and Login with
accept
84734000 5. Search
valid data for that from
days deliverycurrent
date
MM-DD-
old 90 date.
using delivery ticketparticuar
number It should not show any error
10001
YYYY 3.
1. Navigate
Magento to
willthatrecevice EDI DT 810 message in Delivery date field
days
DT from
- A8 /DUNS
dashboard Number
page for between 90 It should show a "Delivery
Customer
current file
6. from
Click onBOOMI
that 7filtered Credit DN if we less
receive
Delivery
DUNS -
Verify
4.
daysClick Rule No Credit(Open)
on current
from DN - Delivery
date.
ticket
link date thanvalid delivery
allowable days
date.
date - it and observe
no missing
under My (DN Credit)from BOOMi of current date " errorEDI
dashboard date from BOOMI for
84734000 2.
for Launch
EDI for DT site and Login with
Should
10001 5. Search
valid data that delivery date message in delivery date field
not Delivery
using ticketticket
delivery number - if Delivery If user receive delivery date
number
DT - A8 3. Navigate
ticket number to that
field particuar
is empty DT
accept
Delivery /DUNS
dashboard Number
page older than 90 days from
less 1. Click
Magento willfiltered
receviceCreditEDI 810
datethan- it 6.
4.
fileClick
from
on that
onBOOMI
DN Credit(Open)
for empty linkDN
delivery
current date from BOOMI for
start
Should date and observe
Verify Rule
under No 7 - Delivery ticket EDI
My dashboard
date
no missing (DN Credit)from BOOMi
accept
Customer 5.
2. Search
Launch for
DT that
site and delivery
Logindatewith
old 90 - for
usingEDI delivery ticket number It should not show any error
DUNS valid
Deliverydataticket number - if Credit message in Delivery date field
days from
84734000 /DUNS
3. Number
Customer
current DNNavigate
6. has on
Click
to that particuar
thethat
Delivery
filtered ticket DT
number
Credit DN if we receive valid delivery
10001
DUNS - dashboard
1. Magento page
will recevice EDI 810 date from BOOMI for EDI
date.
DT - BK and
4. observe
84734000 fileClick
fromonBOOMI
DN Credit(Open) link If user receive empty delivery
Delivery
10001 under
2. Launch DT site and Login with ticket number from BOOMI
My dashboard
ticket
DT - BK 5. Search
valid datafor that empty delivery for EDI then it should show
number
Delivery - ticket using to
3. Navigate DUNS thatNumber
particuar DT "Delivery ticket no missing"
Should
ticket be 6. Click on
dashboard page that filtered Credit DN error message in Delivery
empty
number - and observe
4. Click on DN Credit(Open) link ticket field.
Should under My dashboard If user receive delivery ticket
have 5. Search for that delivery ticket number from BOOMI for EDI
delivery using DUNS Number then it should not show any
ticket 6. Click on that filtered Credit DN error message in Delivery
number and observe ticket field.
BOOMi for EDI
DuplicateCustomer PO (DN DT
3.
1. Navigate
Magento to
willthat particuar
recevice EDI 810
Credit)for
Customer dashboard sameCustomer
page for from
file from BOOMI
DUNS - BOOMi 4. forDN
Click on EDICredit(Open) link
DuplicateCustomer PO be
84734000 Customer
under
2. My
Launch
PO - It should
dashboard
DT site and Login with If user receive any
10001 UniqueCustomer
5. Search for that PO for existingCustomer PO number
valid data
DT - BK sameCustomer.
DuplicateCustomer
3. Navigate to PO using from BOOMi for EDI
Customer 1. Magento
delivery willthat
ticket number
particuar
recevice EDI DT
/DUNS 810 for sameCustomer then it
Customer dashboard
file from page for
BOOMI
PO -
DUNS - 4. Number
Verify Rule No 9 -by
Click on DN Credit(Open) receving link should show
GUS2233 DuplicateCustomer
6. Click on that PO
filtered Credit DN "DuplicateCustomer PO" error
84734000 Duplicate
under
2. My delivery
Launch dashboard
DT site
ticket no (DN
and Login with
32
10001 and observe
Credit)from
5. Search forBOOMi
that for EDI message
If user receive any PO field
inCustomer
Customer valid
Deliverydataticket number - Existed
DT - BK DuplicateCustomer PO using DT existingCustomer PO number
DUNS
Customer- 3. Navigate
delivery
delivery
to that
ticket
ticket number
number
particuar
/DUNS from BOOMi for EDI for
69556810 dashboard
1. Magentopage will recevice EDI 810 differentCustomer then it
PO -
Customer Number
4.
32216
GUS7053 fileClick
fromon DN Credit(Open)
onBOOMI for existed link
DUNS
DT - A6- 6. Click
under
delivery My that filtered
dashboard
ticket number
Credit DN should not show any error
32
84734000 and Verify
5. observe
RuleforNothat
Search 9 - by receving message inCustomer PO field
2. Launch
delivery and Login
no with If user receive any
(DN
valid data BOOMi PO using uniqueCustomer PO number
Customer
DT - BK Credit)from
delivery ticket number for /DUNS
EDI from BOOMi for EDI for
DUNS
Customer- 3. 1. Navigate
Magento
Number
Verify Rule
to
willthat
No 10
particuar
recevice
-by EDI DT
receving 810 existedCustomer then it
Delivery
69556810 dashboard
file from BOOMI page for delivery ticket If user receives any existed
PO -
Customer
ticket 6. Click
Click on
Duplicate
4. that
onLine filtered Credit
Item(DN
DN Credit(Open) DN should
link deliverynot show
ticket any error
number from
32216
GUS705
DUNS number
and
- under observe
Credit)from BOOMi for EDI message inCustomer PO field
number-
DT - A6 2. My
Launchcode dashboard
DT site andproduct
Login with BOOMi for EDI in delivery
69556810
same Product
5. Search - Same
for that delivery ticket as ticket field then it should
32216 valid
2nd data
line item
existing number using delivery ticket shows a "Delivery ticket
DT - A6 3.
delivery 1. Navigate
Magento
number /DUNS
to
willthat particuar
recevice EDI DT
810
Verify
dashboard
file from
Rule page for Duplicate Line number already used" error
No
BOOMI
10 Number
- Duplicate Line
ticket 6.
Delivery Item(DN
4. Click on that
Click onCredit)from filtered
DN Credit(Open) Credit
BOOMi DN message in Delivery ticket
for
link
number Item
and observe
EDI My dashboard number field. any unique
ticket
product under
2. Launchcode DT site and Login with If user receives
Customer
number- Product
5. Search - Should not be Same
for that delivery ticket no delivery ticket number from
code-
DUNS - valid
product dataas 2ndticketline item
unique
07585600 using
3. delivery
Navigate to number DT BOOMi for EDI in delivery
69556810
delivery 1. Magento
/DUNS Number willthat particuar
recevice EDI 810 ticket field then it shouldn't
1600
32216 dashboard
file from page
BOOMI
ticket 6. Click
Verify
4. Click on
Rule
onDTthat filtered
No Credit(Open)
DN 12 - Credit DN show
link If userany errorsame
receives message in
product
DT -
numberA6 2.
and Launch
observe
InvalidCustomer(DN site and Login with delivery ticket number field.
again under
valid My dashboardCredit)from code as 2nd line item from
data
same BOOMi
5. Search forfor
EDI
3.
DUNSNavigate
number tothat
that Duplicate
particuarLine
- InvalidCustomer DT BOOMi for EDI in product
product
product Item using
dashboard delivery
page ticket code field then it show a
Customer
code- DUNS
number number
/DUNS Number "Duplicate Line Item" error
code
DUNS1-- 4. 1. Click
Magentoon DN willCredit(Open)
recevice EDIlink
810
07585600
07585600 6. Click
Verify
under on
Rule that
MyBOOMINo 12 -
dashboardfiltered Credit DN message on product code
24472631
1600 file
and from
observe
InvalidCustomer(DN for Credit)from field
1600
01788 5. Search for thatDUNS
InvalidCustomer Duplicate
numberLine If user receives different diff
BOOMi
Item(Shouldfor EDI
not be Same product
2.
DUNSLaunch
numberDT site and Login
- DUNS number with line item from BOOMi for EDI
product
DT as 2nd
- A6 valid isdata line item) using delivery in product code field then it
Customer
code 2- fieldticket empty /DUNS Number
number should not show any error
DUNS - 3.
07756788 1.
6.
Navigate
Magento
Click
Verify on
to
will
that
Rule page
that
No 12 -
particuar
recevice
filtered EDI
Credit
DT
810
DN
If user reveives
message on product code
24472631 dashboard
file from BOOMI InvalidCustomer DUNS
3261 and
4. observe
InvalidCustomer(DN
Click onDTDNsite Credit)from
Credit(Open) link field
01707 2. Launch
BOOMi EDI and Login with field from BOOMi for EDI then
fordashboard
DUNS under
valid My
data
number DUNS number - ValidCustomer
DT - A6 - 5. 3. Search
Navigate fortothat
thatInvalidCustomer
particuar DT it should show
24472631 DUNSusing
dashboard
number
deliverypage ticket number "InvalidCustomer"
01788 1.
6. Magento
Click
Verify on will
that recevice
filtered EDI
Credit 810
DN message on DUNS number
Customer 4. fileClickRule No Credit(Open)
onBOOMI
DN 14 -No delivery linkdate emptyCustomer DUNS
DUNS (DNfrom
and
under observe
Credit)from
My dashboard
for validCustomer
BOOMi for EDI field
DUNS - 2. Launchdate
Delivery DT site
- if and Login
delivery with
date field
number - 5.
24472631 valid Search
data for that empty DUNs field from BOOMi for EDI then
DUNS is empty
numberCustomer using delivery it should show
01707 3. Navigate to
willthat particuar
EDI DT
number 1. Magento
ticket
dashboardnumber recevice
page for no delivery
810 "InvalidCustomer" error
field is fileClick
6. from BOOMI
DT - A6 4.
dateClick on
on that filtered Credit
DN Credit(Open) DN message on DUNS number
link
empty and observe field
Customer under
site and Login with If user reveives validCustomer
DUNS - 5. Search
valid datafor that validCustomer DUNS number in DUNS
DUNS using
24472631 3. Navigate delivery to ticket number DT
that particuar number field from BOOMi for
number
01707 - /DUNS Number
dashboard page EDI then it should not show
69556810 6. Click on that filtered
DT - 4. Click on DN Credit(Open) link Credit DN any error message on DUNS
32216
A6 and observe
under My dashboard number field the form
If user receive
Delivery 5. Search for that no delivery date without any delivery date
date - if using delivery ticket number from BOOMi for EDI then it
delivery /DUNS Number should show "no delivery
date field 6. Click on that filtered Credit DN date" error message on
is empty and observe delivery date field.
(DN Credit)from BOOMi for EDI
DT valid
Product data Code - if product code
- A6 3. Navigate
field is epmpty to that particuar DT
Delivery dashboard page
1. Magento will recevice EDI 810
date - if 4. Click
file from onBOOMI
DN Credit(Open) link
delivery Verify
under Rule
My No 15for
dashboard - No Noline lineitemitem
Customer 2. (DNLaunch DT
Credit)from site and Login with
date
DUNSfield - 5. Search
valid data for thatBOOMidelivery fordateEDI If user receive the form with
is has Product
using
Verify RuleCode
delivery NO - if
ticket
19 product
- number
Total code
quantity any valid delivery date from
field is has to that
any particuar DT
products
valid
Customer
01707 /DUNS
exceeds
dashboard Number
total
pageeaches threshold - BOOMi for EDI then it should
delivery
DUNS -DT 4. 1.
6. Magento
Click
Requires on will
that recevice
filtered EDI
Credit 810
DN not show any error message
Click
file from onBOOMI
DN Credit(Open)
for line items link
date
-24472631
A6 and observe
Verification
under My DT (DN Credit) from
dashboard on delivery date field
01707 2. Launch
BOOMi for EDIsite and Login with If user receive the form
Product
Customer
Customer 5. Search for that No line item without any line items from
Code
DUNS -- DT valid
if Eaches
using
data
- more ticket
delivery than 50 eaches
number BOOMi for EDI then user
DUNS A6 - 3.
-24472631 1. Navigate
Magento to
willthat particuar
recevice EDI DT
810 should show " Product line
product /DUNS
Verify
24472631 dashboard Number
Rule NO 19 - Total
page for exceeds total quantity
code
01707field 6. file from total
Click BOOMI
01707 4. Click on
exceeds
eaches on that filtered
DNeaches
Credit(Open) Credit
threshold DN
link - items are missing "error
is empty and
DT under
DT observe
Requires My DT dashboard message
Product
-- A6 2. Launch
Verification siteCredit)
(DN and Login from with
A6 -
Code 5. Search
valid data for that line items using If user receive the form
Product BOOMi
delivery for EDInumber /DUNS
ticket
Eaches - Lesstothan
thator particuar
equals to DT50 without any line items from
Code
2181 - Number BOOMi for EDI then user
Product dashboard
07756700 eaches
6. Click
Verify on
Rule
page
that filtered
No credit(Open)
1 -Customer linkCredit PO DN
If user receives
should not show
eaches
any
more
error
Code - 4.
1. Click
Magento on DN will recevice EDI 810 than 50 from BOOMi for EDI
2181 and
doesobserve
under not
My meet pattern (DN Debit) message.
dashboard then it should show "The total
07756700 file for from BOOMI
Flatfile from MuleSoft .total
2181 5. Search for that exceeds quantity exceeds the
Customer 2. Launch DT site and
GopuffCustomers-
eaches using delivery
Login
POticket
should withstarts allowable quantity of 50
valid
Banner - number
with data
GUS
Eaches- Verify /DUNS
Rule No Number
1 -Customer PO eaches. Do you eaches
want tomore
Go Puff 3.
More 1.
6.
Navigate
Magento
Click on
does not meet
to
will
that
that particuar
recevice
filtered Flat DT
file If user receives
(DN Debit) than 50 from BOOMithe
Credit DN approve and submit
Customer dashboard
from MuleSoft pagepattern
for Go for EDI
than 50
Customer 4. and observe
forClick
Flat on
fileDNfrom MuleSoft link
credit(Open) form?"
then it error message
should show "The total
DUNS
Banner - - puffCustomers
interface data havingCustomer PO
Eaches-
05749904 under My dashboard
starting with GUS and 6 char PO quantity exceeds the
Go
Less Puff
than GopuffCustomers-
5. SearchRuleusing if Customer
1delivery ticket
90069
Customer
Verify
2. Launch
does not
Nosite
DT
starts
-Customer
withand GUSLogin with allowable quantity of 50
PO
50
DT or number
does
- BK- valid /DUNS Number
data will recevice Flat for
not meet pattern (DN ) eaches. Do you want to
ForCusto
DUNS
equal to 1.
6. Magento
Click on that filtered Credit file
DN approve and submit the
PO
mer - Flat
3. file fromtoMuleSoft
Navigate that interface
particuar DT
05749904
50 from
and MuleSoft
observe for Go
Should data
Banner - dashboard
90102 puffCustomers pagehavingCustomer PO form?" It shoulderror
not message
show any error
Customer
start
AFEES with AEFIS(Banner
4. Click on DN group)Customers
Debit (Open) link - message inCustomer PO field
DT - BK - not
Banner PO startingstarts
should with withGUS VON and 6 char
GUS
PO - and under
Verify
2. LaunchMy
Rule dashboard
No 1 -Customer
DT siterecevice
and Login PO if we receive vaildCustomer
AFEES
have 6
Distributo 1.
5. Magento
Search
does forwill
not meet that Customer
pattern (DN Flat)with
POfile PO number from MuleSoft for
for
Should
Customer valid
from data
MuleSoft for AEFIS(Banner
digits(GU
r - A36
have number
Flat
3. using delivery
file fromtoMuleSoft
Navigate ticket
interface
thathavingCustomer
particuar DT Flat file
DUNS
S876543)
Customer - group)Customers
number
data /DUNS Number
digits
69556810 but dashboard
starting page VON and 9 char- It should show a "Customer
DUNS
should - PO AEFIS(Banner
4. Click on DN
with
group)Customers
Debit(Open) link PO does not meet pattern."
32216
69556810 2.
PO Launch
should DT sitewith
starts and Login
VON with error message inCustomer PO
not
DT start under
- A3 valid My dashboard
data will recevice Flat file
32216
with 1.
5. Magento
SearchRuleforNo
PO - Verify
3.
Delivery number Navigate
from MuleSoft tothat
1 - Customer
that
for particuarPO
ForCustomer
AEFIS(Banner DT field if we receive invaild
'GUS'(SU
Should using
groups thatpage
dashboard delivery
dont have any PO ticket pattern from MuleSoft for Flat
Date(MM
G865432) group)Customers
number
pattern /DUNS
forDN havingCustomer
Number
Flat(Open)
file from file
start
/DD/YYYYwith 4.
PO Click on
starting with VON and linkMuleSoft
under
9 char
'VON' interface
and My dashboarddata It should not show any error
)ForCusto 2. Launch
NormalCustomers DT site and - it Login
shouldwith
have
PO 9 5. Search for that Customer PO message inCustomer PO field
mer-
char(VON
valid
accept
number
Verify
data
with/without
Ruleusing
No delivery
2 any
-Customer data
ticket PO if we receive vaildCustomer
Should
Banner - 3. Navigate to
inCustomer PO that
field particuar DT
76344523
not number /DUNS
larger than page
start dashboard Number
maximum length for PO number from MuleSoft for
Family
2) 1.
6. Magento
Click
Flat on
file on
from will
that recevice
DN and Flat
observe file Flat file show a "Customer
with
Dollar 4. Click
from MuleSoftDNMuleSoft
(Open) link interface
under It should
Customer
'VON' data
DT - BKand
Banner
MyLaunch
- 2.
dashboard
GopuffCustomers-DT site and Login with
IfCustomer
PO does not meet pattern."
PO error message inCustomer PO
have 9
Customer 5. Search for that Customer PO
Go Puff valid
char(NOV has less
number
datathan
using 6delivery
char ticket field if we receive invaild
DUNS - 3.
Customer number Navigate
1. Magento to
willthat particuar
recevice Flat DT file pattern from MuleSoft for Flat
88776543
24472631 /DUNS Number
DUNS
2) - dashboard
from
6. ClickMuleSoft
on
pagefor Go
that DN and observe
12614
05749904 puffCustomersdebit
4. Click on DN (Open)
havingCustomer link PO file
PO - With under
90102 less thanMy6dashboard
char
any
DT - BK 2. Launch for
value 5. Search DT that Customer
site and Login with PO
or
PO - number
valid data using delivery ticket
without
Should number
3. Navigate /DUNS Number
to that particuar DT It should not show any error
value 6. Click on
start with dashboard page that DN and observe message
It should inCustomer PO field.
show a "Customer
'GUS' but 4. Click on DN Debit(Open) link PO smaller than length."
have less under My dashboard error message inCustomer PO
than 6 5. Search for that Customer PO field if we receive invaild
digits(GU number using delivery ticket pattern from MuleSoft for Flat
S9876) number /DUNS Number file
Customer AEFIS(Banner group)Customers
2 -Customer PO - if
PO - - Verify
Banner more
Customer
Rule 6No
than PO char
has less than 9 char.
Should larger
2. LaunchthanDT maximum
siterecevice length for
and Login with
AFEES 1. Magento
Flat file will
from MuleSoft interface Flat file
start
Customer with valid
from data
MuleSoft for AEFIS(Banner
Customer
GUS but data
DUNS
Banner - - 3. Navigate to thathavingCustomer
group)Customers
AEFIS(Banner
particuar DT
group)Customers - if It should show a "Customer
have
69556810 dashboard
PO with less page
than 9 char..
AFEES
more Customer
4. Click onDT PO length
DNsiteDebit(Open)is morelink than 9
63710
Customer 2. Launch
char and Login with PO larger than maximum
than
DT - BK6 underdata.
Verify My dashboard
Rule No 1 -Customer PO length" error message
DUNS
digits(GU - valid
1.
5. Magento
Search
does not for
meetwill
that recevice
Customer
pattern (DNFlatDebit)
POfile inCustomer PO field if we
PO -
from MuleSoft to that
for particuar DT
AEFIS(Banner
S9876543
Should number
for Flat
dashboard using
file from
page delivery
MuleSoft ticket receive invaild pattern from
63710 group)Customers
)start with number
interface /DUNS
data havingCustomer
Number MuleSoft for Flat file
DT - BK 4. PO Click
withon DNthan
less
GopuffCustomers-
(Open) link under
9ifchar..
Customer PO
'VON'
PO - and My 2. dashboard
Launch DT site and Login with PO smaller than required
Customer
have less is
5. empty
Search
Verify for that Customer PO PO length" error message
Should
DUNS9- valid 1. data. No
Rule
Magento
1 -Customer
willdelivery
recevice Flat) for
file inCustomer PO field if we
than
start with 3. number
does not
Navigate using
meet pattern
to that ticket
(DN
particuar DT
05749904
char(VON from MuleSoft for Go
'VON'
90069(Go and number
Flat file
dashboard /DUNS
from
puffCustomers page Number
MuleSoft
havingCustomer
interface
PO
9876)
have 6. Click
data
4. on that DN and
Click on DN (Open) link under observe MuleSoft for Flat
It should show file
a "Customer
Puff) empty
AEFIS(Banner group)Customers - if
more
DT - BK My 2. dashboard
Launch DT site Login with PO larger than maximum
Customer
than 9 Customer
5. Search fieldand
POthat is empty
Customer
DUNS - valid 1. data will recevice FlatPO
Magento
for Customer length" error message
char(VON
PO - number
Verify
3. Navigate using
Rule No delivery
1
to that - ticket
ForCustomer
particuar DT
69556810
97654324 from
number
groups MuleSoft
/DUNS
that dont for AEFIS(Banner
Number
have any PO receive invaild pattern from
empty(It
63710(AF dashboard
group)Customers page havingCustomer
56)
should 6. Click
pattern
4. Click on that
forDN DN
Flatdebit and
file from observe
MuleSoft MuleSoft for Flat file
Customer
EES ) PO fieldon
interface asdata
empty. (Open) link It should show a "Customer
not
DUNS
DT - BK- Verify under
2. LaunchMy DT
Rule dashboard
Nosite4 - and
DateLogin with PO required." error message
outside
accept
24472631 if NormalCustomers
5. Search
retailer's for that
operation - date
it should
Customer (DN PODebit) inCustomer PO field if we
Customer valid accept data
Customer
05608
PO - number
for
3. Flat using
file
Navigate to from delivery
thatMuleSoft ticket
particuar DT receive empty PO from
PO
DT field is inCustomer
number
- A3 interface /DUNS
dataPO field
Number MuleSoft for Flat filefor go
empty(It dashboard
1. Magento page
will recevice Flat file
empty)
Delivery
should 6. Click
Delivery
4. Click on
on that
date DN
DN-(Open) and
if Delivery observe
date is puff
link under
date - from
less MuleSoft
than start date fromCustomer
not
Customer My dashboard
Verify
2. LaunchRuleDT Nosite4 - and
DateLogin with It should show a "Customer
outside
2013-12-
accept-if hierarchy
5. Search
DUNS
08 (YY- valid
1. data will recevice FlatPO
retailer's
Magento
for that
operation Customer
date (DN Debit) PO required" error message
Customer
24472631
Customer number
for
3. Flat using
file
Navigate from delivery
MuleSoft ticket
to that particuar DT
MM-DD)
PO field
05608 is from
number MuleSoft
/DUNS Number receive empty PO from
DUNS
(Start - interface
dashboard
2. Launch
data
page
empty)
DT - A3 Delivery6. Click on that
date DN and observe
link is MuleSoft for Flat file.
24472631
date 4. Click
Verify
valid on
Rule
data No-debit
DN 4if- Delivery
Date(Open) date
outside
Delivery
12614 greater
under than end
Myoperation
retailer's dashboard datedate (DN DT Debit)
2013-12-
date - 3. Navigate
fromCustomer to that particuar
hierarchy
DT
07 -
it BK 5.
forSearch
Flat
dashboard filefor that
from
page Customer
MuleSoft PO It should not show any error
9999-12-
Customer 1. Magento
number
interface using
datawilldelivery
recevice Flat file message inCustomer PO field.
ticket
Should
31 (YY- 4. Click on DN debit (Open) link It should show a " Date
PO
DUNS
not - any - fromnumber MuleSoft
Delivery
under My /DUNS
date - In
dashboardNumber
between start Customer PO will operation
outside retailer's be same as
MM-DD)
data
24472631 2.
6.
andLaunch
Click on
end date DT
thatsiteDN and
and
ofCustomer Login with
observe DN ticket number
accept
(End date 5. Search
valid datafor that Delivery date date " error message.
05608
less than Hierarchy.
which we receive less than start on delivery date field if we
9999-12-
DT - A3 3.
1. Navigate
Magento to that
willticket particuar
recevice Flat DTfile receive delivery date less than
start
31 it date using delivery
dashboard page number
Delivery
fromCust from
/DUNS MuleSoft
Number start date(Customer
Should
date - 4.
2. Click
Launch on DN
DT debit
site and (Open)
Login link
with It should show a " Date
omer
not 6. Click
Verify
under on
Rule that filtered DN Debit Hierarchy)
No 5 - Delivery date in outside retailer's
My dashboard from MuleSoft
operationfor
2013-12-
hierarchy) valid
and data
observe
theSearch
futurefor (DN Debit) for Flat Flat filefile.
file date " error message.
accept
08 and 5.
3. Navigate tothat
that Delivery
particuar dateDT
greater from
which MuleSoft
we receive interface
greater data
than end on delivery date field if we
9999-12-
Customer dashboard
Delivery datepage-ticket
Future Delivery
than
31 date
it - 4. using delivery number
Click on DN debit (Open) link receive delivery date greater
DUNS
fromCust date
/DUNS Number than end date(Customer
should
24472631 under 1. My dashboard
Magento will recevice Flat file
omer
accept 6. Click
In Verify
5. Search on that
RuleforNothat filtered
5 - Delivery DN
Delivery date date in Hierarchy) from MuleSoft for
Debit
05608
hierarchy) from
and MuleSoft
observe
the future for
(DN Debit) delivery
for Flatdate file Flat filefile.
between
DT - A3 which 2. Launchwe receive
DT site inbetween
and Login start
with
start and and from MuleSoft
end interface data
Delivery
Customer valid datadate
Delivery date
of that Customer
- itdelivery
should accept
end
date date Hierarchy using ticket less It should not show any error
DUNS
ofCustom - 3. Navigate
than
number or equal
/DUNS
totothat particuar
system
Number dateDT . message in Delivery date field
(MM-DD-
24472631 dashboard
1. Click
Magento page
willfiltered
receviceDN Flat file if we receive any date (old 90
er
YY) it 6.
4. Click on that
on DN Debit(Open) Debit
link It should show a "Delivery
05608
Hierarchy. from
and MuleSoft
observe for delivery date days from current date.)
Should
DT - A3 2. Launch DT site and Login with date should not be greater
under My dashboard
not
Delivery 5. Search
valid datafor that delivery date than system date.' error
accept
date using delivery ticket number
3. Navigate to that particuar DT message in Delivery date field
future /DUNS
(MM-DD- dashboard page Number if we receive any future date
delivery
YY) it 6. Click on that DebitDN
4. Click on DN Debit(Open) link and as delivery date from
dates.
should observe
under My dashboard MuleSoft for Flat file
accept 5. Search for that delivery date It should not show any error
less than using delivery ticket number message in Delivery date field
or equal /DUNS Number if we receive valid delivery
to system 6. Click on that DebitDN and date from MuleSoft for Flat
date observe file
Customer between 90 days from current
date
DUNS - valid
date. data
Customer
(MM-DD- 3.
24472631
DUNS 1. Navigate
recevice Flat DTfile
YY)
05608 if - dashboard
from MuleSoftpage for between 90 It should show a "Delivery
84734000
Delivery Verify
4. Click Rule No Debit(Open)
on current
DN 7 - Delivery ticket link date less than allowable days
DT
10001- A3 days
no from
missing date.
(DN Debit) from
date
Deliveryis under
2. My
Launch for dashboard
DT Flat and Login with of current date " error
site file
DT
older- BK MuleSoft
5. Search for that delivery date message in delivery date field
date
Delivery valid dataticket number
Delivery - if Delivery If user receive delivery date
than
(MM-DD- 90 using
3. delivery
Navigate ticket
to that number
ticket
days from ticket
/DUNS number
Number field particuar
YY)
number if - dashboard
1. Click
Magento page
willDebitDN
recevice and Flat file current date from MuleSoft
current
Delivery 6.
4. on that
Click on DN Debit(Open) link
without
date. from
VerifyMuleSoft
observe Rule No 7for empty delivery
- Delivery ticket for Flat file
date
deliveryis under
date My dashboard
older no
5. missingfor
Search (DNthat Debit) from
delivery
ticket 2. Launch for
MuleSoft DT Flat
site file
and Logindate with It should not show any error
than 90
number(it using
valid dataticket number - if Debit message in Delivery date field
delivery ticket number
Customer
days from Delivery
/DUNS
Verify Number
Rule No 8 - byparticuar
recevingDT if we receive valid delivery
should
DUNS - 3.
DN Navigate
has the to that
Delivery ticket number
current
Customer
not 6. Click on that
DuplicateCustomer
dashboard page DebitDN PO (DN Debit) date from MuleSoft for Flat
and
84734000
date.
DUNS -if 1. Magento
observe
forClick
sameCustomerwill recevice Flat file file
from MuleSoft
accept
10001 4.
from on DN Debit(Open)
MuleSoft link If user receive empty delivery
84734000
delivery for FlatMy
under filedashboard ticket number from MuleSoft
DT
10001- BK 2.
1. Launch
Magento DTwill
siterecevice
and Login Flatwith
file for Flat filethen it should show
ticket
Delivery 5. Search
valid data for that empty delivery
DT - BK
number from
ticket
Verify MuleSoft
using
Rule NoDUNS 8for Number
- by recevingDT "Delivery ticket no missing"
ticket
Customer 3. Navigate to
DuplicateCustomer that particuar
PO
field
number is - 6. Click on that
DuplicateCustomer
dashboard page filteredPO (DN Debit) error message in Delivery
Debit DN
PO -
empty)
Customer 2.
and
forLaunch
observe DT site
differentCustomer and Login
fromlink with ticket field.
GUS7723
GUS7053 4. Click
Verify
valid on DN
Rule
data No Debit(Open)
8-
DUNS
56 - MuleSoft
under Myfor Flat filePO (DN Debit) If user receive delivery ticket
dashboard
DuplicateCustomer
56
84734000 3.
1. Navigate
Magento to
willthat particuar
recevice Flat DT
file number from MuleSoft for
(WIth
(It should 5.
forSearch for
sameCustomer
dashboard that
page delivery ticket
from MuleSoft
10001
delivery from
using
for MuleSoft
DUNS
Flat on Numberfor
fileDN Debit(Open) link Flat filethen it should not
not
DT - BK 4. Click
DuplicateCustomer PO
ticket
accept in 6. Click
Customer
under on
My DTthat filtered
PO - It should be
dashboard Debit DN show
If userany errorany
receive message in
Customer
number) 2.
andLaunch
observe
PO for Login with Delivery ticket field.
case
PO - of 5. Search
valid datafor that existingCustomer PO number
sameCust sameCustomer.
DuplicateCustomer PO using from MuleSoft for Flat file
GUS2153 3.
1. Navigate
Magento to
willthat particuar
omer
Customer
32 PO delivery
pagefor /DUNS for sameCustomer then it
Customer
Customer
for
DUNS - from
Number
Verify MuleSoft
Rule No 9 -by receving should show
(It
DUNSshould 4. Click on DN Debit(Open) link
DUNS
sameCust
24472631
accept --in DuplicateCustomer
6. Click
Duplicate
under on that
My delivery DebitDN
dashboard
PO and
ticket no (DN "DuplicateCustomer PO" error
Customer
84734000
24472631
omer) 2. Launch
observe DT site and Login with
12614
case
DUNS of- Debit)
5. SearchfromforMuleSoft
that for Flat file If user receive any PO field
message inCustomer
10001
12614
DT - BK valid dataticket
Delivery number - Existed
sameCust
24472631
DT - BK DuplicateCustomer
3. Navigate to that PO using
particuar DT existingCustomer PO number
omer
12614 PO delivery
delivery ticket
ticket number
number /DUNS from MuleSoft for Flat filefor
Customer
Delivery dashboard
1. Magentopage will recevice Flat file differentCustomer then it
for
DT
PO -
- BK Number
4. Click on DN Debit(Open) link
ticket
diffCusto from
6. MuleSoft
Click that for
on dashboard existed
DebitDN delivery
and should not show any error
GUS995
product
number- under
ticket My
number
mer)
Delivery
(It should observe
Verify
5. SearchRuleforNothat
9 - by receving message inCustomer PO field
code-
80622235
ticket 2. Launch
delivery and Login
no (DN with If user receive any
accept
(It in
07585603
valid data PO using uniqueCustomer PO number
number-
case
1140 of Debit)
delivery from MuleSoft
ticket number for Flat file from MuleSoft for Flat filefor
/DUNS
should
80622231 3.
1. Navigate
Magento to
willthat particuar
recevice Flat DTfile existedCustomer then it
uniqueCu
Again
not Number
Verify
dashboardRule page
No 10 -by receving If user receives any existed
11
stomer from
6. MuleSoft
Click on that for delivery
DebitDN and ticket should
same
accept
(It should in Duplicate
4. Click onLine
number
Item(DN Debit)
DN Debit(Open) link deliverynot show
ticket any error
number from
PO)
product
case of observe
from MuleSoft
under My for Flat file
dashboard message
MuleSoft inCustomer
for Flat PO field
filein
accept
code inin 2. Launchcode
Product DT site
- Same andproduct
Login with as
same
case of 5. Search
valid data for that delivery ticket delivery ticket field then it
2nd line
existing
Customer 2nd line
number item
using delivery ticket should shows a "Delivery
unique
item -- 3.
1. Navigate
Magento to
willthat particuar
delivery
DUNS
delivery number
Verify
dashboard /DUNS
Rule pagefor Duplicate Line ticket number already used"
No 10Number
- Duplicate Line
07585603
ticket from
6. MuleSoft
Click on that DebitDN andlinkfor error
24472631
ticket
1140
Item(DN
4. Click onDebit)
Item
from MuleSoft
DN Debit(Open) If usermessage
receivesinany Delivery
unique
number)
12614
number observe
Flat fileMy dashboard
under ticket
deliverynumber
ticket field.
number from
(It
DT should
- BK 2. Launchcode
Product DT site and Login
- Should with
not ticket
be Same
in
not 5. Search
valid data for that delivery no MuleSoft for Flat filein
delivery product
using as 2ndticket
delivery line item
number DT delivery ticket field then it
accept
product 3. Navigate
1. Magento to
willthat particuar
recevice Flat file shouldn't show any error
ticket
incase /DUNS Number
code 1-of
number
dashboard
from
6. MuleSoft
Click on
page
that DebitDN andlink message in delivery
if we
07684010 4.
2. Click
Launch onDTDNsiteDebit(Open)
and Login with If user receives sameticket
product
field)
receive observe
under My dashboard number
code as field.
2nd line item from
0125 valid data
same
product 5. Search for that Duplicate
3. Navigate to that particuar DT Line MuleSoft for Flat filein
product
code 2- Item using delivery
dashboard page ticket product code field then it
code
07684048 as number /DUNS Number
4. Click on DN Debit(Open) link show a "Duplicate Line Item"
second
5116 6. Click on that
under My dashboard DebitDN and error message on product
line item)
(It should observe
5. Search for that Duplicate Line code
If userfield
receives different diff
accpet in Item(Should not be Same product line item from MuleSoft for
case of as 2nd line item) using delivery Flat filein product code field
diff line ticket number /DUNS Number then it should not show any
level 6. Click on that DebitDN and error message on product
items) observe code field
code
24472631 - Eaches - Eaches should be
not
07756700 valid dataof "eaches per box"
multiples
01788
accept
2204 in 3.
1. Magento to
Navigate willthat particuar
recevice Flat DT
file
case
(Eaches of dashboard
file from page
MuleSoft for Eaches in
DT
eaches- A6 Verify
4. Click Rule
on DNNo Debit(Open)
12 - link
Per Box is full boxes
InvalidCustomer(DN Debit) from
other
24) under
2. LaunchMy DTdashboard and Login with if user receives eaches other
site file
than
Customer MuleSoft
5. Search for
for Flat
that Eaches not in full than multiples of "eaches per
DUNS valid
DUNS data
number - InvalidCustomer
multiples
DUNS
Eaches -- boxes
3. using
Navigate delivery ticket
to that particuar number
DT box" from MuleSoft for Flat
number
of
24472631 - DUNS
/DUNS number
Number filethen it should show
48
24472631 dashboard
1. Magento page
"eaches
01707
(It should 6. Click
Verify
4. Click on
Rule that
on DN filtered
No Debit(Open)
12 - DebitDN
link "Eaches not in full boxes" on
01788
per box") from
and MuleSoft
observe for InvalidCustomer
accept
(It should in under
DUNS My dashboardDebit) from eaches box.
InvalidCustomer(DN
number
DT
case - A6
of MuleSoft
5. Search for
for Flat file
Customer
not 2. Launch
DUNS DT that
number site Eaches
and
- DUNS
in full
Login
number with if user receives eaches
multiples
DUNS
accept- boxes
valid using delivery ticket number multiples of "eaches per box"
of field isdata
/DUNS empty
Number form
24472631
incase
DUNS of 3.
1. Navigate
Magento to that
will particuar
recevice Flat DT
file If userMuleSoft
reveives for Flatthen
"eaches
01707
invalid 6. Click on that
Verify Rule page
dashboard filtered
No 12 - DebitDN user shouldn't
InvalidCustomer getDUNS
show any
number
per box")- from
and MuleSoft
observe
InvalidCustomer(DN error message.
Debit) from number in DUNS number
Duns
Customer
Empty 4.
2. Click
Launch onDTDNsite
Debit(Open)
and Login linkwith
DT
number
DUNS - A6- MuleSoft
under My for Flat file
dashboard field from MuleSoft for Flat
(It should valid
DUNS data
number - ValidCustomer
in
notDUNS
24472631 5.
3. Search
Navigate for that InvalidCustomer
to that particuar DT filethen it should show
number
01707 DUNS
using number
delivery ticket number "InvalidCustomer" error
accept
DUNS dashboard
1. Magento page
will recevice Flat file If user reveives
filed)
incase of 6. Click
Verify
4. Click on
Rule that
on DN DebitDN
No Debit(Open) and
13 - Invalid Product
link message on DUNS
emptyCustomer DUNS number
number
DT - A6 - from
observe MuleSoft
(DN Debit) fromfor validCustomer
MuleSoft for Flat field
empty
69556810 under
2. Launch DT site and Login with number in DUNS number
My dashboard
Duns
Customer file
5. Search for that empty DUNs field from MuleSoft for Flat
32216 valid
DUNS data
number - Invalid Product
number
DUNS
(It should- numberCustomer
3. using
Navigate to that particuar DT delivery filethen it should show
Product
in DUNS
24472631 code
ticket number "InvalidCustomer" error
accept
code - dashboard
1. Magento page
number
01707
incase of 6. Click
Verify
4. Click on
Rule that
on DN DebitDN
No Debit(Open) and
12 - Invalid Product
link message on DUNS number
07756728
filed) from
observe MuleSoft
(DN Debit) for Invalid Product
from MuleSoft for Flat field
valid
3030 under
2. LaunchMy DTdashboard
site and Login with If user reveives validCustomer
DT
Duns - A6
Customer file
5. Search for that validCustomer DUNS number in DUNS
(It should valid
DUNS data
numberticket
- Product code field number field from MuleSoft
number
DUNS
not - using
3. delivery
Navigate to that particuarnumber DT
in DUNS
24472631 is empty
/DUNS Number for Flat filethen it should not
accept
Product dashboard
1. Click
Magento page
willDebitDN
recevice andFlat file show any error message on
number
05644
incase 6. on that
code
filed)
DT - A3 - of 4. Click
from
observe
on DN Debit(Open) link
MuleSoft If user receives Invalid
DUNS number field
invalid
Empty under
2. LaunchMy dashboard
DT site and Login with Product code in Product code
Product
Product Verify
5. SearchRule No 13 - by receiving
for that Invalid Product field from MuleSoft for Flat
(It
code should
-in valid
Invalid data
Productticket
(DN Debit) from
code
not using
3. delivery
Navigate number filethen the it should show
07756700
product MuleSoft
/DUNS fortoFlat
Number
thatfileparticuar DT
"Invalid product " error
accept
2204 dashboard
1. Magento page
code
incase of 6. Click
Verify
4. Click on
Rule that
on DN filtered
No Debit(Open) DebitDN
14 -No delivery linkdate message on product code
Valid
field) from
and MuleSoft
observe
(DN Debit) for valid Product
from MuleSoft for Flat field.
empty
Product under
site and Login with If user reveives empty in
Product file
5. Search for that empty Product product code field from
code valid
Deliverydatadate - if delivery
code
(It in
should code
3. using delivery ticket dateDTfield MuleSoft for Flat filethen it
Navigate to that particuar
Customer
product is empty
number /DUNS Number should show "Invalid product"
accept
DUNS - dashboard
1. Click
Magento page
willfiltered
receviceDebitDN
Flat file error message product code
code
Customer
incase of 6.
4. Click on that
on DN Debit(Open) linkdate
24472631
field)
DUNS - from
and MuleSoft
observe for no delivery field.
valid
02456 under
2. LaunchMy dashboard
DT site and Login with If user receives valid Product
24472631
Product Verify
5. SearchRule No 14 - Delivery date
DT
02456 - A3 valid
(DN data from MuleSoft for Flat code in Product code field
Debit)
for that valid Product
code
Delivery in using
3. delivery
Navigate to ticket number DT
that particuar from MuleSoft for Flat
DT - A3
product file
/DUNS Number filethen it should not show
date
Deliveryfield dashboard
1. Magento page
code
-date
Empty 6.
4. Click
Verify
Click on
Rule that
on DN filtered
No Debit(Open) DebitDN
15 - No line item link any error message on product
field) field from
and MuleSoft
observe
(DN Debit) for delivery date
from MuleSoft for Flat code field.
(It
- should under
site and Login with If user receive the form
not file
5. Search for that no delivery date without any delivery date
(MM/DD/ valid
Product data
Code -ticket
if product code
accept
YYYY) if using
3. delivery
Navigate number
to that particuar DT from MuleSoft for Flat file
Customer
delivery field
/DUNS is epmpty
Number then it should show "no
(It
DUNSshould- dashboard
1. Click
Magento page
willDebitDN
recevice andFlat file delivery date" error message
date
accep field
if 6.
4. Click on that
on DN Debit(Open) link
24472631
is empty) from
observe MuleSoft for No line item on delivery date field.
delivery
05608 under My dashboard
2. Launch DT site and Login with
date
DT - A3field 5. Search
valid datafor that delivery date If user receive the form with
is has
Product using delivery ticket number
3. Navigate to that particuar DT any valid delivery date from
valid
Code - /DUNS Number
dashboard page MuleSoft for Flat filethen it
dalivery
Empty 6. Click on that DebitDN
4. Click on DN Debit(Open) link and should not show any error
date)
(It should observe
under My dashboard message on delivery
If user receive date field
the form
not 5. Search for that No line item without any line items from
accept if using delivery ticket number MuleSoft for Flat filethen user
product /DUNS Number should show " Product line
code field 6. Click on that DebitDN and items are missing "error
is empty ) observe message
DUNS
07756700 - Product code - if Product is not
40307
Product
84734000 valid datato that Customer
2887
DT - A6 mapped
Code
10001
(It should 1. Magento to
- 3. Navigate willthat particuar
Delivery
07756700
DT - A8 dashboard page
not
date - from
Verify MuleSoft for Product not
2228
Delivery
accept 4. ClickRule
listed on DN No Debit(Open)
16 -Product not link
Customer
(MM/DD/
(It
date
incase
DUNS - -of 2. Launch DT site and Login withfor
should listed(DN
under My Debit)
dashboard from MuleSoft
YYYY)
accept
(MM/DD/ if Flat
5. file for that line items using If user receive the form
Search
product
84734000
Product valid
Productdata
code -number
if Product are
product
YYYY)
code is delivery
Verify
3. ticket
Rule
Navigate No 17
to that -Quantity/DUNS
particuar DT without any line items from
10001
code
code -
field mapped
Number to the Customer MuleSoft for Flat filethencode
user
Product
not
DT -exist exceeds
A8any dashboard box Threshold
page - requires If user receives product
07585600
Customer
is
code has - 1.
6. Magento
Click on
verification will
that
(DN recevice
DebitDN Flat
and
Debit) fromlink file should not show any error
in
Delivery
1600 4. Click on DN Debit(Open) that is not mapped to the
DUNS
products)
07756700
system/N - from observeMuleSoft
MuleSoft
under My for Flat
dashboard file message.
date
(It
21339648
1238
-
should 2. Launch DT site and
GopuffCustomers - Loginmore
eaches with retailer in the product code
ot
(MM/DD/
accept 5. Search
valid for that Product not field, from MuleSoft for Flat
01700
(Eaches
mapped
YYYY) than
listed
Verify5data
box'sNo
using
Rule delivery
17 ticket
-Quantity filethen it should show
incase
DT
per A8of- 3.
-Box 1. Navigate
Magento to that
will particuar
recevice Flat DTfile “Product not listed” error
to
Product
product that number
exceeds
dashboard /DUNS
box Number
Threshold
pagefor Quantity - requires
Delivery
6)
Customer from
6. MuleSoft
Click
code
code
date
Eaches
-is
- - 4. Click on
verification
exceeds onbox
that
(DN
DN DebitDN
Debit) from
Debit(Open)
Threshold
andlink message on product
If user receives productcode
code
)07756700
exist in observe
MuleSoft
under My for Flat
dashboard file field.
that is mapped to that retailer
(MM/DD/
36
Customer 2. Launch DT site and Login with
1238
system/m
YYYY) GopuffCustomers
5. Search for that -Product
It should is be 5 in the product code field from
listed
(GopuffCu
DUNS
(Eaches - valid
box's data
apped
Product
stomers to- Verify
using delivery
Rule No ticket number DT
17 -Quantity MuleSoft for Flat filethen it
21339648
per
that
code Box- - 3.
1. Navigate
Magento
/DUNS
exceeds Number
box
to that
will particuar
recevice
Threshold - Flat file should not show any error
requires
It
01700
6) should dashboard
from MuleSoftpagefor Quantity
Customer
07756700
not 6. Click
Click on
verification
4. on that
(DN
DN DebitDN
Debit) from
Debit(Open) andlink message on product
If user receives recivescode
more
DT
Eaches
)accept - A8 - exceeds
observe box Threshold field.
2228
Delivery in MuleSoft
under My for Flat
dashboard file than 5 boxs's for
30
(Eaches 2. Launch
Food DT migration
Service site and Login with
- It should
case
date
(GopuffCu of
- 5. Search
valid data for that Quantity exceeds GopuffCustomers from
per
eaches
(MM/DD/ Box - be box 5using
box's
Ruledelivery ticket MuleSoft for Flat filethen it
stomers
24) - Verify
3.
1. Navigate
Magento
No
to
will
17 -Quantity
that particuar
recevice Flat DTfile should show "Quantity
more
YYYY)
It number
exceeds
should- dashboard /DUNS
box Number
Threshold
pagefor Quantity - requires
Eaches
than 5 in 6. from MuleSoft
Click
Product
accept
144 4. Click on
verification
exceeds onbox
that
(DN
DN DebitDN
Debit) from
Debit(Open)
Threshold
andlink exceeds box Threshold " error
box's)
code
case -
of observe
MuleSoft
under Myfor Flat file
dashboard message in eaches box.
Customer
(It should
07756700 2. Launch
Food DT
Service site and Login
migration - It with If user receives recives less
should
eaches
DUNS
not - 5. Search
valid datafor that Quantity exceeds than or equals 5 boxs's for
2228
are
213396485 be
box 5using
box's delivery ticket GopuffCustomers from
accept
(Eaches in 3.1. Navigate
Magento to
willthat particuar
recevice Flat DTfile MuleSoft for Flat filethen it
boxes
02300
case of or number
dashboard /DUNS Number
pagefor Quantity
per
less
DT -Box
A8 - 6.
than from
Verify MuleSoft
Click on that DebitDN andlink should not showrecives
any error
Food
24) 4. ClickRule
exceeds onbox
No Debit(Open)
DN 17
Threshold
-Quantity If user receives more
5 boxes)
Delivery under
Service observe
exceeds My box message
Threshold - requires than 5 boxs's for Food
dashboard in eaches box.Service
Eaches
date - - 2. Launch DT(DN
verification site and Login with
migration
120 5. Search
valid data for thatDebit)
Quantity fromexceeds migration from MuleSoft for
(MM/DD/
-(Iteaches MuleSoft
box using for Flat file
delivery ticket Flat filethen it should show
YYYY)should 3. Navigate to that-particuar
NormalCustomers it should DT
more
accept number
in dashboard /DUNSpage Number "Quantity exceeds box
Product
than 5 accept
6. Click
Verify any
on
Rule value
that DebitDN
No Debit(Open)
1 -Customer link and PO Threshold " error message in
case
code of
- 4.
1. Click on DN
Magento will recevice Flat file
boxes)
Food observe
does notMymeet pattern (DN eaches box.
07684010 under from dashboard
MuleSoft
Credit)for Flat file from MuleSoft.
If user receives less than or
Service
0040(Eac 2. 5. Search for that
Launch DT site and Quantity exceeds equals 5 boxs's for Food
migration GopuffCustomers-
box using delivery PO Login
ticket should with
starts Service migration from
hes per valid with data
GUS
-Box
eaches
-6) number
Verify
3. /DUNS
Rule
Navigate No
to 1Number
that-Customer
particuar PODT MuleSoft for Flat filethen it
is 5 1.
6. Magento
Click on will
that recevice
DebitDN Flat
and file should not show any error
Eaches - does not meet
dashboard
from MuleSoftpagepattern
for Go
(DN
boxes)
120 observe
Credit)for
Click on Flat file from MuleSoft link PO message in eaches box.
Customer 4. puffCustomers
interface
DN Debit(Open)
data havingCustomer
NormalCu
Banner - under startingMy dashboard
with GUS and 6 char PO If user receives eaches in
stomers - GopuffCustomers-
5. Search using if Customer
delivery ticket
Go Puff 2. Verify Rule
Launch
does not
No
DT site
starts
1 -Customer
andGUS
with Login with more than or less than 5 box's
PO
it should
Customer valid number
does data will recevice Flat file from MuleSoft for Flat
not/DUNS
meet Number
pattern (DN
accept 1.
6. Magento
Click on Flat
that DebitDN and DT filethen should show any
DUNS - Credit)for 3. Navigate
from MuleSoft
file
to that
for
from
Go
MuleSoft
particuar
any value
05749904 observe
interface data pagehavingCustomer PO error message.
Customer dashboardpuffCustomers
AEFIS(Banner group)Customers -
It should not show any error
90069
Banner - not 4. Click on DN
startingstartsCredit
with with
GUS VON(Open)
and 6 char link message inCustomer PO field
DT - BK PO should
under My dashboard if we receive vaildCustomer
Go Puff 2. 1. Launch
Magento DT siterecevice
and Login Flatwith
PO -
Customer 5. Search
valid data forwill
that Customer file PO number from MuleSoft for
PO
GUS1234 from MuleSoft
number using for AEFIS(Banner
delivery ticket Flat file
DUNS - 3. Navigate to thathavingCustomer
56
05749904 number /DUNS Number
Customer dashboardPO starting page
with VON and 9 char It should show a "Customer
90102 4. Click
Banner - 2. Launch DT site on DN Credit(Open)
and Login with link PO does not meet pattern."
DT
AFEES- BK under My
valid data dashboard error message inCustomer PO
PO - 5. Search for that
Customer 3. Navigate to that particuar DT Customer PO field if we receive invaild
ABC0987 number
DUNS - dashboard page using delivery ticket pattern from MuleSoft for Flat
65 number /DUNS Number
69556810 4. Click on DN (Open) link under file
32216 My dashboard It should not show any error
DT - A3 5. Search for that Customer PO message inCustomer PO field
PO - number using delivery ticket if we receive vaildCustomer
VON1234 number /DUNS Number PO number from MuleSoft for
56789 6. Click on that DN and observe Flat file
interface data
Banner - 2. Launch DT site and
NormalCustomers - it Login
shouldwith
AFEES valid
accept data
Customer Verify
3. Rule
Navigate No
to 2 -Customer
that particuarPO DT
inCustomer
larger than pagePO field
maximum length for
DUNS - dashboard
1. Magento will recevice Flat file
69556810 Flat
4. file on
Click fromDNMuleSoft
(Open) link interface
under It should show a "Customer
Customer from
data MuleSoft
32216
Banner - My
2. dashboard
Launch DT site and Login with PO does not meet pattern."
Customer
DT - A3 GopuffCustomers-
5. Search for that IfCustomer
Customer PO PO error message inCustomer PO
Family
Banner valid data
PO - -
Dollar
has less
number
Verify
3.
than
using
Rule
Navigate No
to
6delivery
2char
that -Customer ticketPO
particuar DT field if we receive invaild
Go Puff
QWE1234 1. Magento
number /DUNS
larger than page will recevice
Number
maximum length for Flat file pattern from MuleSoft for Flat
Customer
Customer dashboard
from MuleSoft for Go
56789
DUNS -- 6.
4. Click
Flat on
file on
Click fromthat
DNMuleSoft DN
Credit and observe
link PO file
interface
(Open)
DUNS
Customer puffCustomers
data havingCustomer
24472631
05749904 under
less thanMy6dashboard
char IfCustomer PO
Banner
12614 - GopuffCustomers-
5. Search
Verify Rule forNothat Customer
1 -Customer PO
90102
Go -Puff 2.
hasLaunch
more thansite
DT and
6pattern
char Login PO with
DT
DT - BKBK number
does
valid not using
meet delivery
data will recevice Flat file ticket
(DN Credit)
Customer
PO -- Any 1.
forMagento
number /DUNS
Flat file from Number
MuleSoft It should not show any error
PO
DUNS - 3. Navigate
from MuleSoft to that
for particuar DT
Go
value
Should 6. Click
interface
dashboard on that
pagehavingCustomer PO message
data DN and observe It should inCustomer PO field.
show a "Customer
05749904 puffCustomers
AEFIS(Banner group)Customers - if
start
90102 with 4. Clickthan
Verify
more on DN
Rule 6No Credit(Open)
char2 -Customer PO link PO smaller than length."
Customer
'GUS' but Customer
under
larger My
than PO has less than
dashboard
maximum 9 char. error message inCustomer PO
length for
DT - BK
Banner - 2.
1. Launch
Magento DT siterecevice
and Login Flatwith
have
PO - less 5. Search
Flat
validfile
data forwill
from that
MuleSoft Customer PO
interfacefile field if we receive invaild
AFEES
than 6 from
number
data MuleSoft
using for
delivery AEFIS(Banner
ticket pattern from MuleSoft for Flat
Should
Customer 3. Navigate to thathavingCustomer
digits
start with number
AEFIS(Banner
dashboard /DUNS
page group)Customers - if file
Number It should show a "Customer
DUNS
Customer - PO with less
Customer PO than
length 9 char..
is morelink than 9 PO larger than maximum
GUS but
69556810 4.
2. Click on DN Credit(Open)
Banner
have - char
under
Verify My dashboard
Rule No 1 -Customer PO length" error message
63710
AFEES valid
1. data.
Magento will recevice FlatPOfile inCustomer PO field if we
more
DT - A3 5.
3. Search
does not
Navigate for
meet that Customer
pattern
to that (DN
particuar DT
Customer
than from MuleSoft for from
AEFIS(Banner
PO
DUNS - 6- number
Credit)for
dashboard using
group)Customers
Flat
page delivery
file ticket
MuleSoft receive invaild pattern from
havingCustomer
digits
Should number
interface
4. Click /DUNS
data Number MuleSoft for Flat file
69556810 PO withon DNthan
less
GopuffCustomers-
(Open) link under
9ifchar..
Customer PO
start
63710with My
2. dashboard
Launch DT site and Login with PO smaller than required
'VON' is empty
DT - A3and 5. Search
Verify
valid
1.
for
data. No
Rule
Magento
that Customer PO
1 -Customer
willdelivery
recevice
PO length" error message
Flat file inCustomer PO field if we
have
PO - less number
does
3. not
Navigate using
meet pattern
to that ticket
(DN
particuar DT
than 9 from
number MuleSoft
Credit)for /DUNS
Flat for
file Go
Number
from MuleSoft receive invaild pattern from
Should dashboard
puffCustomers page havingCustomer PO MuleSoft for Flat file
char
start with 6. Click
interface
4. on
Click ondatathat DN and
DN (Open) link under observe It should show a "Customer
Customer empty
AEFIS(Banner group)Customers - if PO larger than maximum
'VON'
Bannerand - My
2. dashboard
Launch DT site
have Customer
5. Search POthat
for fieldand Login with
is empty
Customer PO length" error message
Go Puff valid
1. data
Magento willdelivery
recevice Flat file inCustomer PO field if we
more
Customer number
Verify
3. Navigate using
Rule No 1
to that - ticket
ForCustomer
particuar DT
than from MuleSoft for AEFIS(Banner
DUNS9- number
groups
dashboard /DUNS
that
group)Customers
dont
page Number
have any PO
havingCustomer
char
05749904 6. Click
pattern
4. Click on that
forDN DN
FlatCredit and
file from observe
MuleSoft MuleSoft for Flat file
Customer PO fieldon
interface asdata
empty. (Open) link It should show a "Customer
90069
Banner - under
site and PO required." error message
DT - BK NormalCustomers
5. Search for that - it Login
shouldwith
Customer PO inCustomer PO field if we
AFEES valid
accept data
PO -
Customer number
3. using
Navigate to delivery
that ticket
particuar DT receive empty PO from
Should inCustomer PO field
DUNS - be number
dashboard
1. Magento
/DUNS
Verify Rule page No 5 - Delivery date in MuleSoft for Flat filefor go
Number
willCredit)for
recevice Flat file
empty
69556810 6. Click
theClick
4. on
future that
on (DN
DN (Open) DN andlinkobserve
Flat
underfile puff
from
from MuleSoft
63710 My
2. dashboard
Launch DT site and Login with It should show a "Customer
DT - A3 Delivery
5. Search date
for - Future
that CustomerDeliveryPO PO required" error message
Customer
Delivery valid
date data
PO - -
Banner number
3. Navigate using to delivery
that ticket
particuar DT inCustomer PO field if we
date
should be 1. Magento
number /DUNS
Verify Rule page will recevice Flat file
Number
Family
Customer dashboard
from MuleSoft for
empty
Dollar 6.
4. Click
theClick on
future
onDT that
(DN
DNsite DNdelivery
and
Credit)for
Credit (Open)
date
observe
Flat file MuleSoft for Flat file.
link
DUNS - 2. Launch
from MuleSoft and
interface Logindatawith
Customer
84734000 under
valid My dashboard
data
Delivery
DUNS - Delivery
5. Search date - it should
fortothat Customer accept
PO less It should not show any error
10001
date 3. Navigate
than or equal that
to particuar
system dateDT .
24472631
DT - A8 number
dashboard using
page delivery ticket message inCustomer PO field.
Customer
12614 1. Magento
number /DUNS will Number
recevice Flat file Customer PO will be same as
Delivery
DUNS - 4. Click
MuleSoft link It should show a "Delivery
DT - BK
date - it 6. Click
under that for
on dashboard DNdelivery
and observe date DN ticket number
84734000 2. Launch DT site and Login with date should not be greater
My
Should
10001 5. Search
valid datafor that delivery date than system date.' error
accept
DT - A8 using delivery ticket
3. Navigate to that particuar DT number message in Delivery date field
future
Delivery /DUNS Number
dashboard page if we receive any future date
dalivery
date - it 6. Click on that filtered
4. Click on DN Credit(Open) link Credit DN as delivery date from
dates.
Should and observe
under My dashboard MuleSoft for Flat file
accept 5. Search for that delivery date It should not show any error
old 90 using delivery ticket number message in Delivery date field
days from /DUNS Number if we receive valid delivery
current 6. Click on that filtered Credit DN date from MuleSoft for Flat
date. and observe file
between 90 days from current
84734000
Delivery valid
date. data
10001
date 3.
1. Navigate
recevice Flat DT
file
DT - A8
Customer dashboard
from MuleSoftpage for between 90 It should show a "Delivery
Delivery Verify
4. Click Rule No Credit(Open)
on current
DN 7 - Delivery ticketlink date less than allowable days
DUNS - days
no from
missing date.
(DN Credit)from
date - it
84734000 under
2. My
Launch for dashboard
DT Flat and Login with of current date " error
site file
Should MuleSoft
5. Search for that delivery date message in delivery date field
10001 valid dataticket number
Delivery - if Delivery If user receive delivery date
not
DT -A8 using
3. delivery
Navigate ticket
to that number
accept ticket
/DUNS number
Number field particuar
Delivery dashboard
1. Click
Magento page
willfiltered
receviceCredit
Flat file
less
datethan 6.
- it
4. Click on that
on DN Credit(Open) DN
link current date from MuleSoft
start from
date
and MuleSoft
observe
Verify Rule for empty delivery
No 7 - Delivery ticket for Flat file
Should under
date My dashboard
accept no
5. missing
Search (DN
for that Credit)from
delivery
Customer 2. Launch for
MuleSoft DT Flat
site file
and Logindate
with It should not show any error
old
DUNS 90 -using
valid dataticket number - if Credit message in Delivery date field
days Delivery
from
/DUNS
Verify Number
Rule No 8 - byparticuar
recevingDT if we receive valid delivery
84734000
Customer 3.
DN Navigate
has the to that
current
DuplicateCustomer
dashboard page filtered Credit
PO (DN DN date from MuleSoft for Flat
DUNS
date. -1.
andMagento
observe
Credit)for will recevice Flat file file
DT - BK
84734000 4. Click
from on sameCustomer
DN Credit(Open)
MuleSoft
from
link If user receive empty delivery
Delivery MuleSoft
under My for Flat
dashboard file ticket number from MuleSoft
10001 2.
1. Launch
Magento DTwill
siterecevice
and Login Flatwith
file for Flat filethen it should show
ticket
DT - BK 5. Search
valid data for that empty delivery
number from MuleSoft 8for
Delivery -
ticket
Verify
3. using
Rule No
Navigate DUNS
to
DuplicateCustomer that Number
- by recevingDT
particuar
PO
"Delivery ticket no missing"
Should
ticket be6. Click on that
DuplicateCustomer
dashboard page filtered Credit
PO (DN DN error message in Delivery
empty 2.
andLaunch
observe
Credit)for DT site and Login with
from ticket field.
number - 4. Click
Verify
valid on differentCustomer
Rule
data DN
No Credit(Open)
8- link
Should MuleSoft
under for Flat
My dashboard
DuplicateCustomer filePO (DN DT If user receive delivery ticket
3.
1. Navigate
Magento to
willthat particuar
recevice Flat file number from MuleSoft for
have
Customer 5. Search
Credit)for
dashboard for that
sameCustomer
pagefor delivery ticket
from
delivery from
using MuleSoft
DUNS
MuleSoft forNumber
Flat file Flat filethen it should not
DUNS - 4. Click on DN
DuplicateCustomer Credit(Open)
PO link
ticket
84734000 6. Click
Customer
under on
My DTthat filtered
PO - It should be
dashboard Credit DN show
If userany errorany
receive message in
number 2.
andLaunch
observe
PO forLogin with Delivery ticket field.
10001 5. Search
valid datafor that existingCustomer PO number
DT - BK sameCustomer.
DuplicateCustomer PO using from MuleSoft for Flat file
3.
1. Navigate
Magento to
willthat particuar
recevice Flat DT
file
Customer
Customer delivery
pagefor /DUNS for sameCustomer then it
PO - - from
Number
Verify MuleSoft
Rule No 9 -by receving should show
DUNS 4. Click on DN Credit(Open)
DuplicateCustomer PO link
GUS7053
84734000 6. Click
Duplicate
under on that
My delivery filtered
dashboard Credit
ticket no (DN DN "DuplicateCustomer PO" error
32 2.
andLaunch
observe
Credit)from DT site and Login with
for Flat file If user receive any PO field
message inCustomer
10001 5. Search
valid forMuleSoft
dataticket that
Customer
DT - BK Delivery
DuplicateCustomer number - Existed
PO using existingCustomer PO number
DUNS -3. Navigate
delivery to that
ticket number particuar DT
Customer
Customer delivery
dashboard ticket number /DUNS from MuleSoft for Flat filefor
69556810
PO - 1. Magentopage
Number will recevice Flat file differentCustomer then it
DUNS
32216 -4. Click
MuleSoft link
GUS7053
84734000 6. Click
under that for
on dashboard
My
existed
filtered delivery
Credit DN should not show any error
DT
32 - A6 ticket
and number
observe
Verify RuleforNothat
9 - by receving message inCustomer PO field
10001 5.
2. Search
Launch DT siteticket
and Login with If user receive any
DT - BK Unique delivery
DuplicateCustomer no (DN
PO using uniqueCustomer PO number
Customer valid data MuleSoft
Credit)from for Flat file from MuleSoft for Flat filefor
Customer delivery
3. Navigateticket
to number /DUNS
DUNS
PO - - 1. Magento
Number
Verify willthat
Rule page
No 10
particuar
recevice Flat DT
-by receving file existedCustomer then it
Delivery
69556810 dashboard
from MuleSoft for delivery ticket If user receives any existed
GUS4054
Customer
ticket 6. Click
Duplicate
4. on that
Click onLine filtered
Item(DN
DN Credit(Open) Credit DN should
link deliverynot show
ticket any error
number from
32216
43
DUNS - number
and observe
Credit)from MuleSoft for Flat file MuleSoft for Flat fileinPO field
message inCustomer
number-
DT - A6 under
2. My
Launchcode dashboard
DT site andproduct
Login with
69556810
same Product
5. Search - Same
for that delivery ticket as delivery ticket field then it
32216 valid
2nd data
line item
existing number
3. Navigateusingto delivery ticket should shows a "Delivery
DT - A6
delivery 1. Magento
number /DUNSwillthat particuar
recevice Flat DT
file
Verify
dashboard
from
Rule
MuleSoftpagefor Duplicate Line ticket number already used"
No 10Number
- Duplicate Line
ticket
Delivery 6. Click
Item(DN
4. on that
Click onCredit)fromfiltered
DN Credit(Open) Credit
MuleSoft DN
link for error
If usermessage
receivesinany Delivery
unique
number
Customer Item
and observe
Flat fileMy dashboard ticket number field.
ticket
product under
2. Launchcode DT site and Login with delivery ticket number from
DUNS
number- -Product
5. Search for - Should
that not ticket
delivery be Sameno MuleSoft for Flat filein
code-
69556810 valid
productdataas 2ndticketline item
unique
07585600 using
3. delivery
Navigate to number DT delivery ticket field then it
32216
delivery 1. Magento
/DUNS Numberwillthat particuar
recevice Flat file shouldn't show any error
1600
DT - A6 dashboard
from MuleSoftpage
ticket 6.
4. Click
Click on
onDTthat
DNsite filtered Credit
Credit(Open) DN message
link in delivery
If user receives sameticket
product
number 2.
andLaunch
observe and Login with number field.
again under My
valid data dashboard code as 2nd line item from
same 5. Search for that Duplicate
3. Navigate to that particuar DT Line MuleSoft for Flat filein
product
product Item using delivery
dashboard page ticket product code field then it
code-
code 1- number /DUNS Number
4. Click on DN Credit(Open) link show a "Duplicate Line Item"
07585600
under My dashboard filtered Credit DN error message on product
1600
1600 and observe
5. Search for that Duplicate Line code
If userfield
receives different diff
Item(Should not be Same product line item from MuleSoft for
product as 2nd line item) using delivery Flat filein product code field
code 2- ticket number /DUNS Number then it should not show any
07756788 6. Click on that filtered Credit DN error message on product
3261 and observe code field
01788 2. Launch
DUNS DT site
number and Login
- DUNS number with
valid
Customer field is empty data
DT
DUNS - A6- 3. 1. Navigate
Magento to
willthat particuar
recevice Flat DT
file If user reveives
Verify Rule page
No 12 -
24472631 dashboard from MuleSoft
InvalidCustomer(DN Credit)from
InvalidCustomer DUNS
01707 4. Click on
2. Launch forDN Credit(Open)
DT Flat and Login with number in DUNS number
site file link
DUNS MuleSoft
under
valid My
data dashboard field from MuleSoft for Flat
number - DUNS
5. number
Search for - ValidCustomer
that InvalidCustomer filethen it should show
DT - A6 3. Navigate to that particuar DT
24472631 DUNS using number
delivery
dashboard page ticket number "InvalidCustomer"
01788 1.
6. Magento
Click
Verify on
Rule will
that recevice
filtered
No Credit(Open) Flat
Credit
14 -No delivery file
Customer 4. Click
from on DN
MuleSoft for validCustomerlinkdate emptyCustomer DUNS
DUNS and
(DN
underobserve
Credit)from MuleSoft for Flat field
DUNS - 2. Launch DT site and Login with number in DUNS number
file
My dashboard
number
24472631 valid - 5. Search for that empty DUNs
datadate field from MuleSoft for Flat
DUNS Delivery
numberCustomer - if delivery
using date field filethen it should show
delivery
01707 3. Navigate to that particuar DT
is empty
number ticket number
dashboard page "InvalidCustomer" error
field is 1.
6. Magento
Click on willfiltered
that receviceCredit
Flat file
DT
"""Custo- A6 4. Click
MuleSoft for no delivery linkdate field
empty and
underobserve
My DTdashboard If user reveives validCustomer
mer 2. Launch
Verify Rulefor site
Nothat14 and Login with
- Delivery date DUNS number in DUNS
DUNS - valid 5. Search
data validCustomer
DUNS (DN
24472631 using
3.
Credit)from
delivery
Navigate
MuleSoft
to ticket number
that particuar
for Flat number field from MuleSoft
DT
Customer
number - file
/DUNS Number for Flat filethen it should not
01707
DUNS - 1. dashboard
Magento page
69556810 DT - 4.6. Click
Verify
Click on
Rule that
on DN filtered
No Credit(Open) Credit
15 - No line item DN
link show any error message on
24472631
32216 from
and
(DN MuleSoft
observe
Credit)from for delivery date
MuleSoft for Flat DUNS number field
A6
01707 under
2. My DT
Launch dashboard
site and Login with If user receive the form
DeliveryDT 5. file
Search for that no delivery date without any delivery date
valid
Productdata
Code -ticket
if product code
date
- A6 - if using
3. delivery
Navigate number
to that particuar DT from MuleSoft for Flat file
delivery field
/DUNS is epmpty
Number then it should show "no
Delivery dashboard 1. Magento page
date field
date - if 4. 6. Click
Verify
Click on
Rule that
on DN filtered
No Credit(Open) Credit
15 - No line item DN
link delivery date" error message
is empty from
and MuleSoft
observe
(DN Credit)from for No line item
MuleSoft for Flat on delivery date field.
delivery
Customer under 2. My DT
Launch dashboard
site and Login with
date file
DUNSfield - 5. Search
valid
Productdata for that delivery date
Code -ticket
if product code
If user receive the form with
is has
24472631 3. using
Verify delivery
Rule
Navigate NO 19
to that - number
Total quantity
particuar DT any valid delivery date from
valid field
/DUNS is has
exceeds any
Number
total products
eaches threshold - MuleSoft for Flat filethen it
01707 dashboard
1. Magento page
daliveryDT 6. Click
Requires
4. Click on that filtered
on DN Credit(Open) Credit DN
link should not show any error
Customer
date from
and MuleSoft
observe
Verification for line
(DN Credit) from items message on delivery date field
-DUNS A6 - under 2. My DT
Launch dashboard and Login with If user receive the form
site file
Product MuleSoft
5. Search for Flat
for that No line item without any line items from
24472631
Customer valid
Eaches data
- more ticket
than 50 eaches
Code
01707 - if using delivery number MuleSoft for Flat filethen user
DUNS - 3.
product 1. Navigate
Magento
/DUNS
Verify Number
Rule
to
willthat
NO 19 -
particuar
recevice
Total Flat DT
file should show " Product line
quantity
24472631 DT dashboard
from pagefor exceeds total
MuleSoft
code A6 field 6.
-01707 Click
Click on
exceeds
4. on that
total
DNeachesfiltered Credit
threshold
Credit(Open) DN
link - items are missing "error
is empty
Customer under eaches
and observe
Requires message
Product DT 2. My DT
Launch dashboard
siteCredit)
and Login with
DUNS
Code - Verification (DN from
A6 - if 5.
-24472631 Search
valid for that line items using If user receive the form
datafor
MuleSoft Flat file /DUNS
product
Product delivery ticket number DT50 without any line items from
01707field 3.
code
Navigate
Eaches
Number - Lesstothan
that particuar
or equals to MuleSoft for Flat filethen user
Code - ifDT dashboard
eaches page If user receives eaches more
is has
product any 6.
4. Click
Click on that
on DN filtered Credit DN should not show any error
-products
A6 1.
andMagento
observe willCredit(Open)
recevice Flatlink file than 50 from MuleSoft for Flat
message.
code field under
Product from MuleSoft My dashboard filethen it should show "The
is has any 5. Search for that exceeds
Code - if 2. Launch DT site and Login with total total quantity exceeds the
products eaches
product valid data using delivery ticket allowable quantity of 50
Eaches- number /DUNS Number
code field 3. Navigate to that particuar DT eaches.
If user receives eachestomore
Do you want
More 6. Click on
is has any dashboard page that filtered Credit DN approve and submit
than 50 from MuleSoft thefor Flat
than 50 and observe
products 4. Click on DN Credit(Open) link form?" error message
filethen it should show "The
Eaches - under My dashboard total quantity exceeds the
Less than 5. Search using delivery ticket allowable quantity of 50
50 or number /DUNS Number eaches. Do you want to
equal to 6. Click on that filtered Credit DN approve and submit the
50. and observe form?" error message
Verify whether user able to launch

DT site.
1. Open the browser and enter the User should be able to launch
site URL DT site. Working asPass
Verify whether DT user is able to

directly login to DT dashboard. DT user should be able to
1. Launch the app and login with directly login to DT dashboard
the valid credentials. page. Working asPass
Verify if DT administrative is able
to login to the site
1. Launch the app and login with DT administrative should be
Customer the valid
Verify credentials
Customer for DT
PO does not meet redirect to Select the DT
DUNS - Verify by clicking
administrative. on
pattern by giving invalid patternany DT on account to proceed page Working asPass
05749904 account
1. Launchto theproceed
app . page
90069 Verify
1. Launch
2. Login bywith
clicking
theDTapp on.Create DN
Administrator
Customer Debit under My task or TODOs
DT
Banner- BK - 2. Login
valid datawith DT Administrator
PO - section
3. Click on any DT and navigate to User should be redirected to
Go Puff valid
1.
data
Launch the app .
Should
Customer that
3. particular
Click on any DTDT Dashboard page particular DT Dashboard page. Working asPass
start 2. Login with DT Adminitrator/DT
DUNSwith - 4. Click
Verify
with
on Create
Customer
valid data
DN Debit
PO does not meetunder
prefix
05749904 My tasks
pattern byor TODOs
giving section and for
based 3. Click on any DT-invalid
and pattern
navigate to If user give any invalid pattern
90069 on redirected
GopuffCustomers
that
to
particular
DN
DT
Delivery
Dashboard
ticket
page
the
DT - BK page
1. Click
Launch the app DN. Debit under inCustomer PO text field and
Customer
Customer 4.
5. Enter on
anyCreate
DUNS number andvalid User try toshould
submitable
the to redirect
form then to
PO - - 2.
My Login
tasks with
or DT
TODOs Adminitrator
section "DN
Banner
banner
Should select
Verify
data any store
If user 6. Enterthe
try to submit user should get "Customer PO Working asPass
- Delivery ticket" page.
Go
group Puff Verify
delivery
form Customer
date and
without PO does
delivery
giving not meet
ticket
anyCustomer does not meet pattern." error
not start
Customer 3. Click
pattern on
by any
givingDTinvalid
and navigate
patternto for message.
followed
with no.
PO inCustomer PO field for
DUNSGUS
with - that
6.
particular DT Dashboard page
GopuffCustomers
Enter any
GopuffCustomers. invalidCustomer PO (ex. starts with Gus and has 6
and
05749904have 4.
1. Click
Launch on Create
the app DN
. Debit under
character
6 digits number
(ex.
My starts
task and
orwithclick
TODOs on validate
Gussection
and hasand 6 and char(GoPuff),
If user give anyPOinvalid
start pattern
90069
s(POI6543
or digits 2. Login
submit with
button
char(GoPuff), DT Adminitrator/DT
PO -start digits/letters, length.) Working asPass
DT - BK redirected
with to DN
valid data Debit Entry page for GopuffCustomers
21) digits/letters,
5. Enter any length.)
DUNS number and to inCustomer PO invalid
field and try to
PO - 3. Click on any DT and navigate
[{"prefix":"GUT","condition_group" If user give any pattern
It should
Should select
that any store submit
particular DT Dashboard page for GopuffCustomers the form then user
give ivalid :18}
6. Enter any invalidDN pattern under should get "Customer POtry
does
start
Customerwith 4. Click
1. Launch on Create
the app . Debit inCustomer PO field and to
pattern
GUS and- ofCustomer
My task with PO
or TODOs number and
section and click not meet pattern."
submit the form then usererror
Banner
error 2.
on Login
validateto DT Adminitrator/DT
and submit
have
Go Puff 6 redirected
with valid dataDNPO - Debitbutton
Entry page message.
should get "Customer PO does Working asPass
digits(GU Verify
5. Enter Customer
any DUNS does
number notandmeet not meet pattern." error
Customer 3. Click on
pattern any
by store
givingDTinvalid
and navigate
patternto for message.
S998876)
DUNS - select
that any
particulargroup)
DT Dashboard page
It should AEFIS(Banner
6. Enter valid pattern Customers
ofCustomer (ex. starts with Gus and has 6
05749904 4. Click
1. Launch on Create
the app DN Debit under
. on validate char(GoPuff), PO start
accept
90069 PO
My number
task with and
or TODOs click
section andvalid If user try to submit the form
the 2. Login DT Adminitrator
DT -value.
BK
Customer
and
Verify
data
submitto
redirected button
DN - Debit
If user try to submit Entry digits/letters, length.)
the page without giving anyCustomer
Working asPass
PO -No Verify
5. Enter
form Customer
any
without DUNS PO
giving does
number notand
anyCustomer meet PO inCustomer PO field for
Banner - 3. Click
pattern on any
by store
givingDTinvalid
and navigate
patternto for GopuffCustomers then user
value
AFEES select
PO
that any
inCustomer
particulargroup)PO field
DT Dashboard for page
AEFIS(Banner
6. Click on
AEFIS(Banner validate
group) andCustomers
submit
Customers. should get an error message
Customer 4.
1. Click
Launch on Create
the app DN
. Debit under
DUNS - button
(ex.
My without
starts
task orwith
TODOs giving
Gussection
and hasand 6 "Customer
If user give POanydoes notpattern
invalid meet
2. Login
anyCustomer with
char(AEFIS(Banner DT
PO Adminitrator/DT
number.
group)Entry pattern"
), POpage for AEFIS(Banner group) Working asPass
69556810
Customer redirected
with valid to DN - Debit
data
32216 start
5. digits/letters,
Enter any DUNS length.)
number and to Customers inCustomer PO
Banner - 3. Click on any DT and navigate
[{"prefix":"GUT","condition_group"
DT
AFEES- A3 select
that particular DT Dashboard page field
any store and
If user tryany
give to submit the
invalid pattern
PO - :18}
6. Enter any invalid pattern form then user should get
Customer 4.
1. Click
Launch onthe
Create
app DN
. Debit under for AEFIS(Banner group)
PLB12345
Customer
DUNS - ofCustomer
My task with PO
or TODOs number and
section and click "Customer PO does
Customers inCustomer PO not meet
6789
DUNS - 2.
on Login
validate andDTsubmit
Adminitrator/DT
button pattern." error message. Working asPass
69556810 redirected
with valid datato DN - Debit Entry page field and try to submit the
69556810
32216 5. Enter any DUNS number and to form then user should get
Customer
32216 3. ClickRule
Verify on any
No 1DT- and navigate
IfCustomer
DT - A3
Banner select any store page "Customer PO does not meet
DT -- A3 -
PO
that
groups
6.
particular
Enter dont
valid
DT prefix
have
pattern
Dashboard(pattern)
AFEES
PO - 4.
1. Click
Launch onthe
Create
app DN
. on Debit under pattern."
ofCustomer If user tryerror message.
to submit the form
VON1234
Customer PO
My number
task with and
or TODOs click validate
section and (AEFIS - Starts with 'VON' - 9
without giving anyCustomer
12334558
56789 2.
andLogin
submitto DT
buttonAdminitrator/DT
DUNS
9987 - redirected
with valid data DN - Debit Entry page digit}, PO inCustomer PO field for Working asPass
69556810 5.
3. Enter
Click on anyanyDUNS
DT andnumber and to AEFIS(Banner group)
navigate
32216 select
that particular DT Dashboard page Customers then user should
any store
DTIt- A3 6.
4. Click
Click onon validate
Create DN and submit
Debit under get an error message
PO - No
should button without giving
My task or TODOs section and "Customer PO does not meet
data
give anyCustomer
redirected to DN - Debit Entry page pattern"
PO number. Working asPass
"Custome 5. Enter any DUNS number and If user try to submit the form
r PO does select any store with/withoutany data then it
not meet 6. Click on validate and submit should not show any error
pattern" button with/without any data message for Customer PO
error. giving anyCustomer PO number. field. Working asPass
90069 PO inCustomer PO field for
It should 3. Click on any DT and navigate to Greater than or Lessthan 9
GopuffCustomers.
DT
give- BK error that particular DT Dashboard page inCustomer PO text field and
PO - 1. Launch the app .
message
It should 2. 4. Click
Login on Create DN Debit under try to submit the form then
GUS3458
as
"Custome Verify
My taskIf with
user
ordata
DT Adminitrator/DT
try
TODOs tosection
submit and the user should get "Customer PO
give
76321 error with
form valid
with greater than
"Custome
r Banner - 3. Click on any DT and navigate to larger than maximum length"
message redirected to DN - Debit Entry page
rasPO 6charCustomer
5. Enter any DUNS PO number
inCustomer and PO
AFEES that
field particular
for DT Dashboard
GopuffCustomers. page error message.
larger
Customer
"Custome select any store Debit under Length of PO should be
than It 4.
1.
6.
Click
Launch
Enter
ontheCreate
greater appthan
DN
. or equal
DUNS
rshould
PO
"Custome - My
2. task with
Login or TODOs
DT section
Adminitrator/DTand to 9 certain
If user try to submit the form
maximum
69556810
larger and
Verify click
redirected on
If user validate
to try
DNto and
submit
- Debit submit
the page ex.AEFIS
Entry with giving - 9less
digit
than
rgiveBanner
length" error - with
button valid data Go Puff - 6 Digits
32216
than
AFEES
message
form
5.
3. Enter
Click
with less
any than
DUNS
on any DT
9charCustomer
number
and and
navigate 6CharCustomer
to If user try to submit PO the form Working asPass
DT
maximum-
Customer A3 PO inCustomer
selectparticular PO field for
any storeDT Dashboard page inCustomer PO fieldthan
for
as
PO - - that AEFIS(Banner group) Customers. with giving greater
length"
DUNS
"Custome 6.
4. Enter
Click less
onthe than
Create 6char
DN and Click GopuffCustomers
Debit under 6CharCustomer PO then user
VON1234
69556810 1.
on Launch
Verifyvalidate
If userand app
try to . submit
submit button
the should get an error message
r567PO My
2. task with
Login or TODOs section and
DTanyCustomer
Adminitrator/DT inCustomer PO field for
32216 without giving Debit EntryPOpage "Customer PO does notuser
meet
Customer form
larger redirected
with
number.
with
valid
greater
to DN
data - than GopuffCustomers
pattern"
then
Working asPass
DT
than - A3 - 9charCustomer PO number
inCustomer and PO
Banner
PO - It 5. 3.
field
Enter
Click
for onanyanyDUNSDT and
AEFIS(Banner navigate
group) to should get an error message
maximum
Go
shouldPuff select that any storeDT Dashboard page "Customer PO does not meet
particular
VON8765
length"
Customer Customers.
6. Enter greater than 6char and pattern"
give
43215678 error 4. 1. Click
Launch on Create
the appand DN Debit under
. submit If user try to submit the form
DUNS
message My - Click on
task validate
or TODOs section andbutton (ex.
withstarts
givingwith
less Gus
thanand has 6
05749904 2. Login
without with
giving DT Adminitrator/DT
anyCustomer PO char(GoPuff), PO start
as redirected
with valid to DN - Debit Entry page 9CharCustomer PO
data
90069
""Custom number. digits/letters, length.) Working asPass
It - BK 5.
Customer
DT 3. Enter
Click on anyanyDUNSDT andnumber and to inCustomer PO field for
navigate
er
DUNS PO - select
should any storeDT Dashboard page AEFIS(Banner group)
PO
larger- 12 that
24472631 Verify
6.
particular
Enter RulelessNo 2 - 9char
than IfCustomer
andunderPO Customers then user should
Click
give error 4. Click on
doesn't haveCreate
any DN Debit
specific length If user try to submit the form
than
05608
message My on validate
task or and
TODOs submit
section button
and get
withan errorgreater
giving message than
maximum 1. Launch
without the
giving app .
anyCustomer
DT
as - A3 redirected2. Login to DT
with - Debit Entry page 9CharCustomerdoes
DNAdminitrator/DT PO "Customer PO PO not meet
length"""
Delivery
""Custom number.
5. Enter any DUNS number and pattern"
inCustomer PO field for Working asPass
Customer
It - with valid data
date
er PO - select
DUNS
should
2013-12- 3. Clickany
Verify on store
Date any DT and
outside navigate to AEFIS(Banner group)
retailer's
larger
24472631
give 6. Enter
Verify
error that Rulegreater
particular No 4 than
- Date 9char and
outside page Customers then user should
08
than (YY- operation
Click on dateDT
validate (DN
and
Dashboard
Debit)
submit
05608
message
MM-DD)
retailer's
4.
1. Click
Launch
operation
ontheCreate
app DN
. Debit under get an error message
date (DN button
Debit)
maximum
DT - A3 -My
as without
Select
taskany giving anyCustomer
less than
or TODOs start and
section PO "Customer PO does not meet
(Start
length""" 2. Login
number. with DT Adminitrator valid
Delivery
"Custome
date
ofCustomer
redirected
data toHierarchy1.
DN - Debit LaunchEntry page pattern" Working asPass
date
r2013-12-
PO
Customer - the
5. app
Enter .any DUNS number and to If user try to submit the form
2013-12- 3.
2. Click
Login on any
with DT4DTAdminitrator
and navigate valid
larger
DUNS
07 it - select
Verify
that particular DT Dashboard page with/without any data then it
any
Rule store
No - Date outside
08
than(YY-
24472631 data
6. Click
retailer's on validate
operation and
date submit Debit) should
(DNunder not show any error
Should
MM-DD) 4.
3. Click
Click on
on Create
any DT DN
and Debit
navigate to If user select delivery dates
maximum
05608
not button
-MySelect
task with
any any data/without
greatersection
or TODOs than end anddate message for Customer
less than start or greater POthan
(Start
length" that
giving particular
anyCustomer DT Dashboard
PO number. page
DT
date
- A3 ofCustomer
accept redirected
4. Click onthetoHierarchy
DN -DN
Create Debit Entry
Debit page end date(Customer Hierarchy) Working asPass
under
field.
Delivery
less than 5. 1. Launch
Enter any app .
DUNS section
numberand and and try to submit the form
2013-12-
date - My
2. task with
Login or TODOs
DT Adminitrator valid then then user should get "
start
07 it date select
redirectedany store
to DN - Debit Entry page
9999-12-
fromCust
Customer data
6. Select anyDUNS
less than start and
or Date outside retailer's
Should
31 (YY- 5.
3. Enter
Click onanyany DT number
and navigate to
omer greater
DUNS - select any store
not than end date and Click operation
If user selectdate " errordates
delivery
MM-DD)
hierarchy)
24472631 Verify that
and particular
Validate
Rule Noless DT
and Dashboard
submit
4 - Datestart page
button.
outside message. Working asPass
accept
(End date 6. 4. Select
Click onany Createthan DN Debit and
under less than start (Customer
05608
less than Click retailer's operation
andorValidate date (DN Debit)
9999-12-
DT - A3 My task
-button.
Verify TODOs and
by selecting sectionsubmit
any in and
Hierarchy) and try to submit
start
31 it date redirected to DN -end
Debit Entry page the form then then user
Delivery
fromCust between
(Open start
Magento orAdmin date
--> Uniliver should get " Date outside than
Should
date - 5.
1. Enter
Launchany theDUNS .number -and
appHierarchy If user Select any greater
omer
not CremeCustomer
select any store search retailer's operation date "
2013-12-
hierarchy) 2.
forLogin
that with DT Adminitrator valid end
particularCustomer) error
date ofCustomer
message. Working asPass
accept
08 and 6. Select any greater than end date Hierarchy (Customer
data
greater
9999-12- ofCustomer
3. ClickDelivery
on any Hierarchy
DT and and Click to Hierarchy) and try to submit
Customer
than date Verify
and Validate anddate in navigate
submit thebutton.
future the form then then user
31
DUNS it - that particular DT Dashboard
(DN Debit) page
fromCust
should (Open
4. Click Magento
on Create Admin
DN -->
Debit Uniliver
under should get " Date outside
24472631 CremeCustomer
omer 1. Launch the appHierarchy .
accept
05608 In My 2. task with
Login or TODOs section andvalid retailer's operation date "
DT Adminitrator
- search
hierarchy)
between for that particularCustomer)
to DN - Debit Entry page error message. Working asPass
DT - A3 redirected data
start
Delivery and 5. 3. Enter
Click on anyanyDUNSDT andnumber and to If user select delivery dates in
navigate
end
date date select
that particular DT Dashboard page between start or end
any store
ofCustom
(MM-DD- 6. 4. Select
Click onany inbetween
Create DN Debit start or
under date(Customer Hierarchy) and
er
YY) it end date and Click
My task or TODOs section and and Validate try to submit the form then it
Hierarchy.
Should and
redirected to DN - Debit Entry page show any error message
submit button. Working asPass
not 5. Enter any DUNS number and
accept select any store
future 6. Select future delivery date and Standard check - Future
delivery Click and Validate and submit delivery dates should be
dates. button. disabled in Calender Working asPass
84734000
84734000
system
10001 that particular DT Dashboard page
10001
should 4. Click on Create
DT
DT -- BKBK if Delivery ticket no DN Debit under
missing
accept
Delivery My task or TODOs
1. Launch the app . section and
Customer
Delivery redirected to DTDNAdminitrator
- Debit Entry valid page If user selects delivery date
ticket
PO - is 2. Login
Verify with
byanyentering the
date
number - 5. Enter
data DUNS number and greater than or equal to 90
GUT7053
older existingCustomer
select PO number of
Empty
32 - it90 3. Click on any DT and navigate to days from current date and
any
sameCustomer
store
than
(it 6. Select
that delivery
particular DTdate older than try to submit the form then
Dashboard
should
days from be 1. Launch
90 days the current
from app . date andpage user should get "Delivery date
shpould
unique 4.
2. Click
Login on Create DN Debit under
current
not Click
My andwith
task
DT Adminitrator
orValidate
TODOs and sectionsubmit
and
valid less than allowable days of
for
date
Customer data
button.
Verify by entering the current date " error message. Working asPass
accept
sameCust if redirected
3. Click on any to DN DT-PODebit
and Entry page
navigate to If user doesn't enter any
DUNS
delivery - existingCustomer
5. Enter any DUNS number
number and of
omer
84734000 that particular
differentCustomer DT Dashboard page delivery ticket number and try
ticket
Customer
(It should select
4. Click any store
on Create DN Debit under to submit the form then user
10001
number 6. 1. Launch
Click on the app
Validate . submit
DUNS
not
DT - BK
- My task with
2. Login or TODOs section andvalid should get " delivery ticket
DTdelivery
and
Adminitrator
field
24472631
accept is in button
redirected without
to DN - Debit ticket Entry page number is missing" error
Customer
empty) data
number
12614
case
PO of 5.
3. Enter any DUNS number and to message.
If user give any Working asPass
DT -- BK
sameCust
Customer
Click on
select any
any
store
DT and navigate
existingCustomer PO number
GUT7053
Customer that particular
Duplicate deliveryDT Dashboard
ticket noPO page for sameCustomer and try to
omer
DUNS
32 PO
-- 6.
4. Enter existingCustomer
DUNS
Delivery
for
24472631 1. Click
Launch
number
ontheCreate
app DN
inCustomer . PO Debit under
text box submit the form the user
(It should
24472631
ticket My task
2. Login or
with TODOs section
DT Adminitrator and valid
sameCust
12614
accept in and click
redirected onto DN - Debit Entry page should
Validate and submit get "Duplicate
If user give any PO
12614
number-
omer) data
button. number " error message. Working asPass
DT
case
DT -
- BKBK
of 5. Enter any DUNSand number and to existingCustomer PO number
80622235
Delivery 3. ClickRule
Verify on any
No 9DT- by navigate
giving Unique
sameCust
product
03 (It select
that any
particular store DT (DN
Dashboard page for differentCustomer and try
ticket
omer PO delivery
6. Enter ticket no
existingCustomer Debit)
code-
should
number- 4.
1. Click
Launch ontheCreate
app DN. PO Debit under to submit the form then user
PO
for
1st
not line number
My inCustomer
task with
or TODOs section text
and box should not get any error
8062265
diffCusto 2. Login
and click on DT Adminitrator valid
item
accept
(It should
- in redirected
data to DN - Debit Entry page message,
Validate and submit If user giveit any
should accept the
existing
mer)
07585603
case of button.
Duplicate
5. Enter anyLine Itemnumber and
DUNS form if no errors are there. Working asPass
accept
Customer
1140 in 3.
1. Click
Launch on any
the DT and
app . navigate to delivery ticket number in
same
case of select
that any storeDT Dashboard page delivery ticket text field and
particular
DUNS
2nd
existing line - 2.
6. Login
Enter with
existingDT Adminitrator valid
unique
24472631
item - 4. Click on
data Createdelivery
DN Debit ticket
under try to submit the form the
delivery
Customer
delivery number
My taskon in delivery
or any
TODOs ticket
section text
and to user should get "Duplicate
box
05644
07585603
ticket 3. Click
and click on DT and
Validate navigate
and submit
DUNS
ticket
1140
- redirected
that particular to DN DT- Dashboard
Debit Entrypage page delivery ticket
If user give anynumber
unique " error
number)
24472631
number button.
5. Enter any DUNSDN number message. Working asPass
DT
(It
12614
- A3
should 4. Click not
Eaches on Create
in full boxes Debit and
under delivery ticket number in
in
Product
not select
My any
task orthe store
TODOs delivery ticket field and try to
DT - BK
delivery 1.
6. Launch
Enter any app .section
unique delivery
and
ticket
code
accept
product
- redirected
2. Login with to DTDNAdminitrator
- Debit Entry valid page submit the form the user
ticket
07756700
incase number in delivery ticket text box shouldn't get error message
code
number 1-of 5. Enter any DUNS number and
data
and click on Validate and submit and from
2204
if we
Customer
07684010 select
3. Click any
on store
any DT and navigate to If user giveshould
same be submitted
product
field)
(Eaches
receive button.
Verify
6. Enter Rule No 11code
product -by giving if no error are there.
Eaches code as 2nd line item in
in product Working asPass
DUNS
0125 - that
Per
same
24472631Box is in fullparticular
code boxes
field and (DN DTDebit)
Dashboard
select the product
page
product code field and try to
product
24) 4.
1. Click
Launch on Create
the app DN Debit under
. product code submit the form the user
product
05644
code 2- and
My again
task with give
or TODOs same section andvalid
code as 2.
in Login
2nd line toNoDT
product11Adminitrator
code Entry
field and
07684048
Eaches
Verify
redirectedRule DN --Eaches
Debit in fullpage should get "Please remove
second
DT
5116 - A3 -
Customer
data
and
boxes
5. click
Enter (DN on
any Validate
Debit)
DUNS and
number submit
and to duplicate
if user enterproduct
eachescode or line
other
50
line
Product item) 3. Click
button.
Eachesany on any
- Eaches DT and
should be navigate items " error message. Working asPass
(It
DUNS
(It should
should - select
that particular storeDT Dashboard than multiples of "eaches per
code
accpet
24472631 - in multiples
6. Enter of "eaches
product code per
in box" page box" then user should get
product
not
07756700 4.
1. Click
Launch ontheCreate
app DN
. the Debit under
case
01788
accept of in code
My field
task or and
TODOsselectsection product
andvalid "Eaches not in full boxes"
2204
diff line 2. Enter
7. Login withother DT Adminitrator
than multiple ofpage [{"multiples":"eaches"}] - it
case
(Eaches of redirected
data to DN - Debit Entry if user enter eaches multiples
level
DT
eaches- A6 eaches
5. Enter in
anyeaches
DUNS box and
number click on should accept only multiple
and to of "eaches per box" then user of
Per
items) Box is 3. Click on
Validate andany DT and
submit navigate
button. eaches per box Working asPass
other
24) select any storeDT Dashboard page shouldn't get any error
that particular
than 6. Enter
4. Click on product
CreatecodeDN Debitin product
under message and form should be
DUNS
multiples code field and select the product submitted if no errors.
Eaches
number -- My task or TODOs section and
of
48 7.
redirected to DN - Debit Entry page [{"multiples":"eaches"}] - it
Enter multiple of eaches in
24472631
"eaches eaches
(It should
01788 5. Enterbox anyand
InvalidCustomer DUNS click on Validate
number and should accept only multiple of
per
accept box") in and
selectsubmit
any the button.
store eaches per box Working asPass
(It should 1. Launch app .
case
not of 6.
2. Enter
Login withproduct code in product
DT Adminitrator valid
multiples
accept code
data field and select the product if user submit the form with
of
incase of 7.
3. Enter
Click on multiple
any DTofand eaches in to eaches multiples of "eaches
navigate
"eaches
invalid eaches
that particular DT Dashboard page per then it should not any
box and click on Validate
per
Dunsbox") and submit
4. Click button.DN Debit under error
on Create If usermessage.
enter InvalidCustomer Working asPass
number My task or TODOs section and DUNS number in DUNS
in DUNS redirected to DN - Debit Entry page number fiels and try to submit
number 5. enter InvalidCustomer DUNS the form then the user should
filed) number in DUNS number fiels and get "InvalidCustomer " error
click on validate and submit form. message. Working asPass
01707
(It should 2. Login with DT Adminitrator valid
not
DT - A6 data
accept
DUNS 3. ClickRule
Verify on any
No 12 DT -and navigate to
by giving
Customer
incase of- that particular DT Dashboard page
number
DUNS validCustomer(DN Debit)
- 4. Click on Create DN Debit under If user submit the form
empty
69556810 1. Launch the app .
21339648
Duns My task with
or TODOs section andvalid withoutCustomer then it
32216
02300 2. Login
Invalid Product DT Adminitrator
number
(It should redirected to DN - Debit Entry page should show
DTDUNS
in - A8 data 1.
5. Launch
enter the app .
InvalidCustomer DUNS to "InvalidCustomer" error
accept
Product 3.
2. Click
Loginon anyDTDTAdminitrator
with and navigate valid
number
incase number in DUNS number fielspage
and message on DUNS number
code
filed) - of thatdata
click
particular DT Dashboard
on validate and submit form. field Working asPass
valid
04100005 4. 3. Click on
on Create
ClickRule any DT DNand Debit under
navigate to If user enter validCustomer
Duns Verify
My task No
or TODOs 13 - by giving valid
section andpage DUNS number in DUNS
3152 that
Productparticular
code DT Dashboard
(DN Debit)
number
Inavlid redirected
4. Click to
onthe DN
Create - Debit Entry page number fiels and try to submit
Customer
in DUNS 1.
5. Launch
enter app DN
validCustomer . Debit under
Product
DUNS - My 2. task with
Login or TODOs section andvalid the form then the user should
DUNS
DT Adminitrator
number
code number
redirected in DUNS number
to DN - Debit Entry fiels and
page get a auto pop of that
21339648
filed) data
click on validate and submit
(It
02300 should 5. 3. Enter
Click on anyanyDUNSDT andnumber and to particularCustomer
navigate
form. Working asPass
give
DT - A8 error select any storeDT Dashboard page If user enter Invalid Product
that particular
message
Product 6.
4. Enter
Click invalid
on Create product
DN Debit code in
under code in Product code field and
DUNS
as No delivery
product code date
field try to submit the form the
code
number - - My 1. task orthe
Launch TODOsapp .section and
"Inavlid
07756700 7. click
redirected on Validate
to DT and
DNAdminitrator submit
- Debit Entry validpage user should get "Invalid
21339648
product") 2. Login with
button. product " error message. Working asPass
1542
66600 5. Enter any DUNS number and
data If user enter valid Product
Inavlid
DT - A8 select 3. Clickanyon store
any DT and navigate to code in Product code field and
Product
Delivery 6. Enter
that valid
particular product
DT code in page try to submit the form then
DUNS
code Verify
product Rule
code 14 -Dashboard
Nofield by selecting
date
number - - 4. Click on
delivery Create
date (DN DN
Debit)Debit under the user should get auto
(It
DUNS
Empty should 7.
My click on
task ortheValidate
TODOs and
sectionsubmit
and populated of that particular
21339648
accept) 1. Launch
button. app .
number
It
66600should- redirected
2. Login with to DTDNAdminitrator
- Debit Entry validpage product.
If user try to submit the form Working asPass
21339648
not
DT
66600 - A8 5. Enter any DUNS number and
data without selecting any delivery
accept
Delivery if select any store
any DT and navigate to date in delivery date box then
DT - A8 3.
delivery No
6.
Click
line on
without item.
selecting any delivery
date
Customer
Delivery - that
1. particular
Launch the DT Dashboard
app . page user should get "Delivery date
date
DUNS
(MM/DD/ field date click on Validate and submit is a mandatory field."the
error
DUNS
date
Customer
is -
empty. - 4. 2. Click
Login
button.
on Create
with DT DN Debit under
Adminitrator valid If user
message
try to submit form
Working asPass
number
YYYY)
24472631 - My task or TODOs section and with selecting any delivery
(MM/DD/
DUNS
21339648 - data
It
01707
YYYY)should redirected
3. ClickRule to DN
on any DT--and
Debit Entry page
navigate date in delivery date box then
84734000
66600
accept if
DT Verify
5. Enter any NoDUNS15 by giving
number anyto user shouldn't get any error
and
Product
10001
DT that particular DT Dashboard page
-DT A6-- A8
delivery
code -
A8
line
select
4.
item
Click any
on
(DN
store
Create
Debit)
DN Debit under message and form should be
Delivery
date
Product is 1.
6. Launch
Select the
any app
delivery. date and
click on submitted if no errors are
Empty
Delivery
date - My
2. task with
Login or TODOsDT section
Adminitrator valid
Customer
selected
code
It -
should Validate
redirected and
to DN - Debit Entry page there.
submit button. Working asPass
date
(MM/DD/
DUNS - - data
07756700
not
(MM/DD/ Product
5. Enter not
any listed
DUNS number and If user is trying to submit the
YYYY)
84734000
2887 3.
1. Click
Launch on any
the DT and
app . navigate to form without selecting any
accept
YYYY)
Product if select any store
10001
(It should that
product 2.
6.
particular
Login
Click with
on
DT Dashboard page
NoDT17Adminitrator
validate and submit valid
Product
code
DT
not - -
A8 Verify
4. Click
data
Rule
on Create -Quantity
DN Debit under product
If user is code,
tryingthen user the
to submit
field
code
07756700is
- button
exceeds
My taskonwithout
boxTODOs
or Threshold - requires
section should get “Product
and to form with selecting any line item
Delivery
accept
empty 3. Click
Selecting any DT
products. and navigate is Missing” error message. Working asPass
07756700
date - of verification
1559 redirected to(DNDN Debit)
incase
GopuffCustomers DT--Dashboard
Debit Entrypage
eaches more
page product code, then user
It should 5.
(MM/DD/
product 4. Enter
Click any
on DUNSDN
Create number
Debit and
under shouldn't get any error
(Eaches
accept
YYYY) if than
select 5any
boxesstore message and form should be
code
per is - My
Box 1. task orthe
Launch TODOsapp .section and
products
Product
not 6. Click
Verify
exist redirected on
Rule validate
No
to DT 17 and
-Quantity
DNAdminitrator submit
- Debit Entry validpage submitted if not errors are
6)
date is 2. Login
button with
with there
code -
in
Eaches -
exceeds
5. Enter any
data
box DUNS
Thresholdnumber- requires
and If userinenter
the form while
product code
selected
07756700
system/N Selecting
verification
select any products.
(DN Debit)
store submitting.
that is not mapped to the Working asPass
36
1238 3. Click on any DT -and
GopuffCustomers It navigate
should be to
5
ot
(GopuffCu 6. Enter
that product
particular DTcode in product
Dashboard page retailer in the product code
(Eaches
mapped boxes
code field which is not mapped to field, and try to submit the
stomers
perthatBox -- 4. 1. Click
Launch onthe
Createapp DN. Debit under Form then user should get
to
It that retailer.
6)should My
Customer 7.
task with
2. click
Login or TODOs section andvalid
DT Adminitrator
on Validate and submit
not
Eaches - redirected
data to DN - Debit Entry page “Product not listed” error
)accept in button.5. and to message. Working asPass
30 3. Enter
Click on anyanyDUNSDT andnumber
navigate
case of
(GopuffCu select any storeDT Dashboard page
that particular
eaches 6. Enter
stomers - 4. Click on product
Createcode in product
DN Debit under
more code field
It should My task or TODOs section and If user enter enter eaches
than
accept in redirected to DN - Debit Entry page more than 5 box then user
5 7. Enter eaches more than 5 boxs
box's)
case of 8.
5. Click
Enteron anyvalidate
DUNS numberand submit.and should get error message. Working asPass
eaches select any store
are 5 6. Enter product code in product
box's or code field If user enter enter eaches as 5
less than 7. Enter eaches as 5 boxs box then user shouldn't get
5 boxs) 8. Click on validate and submit. error message. Working asPass
code
DUNS -- Food Service migration - It should
not
07756700 that
be 5 particular
box's DT Dashboard page
21339648
accept in 4. Click on Create DN
2228
02300 1. Launch
Verify Rule the
Noapp . Debit under
17 -Quantity
case
(Eaches of My
2. task or
Login with TODOs section andvalid
DT Adminitrator
DT
Food - A8 exceeds
redirected boxtoThreshold
DN - Debit- Entry requires page
per
DeliveryBox - data
verification (DN Debit)
Service
24) 5.
3. Enter any DUNS
Click on any DT and number and
navigate to
date
migration - NormalCustomers
select - it should
any storeDT Dashboard
Eaches
(MM/DD/ - that
acceptparticular
any value code in product page
-120eaches 6.
4. Enter
Click product
on Create DN Debit under
YYYY)
more 1. Launch
code field the app .
(It should
Product My
2. task
Login or TODOs
with DT more section andvalid If user enter enter eaches
Adminitrator
than
accept 5 in 7. Enter
redirected eaches
to DN - Debit than
Entry 5 boxs
page more than 5 box then user
code
box's) - data
8. Click on validate and submit.
case
07684010 of 5.
3. Enter
Click on anyanyDUNS
DT and number
navigate and to should get error message. Working asPass
Food
0040(Eac select any storeDT Dashboard page
that particular
Service
hes per 6. Enter
4. Click on product
Createcode DN Debitin product
under
Duns
migration code field If user enter eaches as 5 box
Box
number -6) My task or TODOs section and
eaches- -
-Eaches 7.
redirected to DN - Debit Entry page then user shouldn't get error
Enter eaches as 5 boxs
05749904
is 5 box's) 8. Click on validate and submit. message. Working asPass
120
90069 5.
SubEnter any DUNSMissing
– Distributor number and
NormalCu
DT - BK select
1. Launchany the
storeapp .
stomers
Delivery - 6. Enter product code in product
2. Login with DT Adminitrator valid
it should
date - code
data field If user enter eaches as 5 box
accept
(MM/DD/ 7.
3. Enter
ClickRuleany
on any value
DT -andin eaches
navigate box to then user shouldn't get error
any value Verify
8. Click on No 18
validate if
andSub -
submit.
YYYY) Verifyparticular
that Customer
Distributor DTPO
is mapped
does not meet
Dashboard page message.
If user enter DUNS number Working asPass
it should pattern
4. Click by
on giving
Create invalid
DN pattern
Debit under for and select any store, if the
Customer 1. Launch the group) Customers
AEFIS(Banner app .
not
Duns My
2. task with
Login or TODOs
DT section and store Is not mapped to any
Bannerid
accept - 1. Launch the
redirected to appAdminitrator
DN - .Debit Entry valid page Sub- Distributor, user should
number
Go Puff - data
2. Enter
Login with DT Adminitrator valid get default as “NONE”(not an
Sub-
05749904DT is 5.
3. ClickIfonany DUNS
anytryDTtoand number
navigate and
Customer
missing Verify
data
select anyuser
store submit the to error). Working asPass
Customer
90102 that particular DT Dashboard page
DUNS
Banner - form
3. without
Click on anygiving
DT and anyCustomer
navigate to If user enter DUNS number
DT - BK -
05749904
Verify
4.
PO Click
that
Customer
on
inCustomer Create
particular
PODN
PO
DT
does not
Debit
field
Dashboardfor meet
under
page and select any store, if the
Go Puff
Delivery pattern
My taskbyorgiving
TODOs invalid pattern for
90069
Customer
AEFIS(Banner
4. Click on Create
AEFIS(Banner
DN Credit under store
section
group) Customers.
group) Customers
and If userIsgive
mapped to anypattern
any invalid Sub-
date
DT -
- BK redirected
(ex.
My starts to
withDN
task ortheTODOs Gus - Debit
and Entry
has
section and 6 page Distributor,
for AEFIS(Banner user should get
DUNS
(MM/DD/ - 1.
5. Launch
Enter any
char(AEFIS(Banner app
DUNS . number
group)Entry and
), PO that mapped sub DT (not an
PO -
ForCusto
05749904 redirected
2. Login
toDT
with
DNAdminitrator/DT
- Credit group) Customers inCustomer
YYYY)
Should select
start
page any store
digits/letters, length.) error).
PO field and try to submit the Working asPass
mer
90102 with valid data
Customer
start
Banner with - [{"prefix":"GUT","condition_group"
5. Enter any DUNS number and form then user should get
DT - BK
Banner - 3. Click on any DT and navigate to that
:18}
GUS
AFEES
PO - and select any
particular DTstore
Dashboard page "Customer
If user give PO anydoes notpattern
invalid meet
AFEES
have 6 1. Enter
6. Launchany theinvalid
app . pattern pattern." error message.
Should
Customer 4.
2. Click
Loginon Create
with DN Credit under
DTnumber
Adminitrator/DT for AEFIS(Banner
digits(GU
Distributo
have 6- ofCustomer
My task PO
or TODOs section and and click (AEFIS - Starts withinCustomer
group) Customers 'VON' - 9
DUNS
S556678)
r - ARCbut with
on valid
validate data
and submit button digit}, Working asPass
digits
69556810 redirected
3. Click ontoany DNDT - CreditEntry
and navigate pageto PO field and try to submit the
(A3)
should select form
32216
Customer
5. Enter
that
Verify
any
particularDUNS
Rule No DT
number
1 - Dashboard
and
IfCustomerpage If userthen
try to user should
submit theget
form
not
DT -start
A3- any
4. store
Click on Create DN Credit under "Customer
without PO
giving does not
anyCustomer meet
DUNS
with groups
6. Enter
Verify Ifdont
valid
user have
try toprefix
pattern (pattern)
ofCustomer
submit the PO pattern." error message.
PO -
69556810 My
1. task
Launch orthe
TODOs
app .section and PO inCustomer PO field for
'GUS'(SW
Should number and
form with less
redirected click
to DT
DN on
than validate
- Credit and
6charCustomer
Entry (AEFIS
AEFIS(Banner with 'VON' - 9
- Starts
32216
Q987567) 2. Login
submit with Adminitrator/DT
button PO field for
PO inCustomer digit}, Working asPass
start
Deliverywith page
with valid data group) Customers then user
ForCusto
'VON' and GopuffCustomers.
5. Enter any DUNS number and should get an error message
Date
mer 3.
1. Click
Launch onthe
anyappDT and . navigate to "Customer PO does not meet
have
PO - -9 select
that any store
particular
Banner
char(VON 2.
6. Login
Click with
Ifon DTDTAdminitrator/DT
validate
Dashboard page
and submit
Should
Family
Verify
4. Click
with
user
on
valid
try
Create
data
toDN submit
Credit under pattern"
the
98887654
not start button
formtask
My withwithout
orless
TODOs giving
thansection and to (AEFIS - Starts with 'VON' - 9
6charCustomer
Dollar
3) 3. Click
anyCustomeron any DT
PO and
number. navigate
with PO inCustomer
redirected
that to DN
particular
PO Debitfield for
DT- Dashboard Entrypage page digit}
If user give length that is
Working asPass
Customer
'VON' GopuffCustomers.
DT - BKand
Banner
5.
4. Enter
Click any
on DUNSDN
Create number
Credit and
under If user try
Greater thanto submit the form
or Lessthan 9
have
Customer9 - 1.
My
Launch
select
taskanyor
the
storeapp .
TODOs section and with/withoutany
inCustomer PO data
text then
field andit
Go Puff
char(NER 2. Click
6. Loginon with DT Adminitrator/DT
validate and submit should not show any error
DUNS
Customer - redirected
with valid to DN - Credit Entry
data try to submit the form then
98543334
24472631 button
page with/without any data message
user should forgetCustomer
"CustomerPO PO
DUNS
5) - 3. Click
giving on any
anyCustomer DT and PO navigate
number. to field. Working asPass
12614
05749904 5. Enter
that any DUNS
particular number and
DT Dashboard page larger than maximum length"
PO
90102- With select
4. Click on Create DN Credit under error message.
any store
any
DT - value
BK 6.
MyEnter
task less than 6char
or TODOs section and andClick Length of PO should be
or
PO - on validate and submit
redirected to DN - Credit Entry button certain
If user try to submit the form
without
Should without
page giving anyCustomer PO ex.AEFIS
with giving - 9less
digit
than
value
start with number.
5. Enter any DUNS number and Go Puff - 6
6CharCustomer PODigits Working asPass
'GUS' but select any store inCustomer PO field for
have less 6. Enter less than 6char and Click GopuffCustomers then user
than 6 on validate and submit button should get an error message
digits(GU without giving anyCustomer PO "Customer PO does not meet
S99274) number. pattern" Working asPass
Customer
PO
Banner- - 4. Click on
Delivery Create
ticket no DN Credit under with giving greater than
missing
Should
AFEES My task or TODOs
1. Launch the app . section and 6CharCustomer PO
start
Customer with redirected
2. Loginbywith to DN - Credit
DT Adminitrator Entry valid inCustomer PO field for
Customer
GUS but Verify
page entering the GopuffCustomers then user
DUNS
Banner -- data
existingCustomer PO number of
have
69556810 5.
3. Enter
Click on any DT and navigate to should get an error message
any DUNS number and
AFEES
more sameCustomer
select any storeDT Dashboard page "Customer PO does not meet
63710
Customer that
1. particular
Launch the app .
than
DT 6
- A3 6.
4. Enter greater than
DN 6char
Creditand pattern"
DUNS
digits(GU - 2. Click
Login
Click on
on
withCreate
DT Adminitrator
validate and submit
under
valid (ex. starts with Gus and has 6
button
PO -
69556810 My
data task or TODOs section and
S9033456
Should without
Verify bygiving
redirected to DNanyCustomer
entering the
- and
Credit EntryPO char(GoPuff), PO start
63710
)start with 3. Click
number. on any DT
existingCustomer PO number of navigate to digits/letters, length.) Working asPass
DT - A3 page
that particular DT Dashboard page If user doesn't enter any
'VON' differentCustomer
PO - and 5.
4. Enter
Click any
on
1. Launch
DUNSDN
Create number and
the app Credit
. under delivery ticket number and try
have
Should less select
My any
task with store
or TODOs section andvalid to submit the form then user
than 9 2. Click
6. Login on DT Adminitrator
Validate and submit should get " delivery ticket
start with redirected
data to DN - Credit Entry
char(VON
'VON' and button
page without delivery ticket number is missing" error
345765) 3. Click on any DT and navigate to message.
number Working asPass
have
Customer 5. Enter
that any DUNS
DT Dashboard If user give any
more Duplicate
select any delivery
store ticket no page existingCustomer PO number
Banner
DUNS - 4.
1. Click
Launch ontheCreate
app DN. Credit under
than
Go Puff 9 6.
My Enter
task existingCustomer
or TODOs section PO
and for sameCustomer and try to
number
char(VON - 2. Login with
number DT Adminitrator
inCustomer PO text valid submit the form the user
box
Customer
14578892 redirected
data to DN - Credit Entry
44569345
DUNS - and clickRule
"Verify
page on Validate
No 9 - byand givingsubmit should get "Duplicate
If user give any PO
01478
67) 3. Click
button. on any DT and navigate to number " error message. Working asPass
05749904 Unique
5. Enter delivery
any DUNS ticket
numberno (DN and
DT - A8
Customer that particular
Credit) DT Dashboard page existingCustomer PO number
90069
Product
Banner - select
4. Click any
onthestore
Create under for differentCustomer and try
DT - BK 1.
6. Launch
Enter app DN. Credit
existingCustomer
code
AFEES - My task with
2. Login or TODOs section andvalid to submit the form then user
DT Adminitrator
PO
PO
1st -
line
Customer number
redirected inCustomer
to DN - CreditPO text box should not get any error
Entry
Should data
DUNS- - be
item and click on Validate
Duplicate Line Item
page
3. Click on any DT and
and submit
navigate to
message,
If user giveit any
should accept the
existing
empty
07756713
69556810 button.
1. Enter
5. Launchany theDUNS
app .number and form if no errors
delivery ticket numberare there.
in Working asPass
2819 that
2. particular
Login with DTDTAdminitrator
Dashboard page valid
63710 select
4. any store
Click on Create DN Credit under delivery ticket text field and
2nd
DT - line
A3 data
6. Enter existing delivery ticket try to submit the form the
Customer
item- also My taskon
3. Click or any
TODOs section
DT and and to
navigate
PO
Banner - number
redirected in delivery
to DN - ticket
Credit text box
Entry user should get "Duplicate
-should be that click
and particular
on DT Dashboard
Validate and submitpage delivery ticket number " error
Family
07756713 page
4. Click on Create DN Credit under "If user give any unique
empty
Dollar button.
5. Enter any DUNS number and message.
delivery ticket number in Working asPass
2819 My task or TODOs section and
Customer
In this select any store
redirected to DN - Credit Entry delivery ticket field and try to
DUNS
case it- 6. Enter
page any unique delivery ticket submit the form the user
24472631
should number
5. in delivery
Enter any DUNS number andticket text box shouldn't get error message
12614 InvalidCustomer
and click on Validate and submit and
not
DUNS select
1. Launchany thestore
app . If user give same be
from should submitted
product
DT - BK
accept button."
6. if no error are there. Working asPass
number - 2. Enter product
Login with code in product
DT Adminitrator valid code as 2nd line item in
the same
14578892 code
data field and select the product product code field and try to
product
00008 and
3. again
ClickRule give
on any same
DT -and product
navigate to submit the form the user
code
item to Verify
in 2nd line No 12
product by
codegiving
field page
and should get "Please remove
DT - A8 that particular DT Dashboard
validCustomer(DN Credit)
2nd line
It should and
4. click
Click on
onthe Validate
Create and submit duplicate product code or line
item 1. Launch
button. app DN. Credit under items " error message. Working asPass
not My task with
2. Login or TODOs section andvalid If user enter InvalidCustomer
DT Adminitrator
accept redirected
data to DN - Credit Entry DUNS number in DUNS
any Verify
page Rule No 14 - by selecting
DUNS 3. Click on
delivery dateany(DN and navigate to number fiels and try to submit
DT Credit)
invalid 5. enter
that InvalidCustomer
particular DT Dashboard DUNS page the form the user should get
number
DUNS - 1. Launch
number in the
DUNSapp .
number fiels and "InvalidCustomer " error
21339648 4.
2. Click
Login on
withCreate
DT andDN Credit under
Adminitrator valid message.
number. click
My on validate submit form. Working asPass
66600 datatask or TODOs section and If user enter validCustomer
DUNS
DT - A8 redirected
3. ClickRule to
on any DN - Credit
DT -and navigate to DUNS number in DUNS
Entry
number - Verify
page No 14 by selecting
Delivery
DUNS that particular
delivery date (DN Dashboard page number fiels and try to submit
DT Credit)
14578892
date - - 5.
4. enter validCustomer DUNSunder the form then the user should
number
01478 1. Click
Launch
number
onthe
in
Create
DUNS
DN
. Credit
appnumber
Empty
21339648 My
2. task with
Login or TODOs
DT and sectionfiels
Adminitrator
and get a auto pop of that
andvalid
DT
It - A8
should click on
redirected validate submit
to DN - Credit Entry form. particularCustomer
If user try to submit the form Working asPass
66600 data
not
DT - A8 page
3. Click on any DT and navigate to without selecting any delivery
accept
Deliveryif 5. Enter
that any DUNS
DT Dashboard page date in delivery date box then
delivery
date - select
4. Click on Create DN Credit under user should get "Delivery date
any store
date
(MM/DD/field 6.
MySelect
task or any delivery
TODOs date and
section click on is a mandatory
If user field."the
try to submit error
form
is empty.
YYYY) Validate and submit button.
redirected to DN - Credit Entry message
with selecting any delivery Working asPass
It should page date in delivery date box then
accept if 5. Enter any DUNS number and user shouldn't get any error
delivery select any store message and form should be
date is 6. Select any delivery date click on submitted if no errors are
selected Validate and submit button. there. Working asPass
21339648
give pop Verify Rule No 15 - by giving any
YYYY)
line item DT Dashboard page
(DN Credit)
up
Product 4. Click on Create DN
DT - A8
message 1. Launch
Total the app
quantity . Credit under
exceeds
code
Delivery- My
2. task
Login or TODOs section andvalid
with threshold
DT Adminitrator
as "The
Empty total eaches
redirected to DN - Credit- Requires
Entry
date
total data
verification
It should
(MM/DD/ page
3. Click onthe
anyapp
DT and navigate to If user is trying to submit the
quantity
not 1.
5. Launch
Enter any DUNS .number and
YYYY)
exceeds that
2. particular
Login with DTDTAdministrator
Dashboard page form without selecting any
accept
DUNS
Product if select
4. Click any
on Create DN Credit under product code, then user
store
the
product valid
6. data
Click on
number
code - -
allowable
Total
My
3. taskon
Click or validate
quantityTODOs
any DT
and submit
not exceeding
section
and and to should get “Product line item
navigate
field is
21339648
07756700 button
redirectedwithout
total eaches to threshold
DN Credit- Does
- Dashboard not is
Entrypage
quantity
empty
Selecting
require DT
products.
verification Missing” error message. Working asPass
1559
of 50 page
4. Click onthe
Create DN Credit under
DT
It
Save - A8
should
the 1.
5. Launch
Enter any app .
DUNS section
numberand and If user is trying to submit the
eaches.
Delivery My
2. task with
Login or TODOs
DT Administrator
accept
form
Unilever if
with select any
redirected store
to DN - Credit Entry form without selecting any
date
products
any error valid
6. data
Click on validate and submit product code, then user
is
(MM/DD/ page
3. Click with
on any DT and navigate to should get “Product line item
date
Ex:- is
required button
5. Enter any DUNS number and
YYYY)
selected
DUNS that
Verifyparticular
Selecting DTSave
products.
by clicking Dashboard
button page
after is Missing” error message. Working asPass
to
Product select
4. Click any
on store
Create DN Credit under
number
approve - clicking
6. Enter on validate
product and submit
code in product If user enter eaches more
code
21339648- My taskwith
button or TODOs
errors section and
for DN Debit
this credit
07756700 code field.
redirected to DN - Credit Entry than 50, then user should get
66600
ticket. Do form
7. Enter eaches more than 50. “Total quantity exceeds total
1559
DT - want
A8 page
1. Click
Launch the app . and submit
you
Eaches- 8.
5. Enter on validate
any DUNS number and eaches threshold - Requires
Delivery
to Save?" 2. Login with
button DT Administrator Verification” pop up message. Working asPass
49
date select any store
valid data
It should
(MM/DD/ 6.
3. Enter
Click onproduct
any DTcodeand in productto
navigate
accept
YYYY) code
that particular DT Dashboard page If user enter eaches less than
field.
based
Product on 7.
4. Enter
Click oneaches
Createlessthan
DN Debit 50.under 50, then user should not get
the
code - 8. Click on validate and
My task or TODOs section and submit any verification pop up
eaches.
07756700 button
redirected to DN - Debit Entry page message.
If any validation fails delivery Working asPass
1559 5. Enter any DUNS number and notes then that will be
Delivery select any store created with an error flag.
ticket 6. Click on validate and submit Such delivery notes should
number - button with errors and after click not be pushed to SAP. (Line
empty on save button level/ Header level errors) Working asPass
Executed
Executed Date By Remarks
Test Scenario Description Test cases Id
Applicatio Retailer
S.No n Project Story
130 Website CREME – US SMTM – 18 Verify Rule No 1 -Customer PO pattern (DN SMTM _18_01
debit) for EDI file from BOOMI interface data
GopuffCustomers- PO should starts with GUS and
have 6 char
131 Website CREME – US SMTM – 18 Verify Rule No 1 -Customer PO does not meet SMTM _18_02
pattern (DN debit) for EDI file from BOOMI
interface data
GopuffCustomers- if Customer PO does not starts
with GUS
pattern (DN debit ) for EDI file from BOOMI
interface data
AEFIS(Banner group)Customers - PO should starts
with VON and have 9 char
pattern (DN debit ) for EDI file from BOOMI
interface data
AEFIS(Banner group)Customers - PO should not
start with VON and have 9 char
pattern (DN Credit) for EDI file from BOOMI
interface data
Normal Customers - it should accept with/without
any data in Customer PO field
135 Website CREME – US SMTM – 18 Verify Rule No 2 -Customer PO length (DN debit) for SMTM _18_06
GopuffCustomers- If Customer PO has less than 6
char
136 Website CREME – US SMTM – 18 Verify Rule No 2 -Customer PO larger than SMTM _18_07
maximum length (DN debit) for EDI file from
GopuffCustomers- If Customer PO has more than 6
char
AEFIS(Banner group)Customers - if Customer PO
has less than 9 characters
has more than 9 characters
139 Website CREME – US SMTM – 18 Verify Rule No 3 -Customer PO mandatory for Go SMTM _18_10
Puff (DN debit) for EDI file from BOOMI interface
data
GopuffCustomers- if Customer PO field is empty
140 Website CREME – US SMTM – 18 Verify Rule No 3 -Customer PO mandatory for SMTM _18_11
AFEES (DN debit) for EDI file from BOOMI interface
data
field is empty
141 Website CREME – US SMTM – 18 Verify Rule No 3 -Customer PO not mandatory (DN SMTM _18_12
debit) for EDI file from BOOMI interface data
(Except Go puff/ AFEES/Doordash)
142 Website CREME – US SMTM – 18 Verify Rule No 4 - Date outside retailer's operation SMTM _18_13
date (DN Debit) for EDI file from BOOMI interface
data
Delivery date - if Delivery date is less than start date
from Customer hierarchy
data
Delivery date - if Delivery date is greater than end
date from Customer hierarchy
data
Delivery date - In between start and end date of
Customer Hierarchy.
145 Website CREME – US SMTM – 18 Verify Rule No 5 - Delivery date in the future (DN SMTM _18_16
Debit) for EDI file from BOOMI interface data
Delivery date - Future Delivery date (it should not
be greater/Future than system date.)
Debit) for EDI file from BOOMI interface data
Delivery date - it should accept less than or equal to
system date .
147 Website CREME – US SMTM – 18 Verify Rule No 6 - Delivery date less than allowable SMTM _18_18
days of current date (DN Debit) for EDI file from
Delivery date - if Delivery date is older than 90 days
from current date.
days of current date (DN Debit) for EDI file from
Delivery date - if Delivery date is in between 90
days from current date.
149 Website CREME – US SMTM – 18 Verify Rule No 7 - Delivery ticket no missing (DN SMTM _18_20
Delivery ticket number - if Delivery ticket number
field is empty
Delivery ticket number - if Debit DN has the
151 Website CREME – US SMTM – 18 Verify Rule No 8 - Duplicate Customer PO (DN SMTM _18_22
Debit) for same Customer from BOOMi for EDI
Customer PO - Existed Customer PO for same
Customer.
Customer PO - Existed Customer PO for different
Customer.
Customer PO - It should be Unique for same
Customer.
154 Website CREME – US SMTM – 18 Verify Rule No 9 - Duplicate delivery ticket no (DN SMTM _18_25
Delivery ticket number - Existed delivery ticket
number
155 Website CREME – US SMTM – 18 Verify Rule No 9 - by receiving Unique delivery SMTM _18_26
ticket no (DN Debit) from BOOMi for EDI
156 Website CREME – US SMTM – 18 Verify Rule No 10 - Duplicate Line Item(DN Debit) SMTM _18_27
from BOOMi for EDI
Product code - Same product as 2nd line item
from BOOMi for EDI
Product code - Should not be Same product
158 Website CREME – US SMTM – 18 Verify Rule No 11 -Eaches not in full boxes (DN SMTM _18_29
Eaches - Eaches other than multiples of "eaches per
box"
159 Website CREME – US SMTM – 18 Verify Rule No 11 - Eaches in full boxes (DN Debit) SMTM _18_30
from BOOMi for EDI
Eaches - Eaches should accept multiples of "eaches
per box"
160 Website CREME – US SMTM – 18 Verify Rule No 12 - Invalid Customer(DN Debit) SMTM _18_31
from BOOMi for EDI
DUNS number - Invalid Customer DUNS number
from BOOMi for EDI
DUNS number - DUNS number field is empty
from BOOMi for EDI
DUNS number - Valid Customer DUNS number
163 Website CREME – US SMTM – 18 Verify Rule No 13 - Invalid Product (DN Debit) from SMTM _18_34
BOOMi for EDI
BOOMi for EDI
Product code - Product code field is empty
165 Website CREME – US SMTM – 18 Verify Rule No 13 - by receiving valid Product (DN SMTM _18_36
166 Website CREME – US SMTM – 18 Verify Rule No 14 -No delivery date (DN Debit) from SMTM _18_37
BOOMi for EDI
Delivery date - if delivery date field is empty
167 Website CREME – US SMTM – 18 Verify Rule No 14 - Delivery date (DN Debit) from SMTM _18_38
BOOMi for EDI
Delivery date - if delivery date field is has valid
delivery date
168 Website CREME – US SMTM – 18 Verify Rule No 15 - No line item (DN Debit) from SMTM _18_39
BOOMi for EDI
Product Code - if product code field is empty
BOOMi for EDI
Product Code - if product code field is has any
products
170 Website CREME – US SMTM – 18 Verify Rule No 16 -Product not listed(DN Debit) SMTM _18_41
from BOOMi for EDI
Product code - if Product that is not mapped to the
Customer
from BOOMi for EDI
Product code - if Product are mapped to the
Customer
172 Website CREME – US SMTM – 18 Verify Rule No 17 -Quantity exceeds box Threshold SMTM _18_43
- requires verification (DN Debit) from BOOMi for
EDI
Gopuff Customers - eaches more than 5 box's
EDI
GopuffCustomers - It should be 5 boxes
EDI
Food Service migration - eaches more than 5 box's
EDI
Food Service migration - It should be 5 boxes
EDI
Normal Customers - it should accept any value
Credit) for EDI file from BOOMI interface data
have 6 char
interface data
with GUS
interface data
interface data
interface data
182 Website CREME – US SMTM – 18 Verify Rule No 2 -Customer PO length (DN SMTM _18_53
char
maximum length (DN Credit) for EDI file from
char
Puff (DN Credit)for EDI file from BOOMI interface
data
AFEES (DN Credit)for EDI file from BOOMI interface
data
field is empty
Credit)for EDI file from BOOMI interface data
system date .
days of current date (DN Credit)for EDI file from
from current date.
days of current date (DN Credit)for EDI file from
field is empty
Delivery ticket number - if Credit DN has the
Credit)for same Customer from BOOMi for EDI
Customer.
Customer.
Customer PO - It should be Unique Customer PO for
same Customer.
number
ticket no (DN Credit)from BOOMi for EDI
200 Website CREME – US SMTM – 18 Verify Rule No 10 - Duplicate Line Item(DN SMTM _18_71
202 Website CREME – US SMTM – 18 Verify Rule No 12 - Invalid Customer(DN SMTM _18_73
205 Website CREME – US SMTM – 18 Verify Rule No 14 -No delivery date (DN Credit)from SMTM _18_76
BOOMi for EDI
206 Website CREME – US SMTM – 18 Verify Rule No 14 - Delivery date (DN Credit)from SMTM _18_77
BOOMi for EDI
delivery date
207 Website CREME – US SMTM – 18 Verify Rule No 15 - No line item (DN Credit)from SMTM _18_78
BOOMi for EDI
BOOMi for EDI
products
209 Website CREME – US SMTM – 18 Verify Rule NO 19 - Total quantity exceeds total SMTM _18_80
eaches threshold - Requires
Verification (DN Credit) from BOOMi for EDI
Eaches - more than 50 eaches
Verification (DN Credit) from BOOMi for EDI
Eaches - Less than or equals to 50 eaches
debit) for Flat file from MuleSoft interface data
have 6 char
pattern (DN debit) for Flat file from MuleSoft
interface data
with GUS
pattern (DN debit ) for Flat file from MuleSoft
interface data
pattern (DN debit ) for Flat file from MuleSoft
interface data
pattern (DN Credit) for Flat file from MuleSoft
interface data
216 Website CREME – US SMTM – 18 Verify Rule No 2 -Customer PO length (DN debit) for SMTM _18_87
char
maximum length (DN debit) for Flat file from
char
Puff (DN debit) for Flat file from MuleSoft interface
data
AFEES (DN debit) for Flat file from MuleSoft
interface data
field is empty
debit) for Flat file from MuleSoft interface data
date (DN Debit) for Flat file from MuleSoft interface
data
Delivery date - if Delivery date is less than start date
from Customer hierarchy
data
Delivery date - if Delivery date is greater than end
date from Customer hierarchy
data
Delivery date - In between start and end date of
Customer Hierarchy.
Debit) for Flat file from MuleSoft interface data
Debit) for Flat file from MuleSoft interface data
system date .
days of current date (DN Debit) for Flat file from
from current date.
days of current date (DN Debit) for Flat file from
field is empty
Delivery ticket number - if Debit DN has the
Debit) for same Customer from MuleSoft for Flat
file
Customer.
file
Customer.
file
same Customer.
number
ticket no (DN Debit) from MuleSoft for Flat file
from MuleSoft for Flat file
Eaches - Eaches other than multiples of "eaches per
box"
per box"
Product code - Product code field is empty
246 Website CREME – US SMTM – 18 Verify Rule No 13 - by receiving valid Product (DN SMTM _18_117
247 Website CREME – US SMTM – 18 Verify Rule No 14 -No delivery date (DN Debit) from SMTM _18_118
248 Website CREME – US SMTM – 18 Verify Rule No 14 - Delivery date (DN Debit) from SMTM _18_119
delivery date
products
Product code - if Product that is not mapped to the
Customer
Product code - if Product are mapped to the
Customer
- requires verification (DN Debit) from MuleSoft for
Flat file
GopuffCustomers - eaches more than 5 box's
Flat file
GopuffCustomers - It should be 5 box's
Flat file
Flat file
Food Service migration - It should be 5 box's
Flat file
Credit) for Flat file from MuleSoft interface data
have 6 char
interface data
with GUS
interface data
interface data
interface data
263 Website CREME – US SMTM – 18 Verify Rule No 2 -Customer PO length (DN SMTM _18_134
char
maximum length (DN Credit) for Flat file from
char
Puff (DN Credit)for Flat file from MuleSoft interface
data
AFEES (DN Credit)for Flat file from MuleSoft
interface data
field is empty
Credit)for Flat file from MuleSoft interface data
Credit)for Flat file from MuleSoft interface data
system date .
days of current date (DN Credit)for Flat file from
from current date.
days of current date (DN Credit)for Flat file from
field is empty
Delivery ticket number - if Credit DN has the
Credit)for same Customer from MuleSoft for Flat
file
Customer.
file
Customer.
file
same Customer.
number
ticket no (DN Credit)from MuleSoft for Flat file
286 Website CREME – US SMTM – 18 Verify Rule No 14 -No delivery date (DN Credit)from SMTM _18_157
287 Website CREME – US SMTM – 18 Verify Rule No 14 - Delivery date (DN Credit)from SMTM _18_158
delivery date
products
Verification (DN Credit) from MuleSoft for Flat file
Verification (DN Credit) from MuleSoft for Flat file
292 Website CREME – US SMTM – 18 Verify user is able to launch DT site. SMTM _18_163
293 Website CREME – US SMTM – 18 Verify DT user is able to directly login to DT SMTM _18_164
dashboard
294 Website CREME – US SMTM – 18 Verify DT administrative is able to login to the site SMTM _18_165
295 Website CREME – US SMTM – 18 Verify by clicking on any DT on account to proceed SMTM _18_166
page
296 Website CREME – US SMTM – 18 Verify by clicking on Create DN Debit under My SMTM _18_167
tasks or TODOs section
pattern (DN Debit) - If Customer groups have prefix
(pattern)
(pattern) with Invalid pattern for GopuffCustomers.
(pattern) with valid pattern for GopuffCustomers.
(pattern) - Without data for GopuffCustomers.
(pattern) with Invalid pattern for AEFIS(Banner
group)(Banner group)Customers.
(pattern) with valid pattern for AEFIS(Banner group)
Customers.
(pattern) - Without data for AEFIS(Banner group)
Customers.
304 Website CREME – US SMTM – 18 Verify Rule No 1 - If Customer groups don't have SMTM _18_175
prefix (pattern)
maximum length (DN Debit)(The Customer PO filed
should follow certain Length as below)
Length of PO should be certain
ex.AEFIS - 9 digit
Go Puff - 6 Digits
maximum length(DN Debit) - If Customer groups
have prefix (pattern) - By giving less than 6 char in
Customer PO filed for GopuffCustomers.
maximum length (DN Debit) - If Customer groups
have prefix (pattern) - By giving greater than 6 char
in Customer PO filed for GopuffCustomers.
maximum length(DN Debit) - If Customer groups
Customer PO filed for AEFIS(Banner group)
Customers.
maximum length (DN Debit) - If Customer groups
in Customer PO filed for AEFIS(Banner group)
Customers.
310 Website CREME – US SMTM – 18 Verify Rule No 2 - If Customer PO doesn't have any SMTM _18_181
specific length
date (DN Debit)
date (DN Debit) - Select any less than start of
Customer Hierarchy
date (DN Debit) - Select any greater than end date
of Customer Hierarchy
date (DN Debit) - Verify by selecting any in between
start or end date
Debit)
days of current date (DN Debit)
Debit)
Debit) for same Customer
Debit) for different Customer
320 Website CREME – US SMTM – 18 Verify Rule No 9 -Duplicate delivery ticket no (DN SMTM _18_191
Debit)
321 Website CREME – US SMTM – 18 Verify Rule No 9 - by giving Unique delivery ticket SMTM _18_192
no (DN Debit)
322 Website CREME – US SMTM – 18 Verify Rule No 10 -Duplicate Line Item(DN Debit) SMTM _18_193
Debit)
324 Website CREME – US SMTM – 18 Verify Rule No 11 -by giving Eaches in full boxes (DN SMTM _18_195
Debit)
per box"
326 Website CREME – US SMTM – 18 Verify Rule No 12 -InvalidCustomer(DN Debit) SMTM _18_196
328 Website CREME – US SMTM – 18 Verify Rule No 12 - by giving valid Customer(DN SMTM _18_197
Debit)
329 Website CREME – US SMTM – 18 Verify Rule No 13 -Invalid Product (DN Debit) SMTM _18_198
330 Website CREME – US SMTM – 18 Verify Rule No 13 - by giving valid Product (DN SMTM _18_199
Debit)
331 Website CREME – US SMTM – 18 Verify Rule No 14 -No delivery date (DN Debit) SMTM _18_200
332 Website CREME – US SMTM – 18 Verify Rule No 14 - by selecting delivery date (DN SMTM _18_201
Debit)
333 Website CREME – US SMTM – 18 Verify Rule No 15 - No line item (DN Debit) SMTM _18_202
334 Website CREME – US SMTM – 18 Verify Rule No 15 - by giving any line item (DN SMTM _18_203
Debit)
- requires verification (DN Debit)
GopuffCustomers - eaches more than 5 box's
GopuffCustomers - It should be 5 boxes
Food Service migration - It should be 5 boxes
341 Website CREME – US SMTM – 18 Verify Rule No 18 - Sub - Distributor Missing SMTM _18_206
(DN Debit)
342 Website CREME – US SMTM – 18 Verify Rule No 18 - if Sub - Distributor is mapped SMTM _18_207
(DN Debit)
pattern (DN Credit) - If Customer groups have prefix
(pattern) with Invalid pattern for AEFIS(Banner
group)(Banner group)Customers.
(pattern) with valid pattern for AEFIS(Banner
group) Customers.
(pattern) - Without data for AEFIS(Banner
group) Customers.
346 Website CREME – US SMTM – 18 Verify Rule No 1 - If Customer groups don't have SMTM _18_211
prefix (pattern)
maximum length (DN Credit)(The Customer PO filed
should follow certain Length as below)
ex.AEFIS - 9 digit
Go Puff - 6 Digits
maximum length(DN Credit) - If Customer groups
Customer PO filed for GopuffCustomers.
maximum length (DN Credit) - If Customer groups
in Customer PO filed for GopuffCustomers.
Credit)
Debit) for same Customer
Debit) for different Customer
353 Website CREME – US SMTM – 18 Verify Rule No 9 -Duplicate delivery ticket no (DN SMTM _18_218
Credit)
354 Website CREME – US SMTM – 18 Verify Rule No 9 - by giving Unique delivery ticket SMTM _18_219
no (DN Credit)
355 Website CREME – US SMTM – 18 Verify Rule No 10 -Duplicate Line Item(DN Credit ) SMTM _18_220
356 Website CREME – US SMTM – 18 Verify Rule No 12 -Invalid Customer(DN Credit) SMTM _18_221
357 Website CREME – US SMTM – 18 Verify Rule No 12 - by giving valid Customer(DN SMTM _18_222
Credit)
358 Website CREME – US SMTM – 18 Verify Rule No 14 -No delivery date (DN Credit) SMTM _18_223
359 Website CREME – US SMTM – 18 Verify Rule No 14 - by selecting delivery date (DN SMTM _18_224
Credit)
360 Website CREME – US SMTM – 18 Verify Rule No 15 - No line item (DN Credit) SMTM _18_225
361 Website CREME – US SMTM – 18 Verify Rule No 15 - by giving any line item (DN SMTM _18_226
Credit)
362 Website CREME – US SMTM – 18 Verify Rule NO 19- Total quantity exceeds SMTM _18_227
total eaches threshold - Requires
Verification (DN Credit)
363 Website CREME – US SMTM – 18 Verify Rule NO 19- Total quantity not exceeding SMTM _18_228
total eaches threshold - Does not require
verification (DN Credit)
364 Website CREME – US SMTM – 18 Verify by clicking Save button after clicking on SMTM _18_229
validate and submit button with errors for DN Debit
form
Test Data Test case description
Customer Banner - Go Puff Verify Rule No 1 -Customer PO does not meet pattern (DN
Customer DUNS - 0574990490069 Debit) for EDI file from BOOMI.
DT - BK GopuffCustomers- PO should starts with GUS
PO - Should start with GUS and have 6 1. Magento will receive EDI 810 file from BOOMI for Go
digits(GUS334567) puff Customers having Customer PO starting with GUS and
6 char
2. Launch DT site and Login with valid data
3. Navigate to that particular DT dashboard page
4. Click on DN Debit (Open) link under My dashboard
5. Search for that Customer PO number using delivery
ticket number /DUNS Number
Customer DUNS - 0574990490102 Debit) for EDI file from BOOMI interface data
DT - BK GopuffCustomers- if Customer PO does not starts with GUS
PO - Should have 6 digits but should not 1. Magento will receive EDI 810 file from BOOMI for Go
start with 'GUS'(QWE789654) puff Customers having Customer PO not starting with GUS
and 6 char
4. Click on DN Debit(Open) link under My dashboard
Customer Banner - AAFES Verify Rule No 1 -Customer PO does not meet pattern (DN )
Customer DUNS - 6955681032216 for EDI file from BOOMI interface data
DT - A3 AEFIS(Banner group)Customers - PO should starts with
PO - Should start with 'VON' and have 9 VON
char(VON098765432) 1. Magento will receive EDI 810 file from BOOMI for
AEFIS(Banner group)Customers having Customer PO
starting with VON and 9 char
4. Click on DN (Open) link under My dashboard
6. Click on that DN and observe
For Customer Banner - AAFES Verify Rule No 1 -Customer PO does not meet pattern (DN )
for EDI file from BOOMI interface data
Distributor -A3 AEFIS(Banner group)Customers - PO should starts with
Customer DUNS - 6955681032216 VON
Delivery Date - MM-DD-YYYY 1. Magento will receive EDI 810 file from BOOMI for
PO - Should not start with 'VON' and have AEFIS(Banner group)Customers having Customer PO
9 char(HJK098765675) starting with VON and 9 char
For Customer Banner - Family Dollar Verify Rule No 1 - For Customer groups that don't have any
DT - BK PO pattern for EDI file from BOOMI interface data
Customer DUNS - 2447263112614 Normal Customers - it should accept with/without any data
PO - With any value or without value in Customer PO field
1. Magento will receive EDI 810 file from BOOMI
4. Click on DN debit (Open) link under My dashboard
Customer Banner - Go Puff Verify Rule No 2 -Customer PO larger than maximum

Customer DUNS - 0574990490102 length for EDI file from BOOMI interface data
DT - BK GopuffCustomers- If Customer PO has less than 6 char
PO - Should start with 'GUS' but have less 1. Magento will receive EDI 810 file from BOOMI for Go
than 6 digits(GUS7654) puff Customers having Customer PO less than 6 char

DT - BK GopuffCustomers- If Customer PO has more than 6 char
PO - Should start with GUS but have more 1. Magento will receive EDI 810 file from BOOMI for Go
than 6 digits(GUS7865432) puff Customers having Customer PO more than 6 char
Customer Banner - AAFES Verify Rule No 1 -Customer PO does not meet pattern (DN)
Customer DUNS - 6955681063710 for EDI file from BOOMI interface data
DT - ARC AEFIS(Banner group)Customers - if Customer PO has less
PO - Should start with 'VON' and have less than 9 char.
than 9 char 1. Magento will receive EDI 810 file from BOOMI for
(VON9876544) AEFIS(Banner group)Customers having Customer PO with
less than 9 char..
2. Launch DT site and Login with valid data.
Customer Banner - AAFES Verify Rule No 2 -Customer PO larger than maximum
DT - A3 AEFIS(Banner group)Customers - if Customer PO length is
PO - Should start with 'VON' and have more than 9 char
more than 9 char 1. Magento will receive EDI 810 file from BOOMI for
(VON9876544569) AEFIS(Banner group)Customers having Customer PO with
less than 9 char..
Verify Rule No 1 -Customer PO does not meet pattern (DN

Customer DUNS - 0574990490069(Go Debit) for EDI file from BOOMI interface data
Puff) GopuffCustomers- if Customer PO is empty
DT - BK 1. Magento will receive EDI 810 file from BOOMI for Go
Customer PO - empty(It should not accept puff Customers having Customer PO empty
if Customer PO field is empty) 2. Launch DT site and Login with valid data
Verify Rule No 1 -Customer PO does not meet pattern (DN )

Customer DUNS - 6955681063710(AFEES ) for EDI file from BOOMI interface data
DT - BK AEFIS(Banner group)Customers - if Customer PO field is
Customer PO - empty(It should not accept empty
if Customer PO field is empty) 1. Magento will receive EDI 810 file from BOOMI for
AEFIS(Banner group)Customers having Customer PO field
as empty.
Verify Rule No 1 - For Customer groups that don't have any

Customer DUNS - 2447263112614 PO pattern for EDI file from BOOMI interface data
DT - BK Normal Customers - it should accept with/without any data
Customer PO - any data in Customer PO field
Verify Rule No 4 - Date outside retailer's operation date
Customer DUNS - 2447263105608 (DN Debit) for EDI file from BOOMI interface data
DT - A3 Delivery date - if Delivery date is less than start date from
Delivery date - 12-08-2013(MM-DD-YYYY ) Customer hierarchy
(Start date 12-07-2013 it Should not 1. Magento will receive EDI 810 file from BOOMI
accept less than start date from Customer 2. Launch DT site and Login with valid data
hierarchy) 3. Navigate to that particular DT dashboard page
5. Search for that Delivery date which we receive less than
start date from Customer Hierarchy using delivery ticket
number /DUNS Number
6. Click on that filtered DN Debit and observe

(DN Debit) for EDI file from BOOMI interface data
Customer DUNS - 2447263105608 Delivery date - if Delivery date is greater than end date
DT - A3 from Customer hierarchy
Delivery date - 12-31-9999 (MM-DD-YYYY) 1. Magento will receive EDI 810 file from BOOMI
(End date 12-31-9999 it Should not accept 2. Launch DT site and Login with valid data
greater than date from Customer 3. Navigate to that particular DT dashboard page
hierarchy) 4. Click on DN debit (Open) link under My dashboard
5. Search for that Delivery date which we receive greater
than end using delivery ticket number /DUNS Number
Customer DUNS - 2447263105608 Verify Rule No 4 - Date outside retailer's operation date
DT - A3 (DN Debit) for EDI file from BOOMI interface data
Delivery date - 2013-12-08 and 9999-12- Delivery date - In between start and end date of Customer
31 it should accept In between start and Hierarchy.
end date of Customer Hierarchy. 1. Magento will receive EDI 810 file from BOOMI
5. Search for that Delivery date which we receive in
between start and end date of that Customer Hierarchy
using delivery ticket number /DUNS Number
Customer DUNS - 2447263105608 Verify Rule No 5 - Delivery date in the future (DN Debit) for
DT - A3 EDI file from BOOMI interface data
Delivery date (MM-DD-YYYY) it Should not Delivery date - Future Delivery date
accept future delivery dates. 1. Magento will receive EDI 810 file from BOOMI for
delivery date
5. Search for that delivery date using delivery ticket
number /DUNS Number
6. Click on that DebitDN and observe
DT - A3 EDI file from BOOMI interface data
Delivery date (MM-DD-YYYY) it should Delivery date - it should accept less than or equal to system
accept less than or equal to system date date .
1. Magento will receive EDI 810 file from BOOMI for
delivery date
number /DUNS Number
Customer DUNS - 2447263105608 Verify Rule No 6 - Delivery date less than allowable days of
DT - A3 current date (DN Debit) for EDI file from BOOMI interface
Delivery date (MM-DD-YYYY) if Delivery data
date is older than 90 days from current Delivery date - if Delivery date is older than 90 days from
date. current date.
1. Magento will receive EDI 810 file from BOOMI for older
than 90 days as delivery date
number /DUNS Number
DT - A3 current date (DN Debit) for EDI file from BOOMI interface
Delivery date (MM-DD-YYYY) if Delivery data
date is older than 90 days from current Delivery date - if Delivery date is in between 90 days from
date. current date.
between 90 days from current date.
number /DUNS Number
Verify Rule No 7 - Delivery ticket no missing (DN Debit)

Customer DUNS - 8473400010001 from BOOMi for EDI
DT - BK Delivery ticket number - if Delivery ticket number field is
Delivery ticket number - without delivery empty
ticket number(it should not accept if 1. Magento will receive EDI 810 file from BOOMI for empty
delivery ticket number field is empty) delivery date
5. Search for that empty delivery ticket using DUNS
Number
6. Click on that filtered Debit DN and observe
Customer DUNS - 8473400010001 from BOOMi for EDI
DT - BK Delivery ticket number - if Debit DN has the Delivery ticket
Delivery ticket number - 1232123 number
(With delivery ticket number) 1. Magento will receive EDI 810 file from BOOMI
5. Search for that delivery ticket using DUNS Number
Verify Rule No 8 - by receiving Duplicate Customer PO (DN

Customer DUNS - 8473400010001 Debit) for same Customer from BOOMi for EDI
DT - BK 1. Magento will receive EDI 810 file from BOOMI for
Customer PO - GUS987332 Duplicate Customer PO
(It should not accept in case of same 2. Launch DT site and Login with valid data
Customer PO for same Customer) 3. Navigate to that particular DT dashboard page
5. Search for that Duplicate Customer PO using delivery

Customer DUNS - 8473400010001 Debit) for different Customer from BOOMi for EDI
(It should accept in case of same 2. Launch DT site and Login with valid data
Customer PO for diffCustomer) 3. Navigate to that particular DT dashboard page
Verify Rule No 8 - Duplicate Customer PO (DN Debit) for

Customer DUNS - 8473400010001 same Customer from BOOMi for EDI
DT - BK Customer PO - It should be Unique Customer PO for same
Customer PO - GUS009 Customer.
(It should accept in case of unique 1. Magento will receive EDI 810 file from BOOMI for
Customer PO) Duplicate Customer PO
Customer DUNS - 2447263112614 Verify Rule No 9 -by receiving Duplicate delivery ticket no
DT - BK (DN Debit) from BOOMi for EDI
Delivery ticket number- 8062223503 (It Delivery ticket number - Existed delivery ticket number
should not accept in case of same existing 1. Magento will receive EDI 810 file from BOOMI for
delivery ticket number) existed delivery ticket number
5. Search for that delivery ticket number using delivery
Customer DUNS - 2447263112614 Verify Rule No 9 - by receiving Unique delivery ticket no
DT - BK (DN Debit) from BOOMi for EDI
Delivery ticket number- 8062223111 1. Magento will receive EDI 810 file from BOOMI for
(It should accept in case of unique delivery delivery ticket number
ticket number in delivery ticket number 2. Launch DT site and Login with valid data
field) 3. Navigate to that particular DT dashboard page
5. Search for that delivery ticket no using delivery ticket
number /DUNS Number
Customer DUNS - 2447263112614 Verify Rule No 10 -by receiving Duplicate Line Item(DN
DT - BK Debit) from BOOMi for EDI
product code- 075856031140 Product code - Same product as 2nd line item
Again same product code in 2nd line item 1. Magento will receive EDI 810 file from BOOMI for
- 075856031140 Duplicate Line Item
(It should not accept in case of if we 2. Launch DT site and Login with valid data
receive same product code as second line 3. Navigate to that particular DT dashboard page
item) 4. Click on DN Debit(Open) link under My dashboard
5. Search for that Duplicate Line Item using delivery ticket
number /DUNS Number
Customer DUNS - 2447263112614 Verify Rule No 10 - Duplicate Line Item(DN Debit) from
DT - BK BOOMi for EDI
product code 1- 076840100125 Product code - Should not be Same product as 2nd line
product code 2- 076840485116 item
(It should accept in case of diff line level 1. Magento will receive EDI 810 file from BOOMI
items) 2. Launch DT site and Login with valid data
5. Search for that Duplicate Line Item(Should not be Same
product as 2nd line item) using delivery ticket number
/DUNS Number
Customer DUNS - 2447263105644 Verify Rule No 11 -Eaches not in full boxes (DN Debit) from
DT - A3 BOOMi for EDI
Product code - 077567002204 (Eaches Per Eaches - Eaches other than multiples of "eaches per box"
Box is 24) 1. Magento will receive EDI 810 file from BOOMI for Eaches
Eaches - 50 not in full boxes
(It should not accept in case of eaches 2. Launch DT site and Login with valid data
other than multiples of "eaches per box") 3. Navigate to that particular DT dashboard page
5. Search for that Eaches not in full boxes using delivery
6. Click on that filtered DebitDN and observe
Customer DUNS - 2447263105644 Verify Rule No 11 -Eaches in full boxes (DN Debit) from
Product code - 077567002204 (Eaches Per Eaches - Eaches should be multiples of "eaches per box"
Box is 24) 1. Magento will receive EDI 810 file from BOOMI for Eaches
Eaches - 48 in full boxes
(It should accept in case of multiples of 2. Launch DT site and Login with valid data
"eaches per box") 3. Navigate to that particular DT dashboard page
5. Search for that Eaches in full boxes using delivery ticket
number /DUNS Number
Customer DUNS - 2447263101788 Verify Rule No 12 - Invalid Customer(DN Debit) from
DUNS number - 2447263101788 DUNS number - Invalid Customer DUNS number
(It should not accept in case of invalid 1. Magento will receive EDI 810 file from BOOMI for Invalid
Duns number in DUNS number filed) Customer DUNS number
5. Search for that Invalid Customer using delivery ticket
number

DUNS number - Empty DUNS number - DUNS number field is empty
(It should not accept in case of empty 1. Magento will receive EDI 810 file from BOOMI
Duns number in DUNS number filed) 2. Launch DT site and Login with valid data
5. Search for that empty DUNs number Customer using

DUNS number - 6955681032216 DUNS number - Valid Customer DUNS number
(It should accept in case of valid Duns 1. Magento will receive EDI 810 file from BOOMI for valid
number in DUNS number filed) Customer
5. Search for that valid Customer using delivery ticket
number /DUNS Number
Customer DUNS - 2447263101707 Verify Rule No 13 - Invalid Product (DN Debit) from BOOMi
DT - A6 for EDI
Product code - 077567283030 DUNS number - Invalid Product code
(It should not accept in case of invalid 1. Magento will receive EDI 810 file from BOOMI for Invalid
Product code in product code field) Product
5. Search for that Invalid Product using delivery ticket
number /DUNS Number
Customer DUNS - 2447263101707 Verify Rule No 12 - Invalid Product (DN Debit) from BOOMi
DT - A6 for EDI
Product code - Empty DUNS number - Product code field is empty
(It should not accept in case of empty 1. Magento will receive EDI 810 file from BOOMI
Product code in product code field) 2. Launch DT site and Login with valid data
5. Search for that empty Product code using delivery ticket
number /DUNS Number
Customer DUNS - 2447263105644 Verify Rule No 13 - by receiving Invalid Product (DN Debit)
DT - A3 from BOOMi for EDI
Product code - 077567002204 1. Magento will receive EDI 810 file from BOOMI for valid
Valid Product code Product
(It should accept in case of valid Product 2. Launch DT site and Login with valid data
code in product code field) 3. Navigate to that particular DT dashboard page
5. Search for that valid Product using delivery ticket
number /DUNS Number
Customer DUNS - 2447263102456 Verify Rule No 14 -No delivery date (DN Debit) from
Delivery date field - Empty Delivery date - if delivery date field is empty
(It should not accept if delivery date field 1. Magento will receive EDI 810 file from BOOMI for no
is empty) delivery date
5. Search for that no delivery date using delivery ticket
number /DUNS Number
Customer DUNS - 2447263102456 Verify Rule No 14 - Delivery date (DN Debit) from BOOMi
DT - A3 for EDI
Delivery date field - (MM/DD/YYYY) 1. Magento will receive EDI 810 file from BOOMI for
(It should accept if delivery date field is delivery date
has valid delivery date) 2. Launch DT site and Login with valid data
number /DUNS Number
Customer DUNS - Verify Rule No 15 - No line item (DN Debit) from BOOMi for
2447263105608_x0001_ EDI
DT - A3 Product Code - if product code field is empty
Product Code - Empty 1. Magento will receive EDI 810 file from BOOMI for No
(It should not accept if product code field line item
is empty ) 2. Launch DT site and Login with valid data
5. Search for that No line item using delivery ticket number
/DUNS Number
Customer DUNS - Verify Rule No 15 - No line item (DN Debit) from BOOMi for
2447263105608_x0001_ EDI
DT - A3 Product Code - if product code field is has any products
Delivery date - 08/30/2022 1. Magento will receive EDI 810 file from BOOMI for line
(MM/DD/YYYY) items
Product Code - 077567002228 2. Launch DT site and Login with valid data
(It should accept if product code field is 3. Navigate to that particular DT dashboard page
has any products) 4. Click on DN Debit(Open) link under My dashboard
5. Search for that line items using delivery ticket
number /DUNS Number
Customer DUNS - 2447263101707 DT - A6 Verify Rule No 16 -Product not listed(DN Debit) from
Product code -077567002887 BOOMi for EDI
(It should not accept in case of product Product code - if Product is not mapped to that Customer
code is not exist in system/Not mapped to 1. Magento will receive EDI 810 file from BOOMI for
that Customer) Product not listed
5. Search for that Product not listed using delivery ticket
number /DUNS Number
Customer DUNS - 6955681040307 Verify Rule No 16 -Product not listed(DN Debit) from
Delivery date - (MM/DD/YYYY) Product code - if Product are mapped to the Customer
Product code -075856001600 1. Magento will receive EDI 810 file from BOOMI
(It should accept in case of product code is 2. Launch DT site and Login with valid data
exist in system/mapped to that Customer) 3. Navigate to that particular DT dashboard page
5. Search for that Product is listed using delivery ticket
number /DUNS Number
Customer DUNS - 8473400010001 Verify Rule No 17 -Quantity exceeds box Threshold -

DT - A8 requires verification (DN Debit) from BOOMi for EDI
Delivery date - (MM/DD/YYYY) Gopuff Customers - eaches more than 5 boxes
Product code - 077567001238 (Eaches per 1. Magento will receive EDI 810 file from BOOMI for
Box -6) Quantity exceeds box Threshold
Eaches - 36 2. Launch DT site and Login with valid data
(GopuffCustomers - It should not accept in 3. Navigate to that particular DT dashboard page
case of eaches more than 5 box's) 4. Click on DN Debit(Open) link under My dashboard
5. Search for that Quantity exceeds box using delivery

Delivery date - (MM/DD/YYYY) GopuffCustomers - It should be 5 boxes
(GopuffCustomers - It should accept in 3. Navigate to that particular DT dashboard page
case of eaches are 5 box's or less than 5 4. Click on DN Debit(Open) link under My dashboard
boxes) 5. Search for that Quantity exceeds box using delivery

Delivery date - (MM/DD/YYYY) Food Service migration - It should be 5 box's
(It should not accept in case of Food 3. Navigate to that particular DT dashboard page
Service migration - eaches more than 5 4. Click on DN Debit(Open) link under My dashboard
box's) 5. Search for that Quantity exceeds box using delivery
(It should accept in case of Food Service 3. Navigate to that particular DT dashboard page
migration - eaches is 5 box's) 4. Click on DN Debit(Open) link under My dashboard

Delivery date - (MM/DD/YYYY) Normal Customers - it should accept any value
Product code - 076840100040(Eaches per 1. Magento will receive EDI 810 file from BOOMI
Box -6) 2. Launch DT site and Login with valid data
Eaches - 120 3. Navigate to that particular DT dashboard page
Normal Customers - it should accept any 4. Click on DN Debit(Open) link under My dashboard
value 5. Search using delivery ticket number /DUNS Number
Customer DUNS - 0574990490069 Credit)for EDI file from BOOMI.
PO - Should start with GUS and have 6 1. Magento will receive EDI 810 file from BOOMI for Go
digits(GUS897654) puff Customers having Customer PO starting with GUS and
6 char
4. Click on DN Credit (Open) link under My dashboard
Customer DUNS - 0574990490102 Credit)for EDI file from BOOMI interface data
PO - Should have 6 digits but should not 1. Magento will receive EDI 810 file from BOOMI for Go
start with 'GUS'(SUG987654) puff Customers having Customer PO not starting with GUS
and 6 char
4. Click on DN Credit(Open) link under My dashboard
Customer Banner - AFEES Verify Rule No 1 -Customer PO does not meet pattern (DN
char(VON876543234) 1. Magento will receive EDI 810 file from BOOMI for
For Customer Banner - AFEES Verify Rule No 1 -Customer PO does not meet pattern (DN
Distributor - A3 AEFIS(Banner group)Customers - PO should starts with
Delivery Date - 08-10-2022 1. Magento will receive EDI 810 file from BOOMI for
9 char(NOV765456754) starting with VON and 9 char
PO pattern for EDI file from BOOMI interface data
Customer DUNS - 2447263112614 in Customer PO field
PO - With any value or without value 1. Magento will receive EDI 810 file from BOOMI

PO - Should start with 'GUS' but have less 1. Magento will receive EDI 810 file from BOOMI for Go
than 6 digits(GUS7654) puff Customers having Customer PO less than 6 char

PO - Should start with GUS but have more 1. Magento will receive EDI 810 file from BOOMI for Go
than 6 digits(GUS98754324) puff Customers having Customer PO more than 6 char
Customer DUNS - 6955681063710 Credit) for EDI file from BOOMI interface data
DT - A3 AEFIS(Banner group)Customers - if Customer PO has less
than 9 char(VON9876545) 1. Magento will receive EDI 810 file from BOOMI for
AEFIS(Banner group)Customers having Customer PO with
less than 9 char..
Customer Banner - AFEES Verify Rule No 2 -Customer PO larger than maximum

more than 9 char(VON674346789) 1. Magento will receive EDI 810 file from BOOMI for
less than 9 char..
DT - BK GopuffCustomers- if Customer PO is empty
PO - Should be empty 1. Magento will receive EDI 810 file from BOOMI for Go
puff Customers having Customer PO empty
DT - A3 AEFIS(Banner group)Customers - if Customer PO field is
PO - should be empty empty
as empty.
Customer Banner - Family Dollar Verify Rule No 1 - For Customer groups that don't have any
Customer DUNS - 2447263112614 PO pattern for EDI file from BOOMI interface data
DT - BK PO- any data/ without data Normal Customers - it should accept with/without any data
in Customer PO field
Delivery date (MM-DD-YYYY) Verify Rule No 5 - Delivery date in the future (DN Credit)for
Customer DUNS - 8473400010001 EDI file from BOOMI interface data
DT - A8 Delivery date - Future Delivery date
Delivery date - it Should not accept future 1. Magento will receive EDI 810 file from BOOMI for
delivery dates. delivery date
number /DUNS Number
6. Click on that filtered Credit DN and observe
Delivery date - MM-DD-YYYY Verify Rule No 5 - Delivery date in the future (DN Credit)for
Customer DUNS - 8473400010001 EDI file from BOOMI interface data
DT - A8 Delivery date - it should accept less than or equal to system
Delivery date - it Should accept old 90 date .
days from current date. 1. Magento will receive EDI 810 file from BOOMI for
delivery date
number /DUNS Number
Delivery date - MM-DD-YYYY(System Verify Rule No 6 - Delivery date less than allowable days of
should not accept the older than 90 days current date (DN Credit)for EDI file from BOOMI interface
from current date) data
Customer DUNS - 8473400010001 Delivery date - if Delivery date is older than 90 days from
DT - A8 current date.
Delivery date - it Should not accept less 1. Magento will receive EDI 810 file from BOOMI for older
than start date than 90 days as delivery date
number /DUNS Number
Delivery date - MM-DD-YYYY Verify Rule No 6 - Delivery date less than allowable days of
Customer DUNS - 8473400010001 current date (DN Credit)for EDI file from BOOMI interface
DT - A8 data
Delivery date - it Should accept old 90 Delivery date - if Delivery date is in between 90 days from
days from current date. current date.
between 90 days from current date.
number /DUNS Number
Customer DUNS - 8473400010001 Verify Rule No 7 - Delivery ticket no missing (DN

DT - BK Credit)from BOOMi for EDI
Delivery ticket number - Should be empty Delivery ticket number - if Delivery ticket number field is
empty
1. Magento will receive EDI 810 file from BOOMI for empty
delivery date
Number
Customer DUNS - 8473400010001 Verify Rule No 7 - Delivery ticket no missing (DN

DT - BK Credit)from BOOMi for EDI
Delivery ticket number - Should have Delivery ticket number - if Credit DN has the Delivery ticket
delivery ticket number number

Customer DUNS - 8473400010001 Credit)for same Customer from BOOMi for EDI
Customer DUNS - 8473400010001 Verify Rule No 8 - by receiving Duplicate Customer PO (DN

DT - BK Credit)for different Customer from BOOMi for EDI
Customer PO - GUS705332 1. Magento will receive EDI 810 file from BOOMI for
Duplicate Customer PO
Customer DUNS - 8473400010001 Verify Rule No 8 - Duplicate Customer PO (DN Credit)for
DT - BK same Customer from BOOMi for EDI
Customer PO - GUS705 Customer PO - It should be Unique Customer PO for same
Customer.
DT - A6 Delivery ticket number- same (DN Credit)from BOOMi for EDI
existing delivery ticket number Delivery ticket number - Existed delivery ticket number
existed delivery ticket number

DT - A6 Delivery ticket number- unique (DN Credit)from BOOMi for EDI
delivery ticket number 1. Magento will receive EDI 810 file from BOOMI for
number /DUNS Number
DT - A6 product code- 075856001600 Credit)from BOOMi for EDI
again same product code- 075856001600 Product code - Same product as 2nd line item
Duplicate Line Item
number /DUNS Number
Customer DUNS - 6955681032216 Verify Rule No 10 - Duplicate Line Item(DN Credit)from

DT - A6 product code 1- 075856001600 BOOMi for EDI
item
/DUNS Number
Customer DUNS - 2447263101788 Verify Rule No 12 - Invalid Customer(DN Credit)from
DT - A6 DUNS number - 2447263101788 BOOMi for EDI
1. Magento will receive EDI 810 file from BOOMI for Invalid
Customer DUNS number
number

DT - A6 DUNS number - DUNS number BOOMi for EDI
field is empty DUNS number - DUNS number field is empty

DT - A6 DUNS number - 6955681032216 BOOMi for EDI
1. Magento will receive EDI 810 file from BOOMI for valid
Customer
number /DUNS Number
Customer DUNS - 2447263101707 DT - A6 Verify Rule No 14 -No delivery date (DN Credit)from
Delivery date - if delivery date field is BOOMi for EDI
empty Delivery date - if delivery date field is empty
1. Magento will receive EDI 810 file from BOOMI for no
delivery date
number /DUNS Number
Customer DUNS - 2447263101707 DT - A6 Verify Rule No 14 - Delivery date (DN Credit)from BOOMi
Delivery date - if delivery date field is has for EDI
valid delivery date 1. Magento will receive EDI 810 file from BOOMI for
delivery date
number /DUNS Number
Customer DUNS - 2447263101707 DT - A6 Verify Rule No 15 - No line item (DN Credit)from BOOMi for
Product Code - if product code field is EDI
empty Product Code - if product code field is empty
1. Magento will receive EDI 810 file from BOOMI for No
line item
/DUNS Number
Customer DUNS - 2447263101707 DT - A6 Verify Rule No 15 - No line item (DN Credit)from BOOMi for
Product Code -077567002181 EDI
Product Code - if product code field is has any products
1. Magento will receive EDI 810 file from BOOMI for line
items
number /DUNS Number
Customer DUNS - 2447263101707 DT - A6 Verify Rule NO 19 - Total quantity exceeds total eaches
Product Code - 077567002181 Eaches- threshold - Requires
More than 50 Verification (DN Credit) from BOOMi for EDI
exceeds total eaches
4. Click on DN credit(Open) link under My dashboard
5. Search for that exceeds total eaches using delivery ticket
number /DUNS Number
Product Code - 077567002181 Eaches- threshold - Requires
Less than 50 or equal to 50 Verification (DN Credit) from BOOMi for EDI
4. Click on DN credit(Open) link under My dashboard
5. Search using delivery ticket number /DUNS Number
Customer DUNS - 0574990490069 Debit) for Flat file from MuleSoft .
PO - Should start with GUS and have 6 1. Magento will receive Flat file from MuleSoft for Go puff
digits(GUS876543) Customers having Customer PO starting with GUS and 6
char
4. Click on DN Debit (Open) link under My dashboard
Customer DUNS - 0574990490102 Debit) for Flat file from MuleSoft interface data
PO - Should have 6 digits but should not 1. Magento will receive Flat file from MuleSoft for Go puff
start with 'GUS'(SUG865432) Customers having Customer PO not starting with GUS and
6 char
Customer Banner - AFEES Verify Rule No 1 -Customer PO does not meet pattern (DN )
Customer DUNS - 6955681032216 for Flat file from MuleSoft interface data
char(VON763445232) 1. Magento will receive Flat file from MuleSoft for
For Customer Banner - AFEES Verify Rule No 1 -Customer PO does not meet pattern (DN )
for Flat file from MuleSoft interface data
Distributor - A3 AEFIS(Banner group)Customers - PO should starts with
Delivery Date(MM/DD/YYYY) 1. Magento will receive Flat file from MuleSoft for
9 char(NOV887765432) starting with VON and 9 char
DT - BK PO pattern for Flat file from MuleSoft interface data
Customer DUNS - 2447263112614 Normal Customers - it should accept with/without any data
PO - With any value or without value in Customer PO field
1. Magento will receive Flat file from MuleSoft
Customer DUNS - 0574990490102 length for Flat file from MuleSoft interface data
PO - Should start with 'GUS' but have less 1. Magento will receive Flat file from MuleSoft for Go puff
than 6 digits(GUS9876) Customers having Customer PO less than 6 char

PO - Should start with GUS but have more 1. Magento will receive Flat file from MuleSoft for Go puff
than 6 digits(GUS9876543) Customers having Customer PO more than 6 char
Customer Banner - AFEES Verify Rule No 1 -Customer PO does not meet pattern (DN)
Customer DUNS - 6955681063710 for Flat file from MuleSoft interface data
DT - BK AEFIS(Banner group)Customers - if Customer PO has less
than 9 char(VON9876) 1. Magento will receive Flat file from MuleSoft for
less than 9 char..

DT - BK AEFIS(Banner group)Customers - if Customer PO length is
more than 9 char(VON9765432456) 1. Magento will receive Flat file from MuleSoft for
less than 9 char..
Verify Rule No 1 -Customer PO does not meet pattern (DN
Customer DUNS - 0574990490069(Go Debit) for Flat file from MuleSoft interface data
Puff) GopuffCustomers- if Customer PO is empty
DT - BK 1. Magento will receive Flat file from MuleSoft for Go puff
Customer PO - empty(It should not accept Customers having Customer PO empty
if Customer PO field is empty) 2. Launch DT site and Login with valid data
Verify Rule No 1 -Customer PO does not meet pattern (DN )

Customer DUNS - 6955681063710(AFEES ) for Flat file from MuleSoft interface data
DT - BK AEFIS(Banner group)Customers - if Customer PO field is
Customer PO - empty(It should not accept empty
if Customer PO field is empty) 1. Magento will receive Flat file from MuleSoft for
as empty.
Verify Rule No 1 - For Customer groups that don't have any

Customer DUNS - 2447263112614 PO pattern for Flat file from MuleSoft interface data
Customer PO - any data in Customer PO field

Customer DUNS - 2447263105608 (DN Debit) for Flat file from MuleSoft interface data
DT - A3 Delivery date - if Delivery date is less than start date from
Delivery date - 2013-12-08 (YY-MM-DD) Customer hierarchy
(Start date 2013-12-07 it Should not 1. Magento will receive Flat file from MuleSoft
accept less than start date from Customer 2. Launch DT site and Login with valid data
hierarchy) 3. Navigate to that particular DT dashboard page
5. Search for that Delivery date which we receive less than
start using delivery ticket number /DUNS Number
(DN Debit) for Flat file from MuleSoft interface data
Customer DUNS - 2447263105608 Delivery date - if Delivery date is greater than end date
DT - A3 from Customer hierarchy
Delivery date - 9999-12-31 (YY-MM-DD) 1. Magento will receive Flat file from MuleSoft
(End date 9999-12-31 it Should not accept 2. Launch DT site and Login with valid data
greater than date from Customer 3. Navigate to that particular DT dashboard page
hierarchy) 4. Click on DN debit (Open) link under My dashboard
5. Search for that Delivery date which we receive greater
than end using delivery ticket number /DUNS Number
DT - A3 (DN Debit) for Flat file from MuleSoft interface data
Delivery date - 2013-12-08 and 9999-12- Delivery date - In between start and end date of Customer
31 it should accept In between start and Hierarchy.
end date of Customer Hierarchy. 1. Magento will receive Flat file from MuleSoft
5. Search for that Delivery date which we receive in
between start and end date of that Customer Hierarchy
using delivery ticket number /DUNS Number
DT - A3 Flat file from MuleSoft interface data
Delivery date (MM-DD-YY) it Should not Delivery date - Future Delivery date
accept future delivery dates. 1. Magento will receive Flat file from MuleSoft for delivery
date
number /DUNS Number
DT - A3 Flat file from MuleSoft interface data
Delivery date (MM-DD-YY) it should Delivery date - it should accept less than or equal to system
accept less than or equal to system date date .
1. Magento will receive Flat file from MuleSoft for delivery
date
number /DUNS Number
DT - A3 current date (DN Debit) for Flat file from MuleSoft
Delivery date (MM-DD-YY) if Delivery interface data
date is older than 90 days from current Delivery date - if Delivery date is older than 90 days from
date. current date.
1. Magento will receive Flat file from MuleSoft for older
number /DUNS Number
DT - A3 current date (DN Debit) for Flat file from MuleSoft
Delivery date (MM-DD-YY) if Delivery date interface data
is older than 90 days from current date. Delivery date - if Delivery date is in between 90 days from
current date.
1. Magento will receive Flat file from MuleSoft for between
90 days from current date.
number /DUNS Number

Customer DUNS - 8473400010001 from MuleSoft for Flat file
Delivery ticket number - without delivery empty
ticket number(it should not accept if 1. Magento will receive Flat file from MuleSoft for empty
delivery ticket number field is empty) delivery date
Number

Customer DUNS - 8473400010001 from MuleSoft for Flat file
DT - BK Delivery ticket number - if Debit DN has the Delivery ticket
Delivery ticket number - GUS772356 number
(With delivery ticket number) 1. Magento will receive Flat file from MuleSoft
Customer DUNS - 8473400010001 Debit) for same Customer from MuleSoft for Flat file
DT - BK 1. Magento will receive Flat file from MuleSoft for
(It should not accept in case of same 2. Launch DT site and Login with valid data
Customer PO for same Customer) 3. Navigate to that particular DT dashboard page

Customer DUNS - 8473400010001 Debit) for different Customer from MuleSoft for Flat file
(It should accept in case of same 2. Launch DT site and Login with valid data
Customer PO for diffCustomer) 3. Navigate to that particular DT dashboard page
Verify Rule No 8 - Duplicate Customer PO (DN Debit) for

Customer DUNS - 8473400010001 same Customer from MuleSoft for Flat file
(It should accept in case of unique 1. Magento will receive Flat file from MuleSoft for
Customer PO) Duplicate Customer PO
DT - BK (DN Debit) from MuleSoft for Flat file
Delivery ticket number- 8062223503 (It Delivery ticket number - Existed delivery ticket number
should not accept in case of same existing 1. Magento will receive Flat file from MuleSoft for existed
delivery ticket number) delivery ticket number

DT - BK (DN Debit) from MuleSoft for Flat file
Delivery ticket number- 8062223111 1. Magento will receive Flat file from MuleSoft for delivery
(It should accept in case of unique delivery ticket number
ticket number in delivery ticket number 2. Launch DT site and Login with valid data
field) 3. Navigate to that particular DT dashboard page
number /DUNS Number
DT - BK Debit) from MuleSoft for Flat file
product code- 075856031140 Product code - Same product as 2nd line item
Again same product code in 2nd line item 1. Magento will receive Flat file from MuleSoft for
- 075856031140 Duplicate Line Item
(It should not accept in case of if we 2. Launch DT site and Login with valid data
receive same product code as second line 3. Navigate to that particular DT dashboard page
item) 4. Click on DN Debit(Open) link under My dashboard
number /DUNS Number
Customer DUNS - 2447263112614 Verify Rule No 10 - Duplicate Line Item(DN Debit) from
DT - BK MuleSoft for Flat file
product code 2- 076840485116 item
(It should accept in case of diff line level 1. Magento will receive Flat file from MuleSoft
items) 2. Launch DT site and Login with valid data
/DUNS Number
Customer DUNS - 2447263105644 Verify Rule No 11 -Eaches not in full boxes (DN Debit) from
DT - A3 MuleSoft for Flat file
Product code - 077567002204 (Eaches Per Eaches - Eaches other than multiples of "eaches per box"
Box is 24) 1. Magento will receive Flat file from MuleSoft for Eaches
Eaches - 50 not in full boxes
(It should not accept in case of eaches 2. Launch DT site and Login with valid data
other than multiples of "eaches per box") 3. Navigate to that particular DT dashboard page
5. Search for that Eaches not in full boxes using delivery
Customer DUNS - 2447263105644 Verify Rule No 11 -Eaches in full boxes (DN Debit) from
Product code - 077567002204 (Eaches Per Eaches - Eaches should be multiples of "eaches per box"
Box is 24) 1. Magento will receive Flat file from MuleSoft for Eaches
Eaches - 48 in full boxes
(It should accept in case of multiples of 2. Launch DT site and Login with valid data
"eaches per box") 3. Navigate to that particular DT dashboard page
5. Search for that Eaches in full boxes using delivery ticket
number /DUNS Number
DUNS number - 2447263101788 DUNS number - Invalid Customer DUNS number
(It should not accept in case of invalid 1. Magento will receive Flat file from MuleSoft for Invalid
Duns number in DUNS number filed) Customer DUNS number
number

DUNS number - Empty DUNS number - DUNS number field is empty
(It should not accept in case of empty 1. Magento will receive Flat file from MuleSoft
Duns number in DUNS number filed) 2. Launch DT site and Login with valid data

DUNS number - 6955681032216 DUNS number - Valid Customer DUNS number
(It should accept in case of valid Duns 1. Magento will receive Flat file from MuleSoft for valid
number in DUNS number filed) Customer
number /DUNS Number
Customer DUNS - 2447263101707 Verify Rule No 13 - Invalid Product (DN Debit) from
Product code - 077567283030 DUNS number - Invalid Product code
(It should not accept in case of invalid 1. Magento will receive Flat file from MuleSoft for Invalid
Product code in product code field) Product
5. Search for that Invalid Product using delivery ticket
number /DUNS Number
Customer DUNS - 2447263101707 Verify Rule No 12 - Invalid Product (DN Debit) from
Product code - Empty DUNS number - Product code field is empty
(It should not accept in case of empty 1. Magento will receive Flat file from MuleSoft
Product code in product code field) 2. Launch DT site and Login with valid data
5. Search for that empty Product code using delivery ticket
number /DUNS Number
Customer DUNS - 2447263105644 Verify Rule No 13 - by receiving Invalid Product (DN Debit)
DT - A3 from MuleSoft for Flat file
Product code - 077567002204 1. Magento will receive Flat file from MuleSoft for valid
Valid Product code Product
(It should accept in case of valid Product 2. Launch DT site and Login with valid data
code in product code field) 3. Navigate to that particular DT dashboard page
5. Search for that valid Product using delivery ticket
number /DUNS Number
Customer DUNS - 2447263102456 Verify Rule No 14 -No delivery date (DN Debit) from
Delivery date field - Empty Delivery date - if delivery date field is empty
(It should not accept if delivery date field 1. Magento will receive Flat file from MuleSoft for no
is empty) delivery date
number /DUNS Number
Customer DUNS - 2447263102456 Verify Rule No 14 - Delivery date (DN Debit) from MuleSoft
DT - A3 for Flat file
Delivery date field - (MM/DD/YYYY) 1. Magento will receive Flat file from MuleSoft for delivery
(It should accept if delivery date field is date
has valid delivery date) 2. Launch DT site and Login with valid data
number /DUNS Number
Customer DUNS - Verify Rule No 15 - No line item (DN Debit) from MuleSoft
2447263105608_x0001_ for Flat file
DT - A3 Product Code - if product code field is empty
Product Code - Empty 1. Magento will receive Flat file from MuleSoft for No line
(It should not accept if product code field item
is empty ) 2. Launch DT site and Login with valid data
/DUNS Number
Customer DUNS - Verify Rule No 15 - No line item (DN Debit) from MuleSoft
2447263105608_x0001_ for Flat file
DT - A3 Product Code - if product code field is has any products
Delivery date (MM/DD/YYYY) 1. Magento will receive Flat file from MuleSoft for line
Product Code - 077567002228 items
(It should accept if product code field is 2. Launch DT site and Login with valid data
has any products) 3. Navigate to that particular DT dashboard page
number /DUNS Number
Customer DUNS - 2447263101707 DT - A6 Verify Rule No 16 -Product not listed(DN Debit) from
Product code -077567002887 MuleSoft for Flat file
(It should not accept in case of product Product code - if Product is not mapped to that Customer
code is not exist in system/Not mapped to 1. Magento will receive Flat file from MuleSoft for Product
that Customer) not listed
5. Search for that Product not listed using delivery ticket
number /DUNS Number
Customer DUNS - 6955681040307 Verify Rule No 16 -Product not listed(DN Debit) from
Delivery date - (MM/DD/YYYY) Product code - if Product are mapped to the Customer
Product code -075856001600 1. Magento will receive Flat file from MuleSoft
(It should accept in case of product code is 2. Launch DT site and Login with valid data
exist in system/mapped to that Customer) 3. Navigate to that particular DT dashboard page
5. Search for that Product is listed using delivery ticket
number /DUNS Number

DT - A8 requires verification (DN Debit) from MuleSoft for Flat file
Delivery date - (MM/DD/YYYY) GopuffCustomers - eaches more than 5 box's
Product code - 077567001238 (Eaches per 1. Magento will receive Flat file from MuleSoft for Quantity
Box -6) exceeds box Threshold
(GopuffCustomers - It should not accept in 3. Navigate to that particular DT dashboard page
case of eaches more than 5 box's) 4. Click on DN Debit(Open) link under My dashboard

Delivery date - (MM/DD/YYYY) GopuffCustomers - It should be 5 box's
(GopuffCustomers - It should accept in 3. Navigate to that particular DT dashboard page
case of eaches are 5 boxes or less than 5 4. Click on DN Debit(Open) link under My dashboard
(It should not accept in case of Food 3. Navigate to that particular DT dashboard page
Service migration - eaches more than 5 4. Click on DN Debit(Open) link under My dashboard

Delivery date -(MM/DD/YYYY) Food Service migration - It should be 5 box's
(It should accept in case of Food Service 3. Navigate to that particular DT dashboard page
migration - eaches is 5 boxes) 4. Click on DN Debit(Open) link under My dashboard

Product code - 076840100040(Eaches per 1. Magento will receive Flat file from MuleSoft
Box -6) 2. Launch DT site and Login with valid data
Eaches - 120 3. Navigate to that particular DT dashboard page
Normal Customers - it should accept any 4. Click on DN Debit(Open) link under My dashboard
value 5. Search using delivery ticket number /DUNS Number
Customer DUNS - 0574990490069 Credit)for Flat file from MuleSoft.
PO -GUS123456 1. Magento will receive Flat file from MuleSoft for Go puff
Customers having Customer PO starting with GUS and 6
char
Customer DUNS - 0574990490102 Credit)for Flat file from MuleSoft interface data
PO - ABC098765 1. Magento will receive Flat file from MuleSoft for Go puff
Customers having Customer PO not starting with GUS and
6 char
PO - VON123456789 VON
1. Magento will receive Flat file from MuleSoft for
PO - QWE123456789 VON
PO - Any value in Customer PO field
PO - Should start with 'GUS' but have less 1. Magento will receive Flat file from MuleSoft for Go puff
than 6 digits Customers having Customer PO less than 6 char

PO - Should start with GUS but have more 1. Magento will receive Flat file from MuleSoft for Go puff
than 6 digits Customers having Customer PO more than 6 char
Customer DUNS - 6955681063710 Credit) for Flat file from MuleSoft interface data
DT - A3 AEFIS(Banner group)Customers - if Customer PO has less
than 9 char 1. Magento will receive Flat file from MuleSoft for
less than 9 char..

more than 9 char 1. Magento will receive Flat file from MuleSoft for
less than 9 char..
DT - BK GopuffCustomers- if Customer PO is empty
PO - Should be empty 1. Magento will receive Flat file from MuleSoft for Go puff
Customers having Customer PO empty
DT - A3 AEFIS(Banner group)Customers - if Customer PO field is
PO - should be empty empty
as empty.
in Customer PO field
Delivery date Verify Rule No 5 - Delivery date in the future (DN Credit)for
Customer DUNS - 8473400010001 Flat file from MuleSoft interface data
DT - A8 Delivery date - Future Delivery date
Delivery date - it Should accept future 1. Magento will receive Flat file from MuleSoft for delivery
delivery dates. date
number /DUNS Number
Delivery date Verify Rule No 5 - Delivery date in the future (DN Credit)for
Customer DUNS - 8473400010001 Flat file from MuleSoft interface data
DT - A8 Delivery date - it should accept less than or equal to system
Delivery date - it Should accept old 90 date .
days from current date. 1. Magento will receive Flat file from MuleSoft for delivery
date
number /DUNS Number
Delivery date - (System should not accept Verify Rule No 6 - Delivery date less than allowable days of
the older than 90 days from current date) current date (DN Credit)for Flat file from MuleSoft
Customer DUNS - 8473400010001 interface data
DT - A8 Delivery date - if Delivery date is older than 90 days from
Delivery date - it Should not accept less current date.
than start date 1. Magento will receive Flat file from MuleSoft for older
number /DUNS Number
Delivery date Verify Rule No 6 - Delivery date less than allowable days of
Customer DUNS - 8473400010001 current date (DN Credit)for Flat file from MuleSoft
DT -A8 interface data
Delivery date - it Should accept old 90 Delivery date - if Delivery date is in between 90 days from
days from current date. current date.
1. Magento will receive Flat file from MuleSoft for between
90 days from current date.
number /DUNS Number
Verify Rule No 7 - Delivery ticket no missing (DN

Customer DUNS - 8473400010001 Credit)from MuleSoft for Flat file
Delivery ticket number - Should be empty empty
1. Magento will receive Flat file from MuleSoft for empty
delivery date
Number
Verify Rule No 7 - Delivery ticket no missing (DN
Customer DUNS - 8473400010001 Credit)from MuleSoft for Flat file
DT - BK Delivery ticket number - if Credit DN has the Delivery ticket
Delivery ticket number - Should have number
delivery ticket number 1. Magento will receive Flat file from MuleSoft

Customer DUNS - 8473400010001 Credit)for same Customer from MuleSoft for Flat file

Customer DUNS - 8473400010001 Credit)for different Customer from MuleSoft for Flat file
Verify Rule No 8 - Duplicate Customer PO (DN Credit)for

Customer DUNS - 8473400010001 same Customer from MuleSoft for Flat file
DT - A6 Delivery ticket number- same (DN Credit)from MuleSoft for Flat file
existing delivery ticket number Delivery ticket number - Existed delivery ticket number
1. Magento will receive Flat file from MuleSoft for existed
DT - A6 Delivery ticket number- unique (DN Credit)from MuleSoft for Flat file
delivery ticket number 1. Magento will receive Flat file from MuleSoft for delivery
ticket number
number /DUNS Number
DT - A6 product code- 075856001600 Credit)from MuleSoft for Flat file
again same product code- 075856001600 Product code - Same product as 2nd line item
Duplicate Line Item
number /DUNS Number
Customer DUNS - 6955681032216 Verify Rule No 10 - Duplicate Line Item(DN Credit)from

DT - A6 product code 1- 075856001600 MuleSoft for Flat file
item
/DUNS Number

DT - A6 DUNS number - 2447263101788 MuleSoft for Flat file
1. Magento will receive Flat file from MuleSoft for Invalid
Customer DUNS number
number

DT - A6 DUNS number - DUNS number MuleSoft for Flat file
field is empty DUNS number - DUNS number field is empty
DT - A6 DUNS number - 6955681032216 MuleSoft for Flat file
1. Magento will receive Flat file from MuleSoft for valid
Customer
number /DUNS Number
"""Customer DUNS - 2447263101707 DT - Verify Rule No 14 -No delivery date (DN Credit)from
A6 MuleSoft for Flat file
Delivery date - if delivery date field is Delivery date - if delivery date field is empty
empty 1. Magento will receive Flat file from MuleSoft for no
delivery date
number /DUNS Number
Customer DUNS - 2447263101707 DT - A6 Verify Rule No 14 - Delivery date (DN Credit)from MuleSoft
Delivery date - if delivery date field is has for Flat file
valid delivery date 1. Magento will receive Flat file from MuleSoft for delivery
date
number /DUNS Number
Customer DUNS - 2447263101707 DT - A6 Verify Rule No 15 - No line item (DN Credit)from MuleSoft
Product Code - if product code field is for Flat file
empty Product Code - if product code field is empty
1. Magento will receive Flat file from MuleSoft for No line
item
/DUNS Number
Customer DUNS - 2447263101707 DT - A6 Verify Rule No 15 - No line item (DN Credit)from MuleSoft
Product Code - if product code field is has for Flat file
any products Product Code - if product code field is has any products
1. Magento will receive Flat file from MuleSoft for line
items
number /DUNS Number
Product Code - if product code field is has threshold - Requires
any products Verification (DN Credit) from MuleSoft for Flat file
Eaches- More than 50 Eaches - more than 50 eaches
1. Magento will receive Flat file from MuleSoft for exceeds
total eaches
5. Search for that exceeds total eaches using delivery ticket
number /DUNS Number
Product Code - if product code field is has threshold - Requires
any products Verification (DN Credit) from MuleSoft for Flat file
Eaches - Less than 50 or equal to 50. Eaches - Less than or equals to 50 eaches
5. Search using delivery ticket number /DUNS Number
Verify whether user able to launch DT site.

1. Open the browser and enter the site URL
Verify whether DT user is able to directly login to DT
dashboard.
1. Launch the app and login with the valid credentials.
Verify if DT administrative is able to login to the site

1. Launch the app and login with the valid credentials for
DT administrative.
Verify by clicking on any DT on account to
proceed page
1. Launch the app .
2. Login with DT Administrator valid data
3. Click on any DT
Verify by clicking on Create DN Debit under My task or

TODOs section
1. Launch the app .
2. Login with DT Administrator/DT with valid data
3. Click on any DT and navigate to that particular DT
Dashboard page
4. Click on Create DN Debit under My tasks or TODOs
section
Customer DUNS - 0574990490069 Verify Customer PO does not meet pattern by giving invalid
DT - BK pattern
PO - Should start with prefix based on the 1. Launch the app .
Customer banner group followed with 2. Login with DT Administrator valid data
characters or digits 3. Click on any DT and navigate to that particular DT
Dashboard page
4. Click on Create DN Debit under My tasks or TODOs
section and redirected to DN - Delivery ticket page
5. Enter any DUNS number and select any store 6. Enter
delivery date and delivery ticket no.
6. Enter any invalid Customer PO number and click on
validate and submit button
Customer Banner - Go Puff Verify Customer PO does not meet pattern by giving invalid
Customer DUNS - 0574990490069 pattern for GopuffCustomers
DT - BK 1. Launch the app .
PO - Should not start with GUS and have 6 2. Login with DT Administrator valid data
digits (POI654321) 3. Click on any DT and navigate to that particular DT
It should give invalid pattern error Dashboard page
4. Click on Create DN Debit under My task or TODOs
section and redirected to DN - Debit Entry page
5. Enter any DUNS number and select any store
6. Enter any invalid pattern of Customer PO number and
click on validate and submit button
Customer DUNS - 0574990490069 pattern for GopuffCustomers
PO - Should start with GUS and have 6 2. Login with DT Administrator/DT with valid data
digits(GUS998876) 3. Click on any DT and navigate to that particular DT
It should accept the value. Dashboard page
6. Enter valid pattern of Customer PO number and click on
Customer Banner - Go Puff Verify If user try to submit the form without giving any
Customer DUNS - 0574990490069 Customer PO in Customer PO field for GopuffCustomers.
DT - BK (ex. starts with Gus and has 6 char(GoPuff), PO start
PO -No value digits/letters, length.)
[{"prefix":"GUT","condition_group":18}
1. Launch the app .
Dashboard page
6. Click on validate and submit button without giving any
Customer PO number.
Customer Banner - AFEES Verify Customer PO does not meet pattern by giving invalid
Customer DUNS - 6955681032216 pattern for AEFIS(Banner group) Customers
DT - A3 1. Launch the app .
PO - PLB123456789 2. Login with DT Administrator valid data
Dashboard page
Customer Banner - AFEES Verify Customer PO does not meet pattern by giving invalid
PO - VON123456789 2. Login with DT Administrator/DT with valid data
Dashboard page
Customer Banner - AFEES Verify If user try to submit the form without giving any
Customer DUNS - 6955681032216 Customer PO in Customer PO field for AEFIS(Banner group)
DT - A3 Customers.
PO - No data (ex. starts with Gus and has 6 char(AEFIS(Banner group) ),
PO start digits/letters, length.)
1. Launch the app .
Dashboard page
Customer PO number.
Customer DUNS - 6955681032216 Verify Rule No 1 - If Customer groups don't have prefix
DT - A3 (pattern)
PO - 123345589987 It should give 1. Launch the app .
"Customer PO does not meet pattern" 2. Login with DT Administrator/DT with valid data
error. 3. Click on any DT and navigate to that particular DT
Dashboard page
6. Click on validate and submit button with/without any
data giving any Customer PO number.
Customer Banner - AFEES Verify Customer PO larger than maximum length

Customer DUNS - 6955681032216 1. Launch the app .
DT - A3 2. Login with DT Administrator valid data
PO - VON1234567890 It should give error 3. Click on any DT and navigate to that particular DT
message as "Customer PO larger than Dashboard page
maximum length" 4. Click on Create DN Debit under My task or TODOs
6. Enter greater than or equal to 9 and click on validate and
submit button
Customer Banner - Go Puff Verify If user try to submit the form with less than
Customer DUNS - 0574990490069 6charCustomer PO in Customer PO field for
DT - BK GopuffCustomers.
PO -GUS123 It should give error message 1. Launch the app .
as "Customer PO larger than maximum 2. Login with DT Administrator/DT with valid data
length" 3. Click on any DT and navigate to that particular DT
Dashboard page
6. Enter less than 6char and Click on validate and submit
button without giving any Customer PO number.
Customer Banner - Go Puff Verify If user try to submit the form with greater than
PO -GUS345876321 It should give error 1. Launch the app .
message as "Customer PO larger than 2. Login with DT Administrator/DT with valid data
maximum length" 3. Click on any DT and navigate to that particular DT
Dashboard page
6. Enter greater than 6char and Click on validate and
submit button without giving any Customer PO number.
"Customer Banner - AFEES Verify If user try to submit the form with less than
Customer DUNS - 6955681032216 9charCustomer PO in Customer PO field for AEFIS(Banner
DT - A3 group) Customers.
PO - VON1234567 It should give error 1. Launch the app .
message as ""Customer PO larger than 2. Login with DT Administrator/DT with valid data
maximum length""" 3. Click on any DT and navigate to that particular DT
Dashboard page
"Customer Banner - AFEES Verify If user try to submit the form with greater than
Customer DUNS - 6955681032216 9charCustomer PO in Customer PO field for AEFIS(Banner
PO - VON876543215678 It should give 1. Launch the app .
error message as ""Customer PO larger 2. Login with DT Administrator/DT with valid data
than maximum length""" 3. Click on any DT and navigate to that particular DT
Dashboard page
Customer Banner - Go Puff Verify Rule No 2 - If Customer PO doesn't have any specific
Customer DUNS - 0574990490069 length
PO - 12 It should give error message as 2. Login with DT Administrator/DT with valid data
"Customer PO larger than maximum 3. Click on any DT and navigate to that particular DT
length" Dashboard page
6. Click on validate and submit button with any
data/without giving any Customer PO number.
Verify Date outside retailer's operation date (DN Debit)

Delivery date - 2013-12-08 (YY-MM-DD) 3. Click on any DT and navigate to that particular DT
(Start date 2013-12-07 it Should not Dashboard page
accept less than start date from Customer 4. Click on Create DN Debit under My task or TODOs
hierarchy) section and redirected to DN - Debit Entry page
6. Select any less than start or greater than end date and
Click and Validate and submit button.

Customer DUNS - 2447263105608 (DN Debit) - Select any less than start of Customer
DT - A3 Hierarchy1. Launch the app .
Delivery date - 2013-12-08 (YY-MM-DD) 2. Login with DT Administrator valid data
(Start date 2013-12-07 it Should not 3. Click on any DT and navigate to that particular DT
accept less than start date from Customer Dashboard page
hierarchy) 4. Click on Create DN Debit under My task or TODOs
6. Select any less than start and Click and Validate and
submit button.
(Open Magento Admin --> Uniliver Creme Customer
Hierarchy - search for that particular Customer)
DT - A3 (DN Debit) - Select any greater than end date of Customer
Delivery date - 9999-12-31 (YY-MM-DD) Hierarchy
(End date 9999-12-31 it Should not accept 1. Launch the app .
greater than date from Customer 2. Login with DT Administrator valid data
hierarchy) 3. Click on any DT and navigate to that particular DT
Dashboard page
6. Select any greater than end date of Customer Hierarchy
and Click and Validate and submit button.
(Open Magento Admin --> Uniliver Creme Customer
Hierarchy - search for that particular Customer)
DT - A3 (DN Debit) - Verify by selecting any in between start or end
Delivery date - 2013-12-08 and 9999-12- date
31 it should accept In between start and 1. Launch the app .
end date of Customer Hierarchy. 2. Login with DT Administrator valid data
Dashboard page
6. Select any in between start or end date and Click and
Validate and submit button.
Customer DUNS - 2447263105608 Verify Delivery date in the future (DN Debit)
Delivery date (MM-DD-YY) it Should not 2. Login with DT Administrator valid data
accept future delivery dates. 3. Click on any DT and navigate to that particular DT
Dashboard page
6. Select future delivery date and Click and Validate and
submit button.
Customer DUNS - 2447263105608 Delivery date less than allowable days of current date
Delivery date MM-DD-YY system should 2. Login with DT Administrator valid data
accept if Delivery date is older than 90 3. Click on any DT and navigate to that particular DT
days from current date Dashboard page
6. Select delivery date older than 90 days from current
date and Click and Validate and submit button.
Customer DUNS - 8473400010001 Delivery ticket no missing

Delivery ticket number - Empty 2. Login with DT Administrator valid data
(it should not accept if delivery ticket 3. Click on any DT and navigate to that particular DT
number field is empty) Dashboard page
6. Click on Validate and submit button without delivery
ticket number
Customer DUNS - 8473400010001 Verify by entering the existing Customer PO number of

DT - BK same Customer
Customer PO - GUT705332 - it should be 1. Launch the app .
unique for same Customer 2. Login with DT Administrator valid data
(It should not accept in case of same 3. Click on any DT and navigate to that particular DT
Customer PO for same Customer) Dashboard page
6. Enter existing Customer PO number in Customer PO text
box and click on Validate and submit button.
Customer DUNS - 8473400010001 Verify by entering the existing Customer PO number of
DT - BK different Customer 1. Launch the app .
Customer PO - GUT705332 2. Login with DT Administrator valid data
(It should accept in case of same 3. Click on any DT and navigate to that particular DT
Customer PO for diffCustomer) Dashboard page
Customer DUNS - 2447263112614 Duplicate delivery ticket no

Delivery ticket number- 8062223503 (It 2. Login with DT Administrator valid data
should not accept in case of same existing 3. Click on any DT and navigate to that particular DT
delivery ticket number) Dashboard page
6. Enter existing delivery ticket number in delivery ticket
text box and click on Validate and submit button.
Customer DUNS - 2447263112614 Verify Rule No 9 - by giving Unique delivery ticket no (DN
DT - BK Debit)
Delivery ticket number- 8062265 1. Launch the app .
(It should accept in case of unique delivery 2. Login with DT Administrator valid data
ticket number in delivery ticket number 3. Click on any DT and navigate to that particular DT
field) Dashboard page
6. Enter any unique delivery ticket number in delivery
ticket text box and click on Validate and submit button.
Customer DUNS - 2447263112614 Duplicate Line Item

product code- 2. Login with DT Administrator valid data
1st line item - 075856031140 3. Click on any DT and navigate to that particular DT
2nd line item - 075856031140 Dashboard page
(It should not accept in case of if we 4. Click on Create DN Debit under My task or TODOs
receive same product code as second line section and redirected to DN - Debit Entry page
item) 5. Enter any DUNS number and select any store
6. Enter product code in product code field and select the
product and again give same product code in 2nd line
product code field and click on Validate and submit
button.
Customer DUNS - 2447263112614 Eaches not in full boxes

product code 1- 076840100125 2. Login with DT Administrator valid data
product code 2- 076840485116 3. Click on any DT and navigate to that particular DT
(It should accept in case of diff line level Dashboard page
items) 4. Click on Create DN Debit under My task or TODOs
product
7. Enter other than multiple of eaches in eaches box and
click on Validate and submit button.
Customer DUNS - 2447263105644 Verify Rule No 11 -by giving Eaches in full boxes (DN Debit)
Product code - 077567002204 (Eaches Per 2. Login with DT Administrator valid data
Box is 24) 3. Click on any DT and navigate to that particular DT
Eaches - 50 Dashboard page
(It should not accept in case of eaches 4. Click on Create DN Debit under My task or TODOs
other than multiples of "eaches per box") section and redirected to DN - Debit Entry page
product
7. Enter multiple of eaches in eaches box and click on
Customer DUNS - 2447263105644 Verify Rule No 11 -Eaches in full boxes (DN Debit)
DT - A3 Eaches - Eaches should be multiples of "eaches per box"
Product code - 077567002204 (Eaches Per 1. Launch the app .
Box is 24) 2. Login with DT Administrator valid data
Eaches - 48 3. Click on any DT and navigate to that particular DT
(It should accept in case of multiples of Dashboard page
"eaches per box") 4. Click on Create DN Debit under My task or TODOs
product
7. Enter multiple of eaches in eaches box and click on
Customer DUNS - 2447263101788 Invalid Customer

DUNS number - 2447263101788 2. Login with DT Administrator valid data
(It should not accept in case of invalid 3. Click on any DT and navigate to that particular DT
Duns number in DUNS number filed) Dashboard page
5. enter Invalid Customer DUNS number in DUNS number
files and click on validate and submit form.
Customer DUNS - 2447263101707 Verify Rule No 12 - Invalid Customer(DN Debit)

DT - A6 DUNS number - DUNS number field is empty
DUNS number - Empty 1. Launch the app .
(It should not accept in case of empty 2. Login with DT Administrator valid data
Duns number in DUNS number filed) 3. Click on any DT and navigate to that particular DT
Dashboard page
Customer DUNS - 2447263101707 Verify Rule No 12 - by giving valid Customer(DN Debit)

DUNS number - 6955681032216 2. Login with DT Administrator valid data
(It should accept in case of valid Duns 3. Click on any DT and navigate to that particular DT
number in DUNS number filed) Dashboard page
5. enter valid Customer DUNS number in DUNS number
Customer DUNS - 2133964802300 Invalid Product
Product code - 041000053152 2. Login with DT Administrator valid data
Invalid Product code 3. Click on any DT and navigate to that particular DT
(It should give error message as "Invalid Dashboard page
product") 4. Click on Create DN Debit under My task or TODOs
6. Enter invalid product code in product code field
7. click on Validate and submit button.
Customer DUNS - 2133964802300 Verify Rule No 13 - by giving valid Product code (DN Debit)
Invalid Product code 3. Click on any DT and navigate to that particular DT
(It should accept) Dashboard page
6. Enter valid product code in product code field
DUNS number - 2133964866600 No delivery date

Delivery date - Empty 2. Login with DT Administrator valid data
It should not accept if delivery date field is 3. Click on any DT and navigate to that particular DT
empty. Dashboard page
6. without selecting any delivery date click on Validate and
submit button.
DUNS number - 2133964866600 Verify Rule No 14 - by selecting delivery date (DN Debit)
Delivery date -(MM/DD/YYYY) 2. Login with DT Administrator valid data
It should accept if delivery date is selected 3. Click on any DT and navigate to that particular DT
Dashboard page
6. Select any delivery date click on Validate and submit
button.
DUNS number - 2133964866600 No line item.

Delivery date - (MM/DD/YYYY) 2. Login with DT Administrator valid data
Product code - Empty 3. Click on any DT and navigate to that particular DT
It should not accept if product field is Dashboard page
empty 4. Click on Create DN Debit under My task or TODOs
6. Click on validate and submit button without
Selecting products.
DUNS number - 2133964866600 Verify Rule No 15 - by giving any line item (DN Debit)
Product code - 077567001559 3. Click on any DT and navigate to that particular DT
It should accept if products date is Dashboard page
selected 4. Click on Create DN Debit under My task or TODOs
6. Click on validate and submit button with
Selecting products.
Customer DUNS - 2447263101707 DT - A6 Product not listed

Product code -077567002887 1. Launch the app .
(It should not accept in case of product 2. Login with DT Administrator valid data
code is not exist in system/Not mapped to 3. Click on any DT and navigate to that particular DT
that Customer) Dashboard page
6. Enter product code in product code field which is not
mapped to that retailer.

DT - A8 requires verification (DN Debit)
Delivery date - (MM/DD/YYYY) GopuffCustomers - eaches more than 5 boxes
Product code - 077567001238 (Eaches per 1. Launch the app .
Box -6) 2. Login with DT Administrator valid data
(GopuffCustomers - It should not accept in Dashboard page
case of eaches more than 5 box's) 4. Click on Create DN Debit under My task or TODOs
6. Enter product code in product code field
7. Enter eaches more than 5 box's

Delivery date - (MM/DD/YYYY) GopuffCustomers - It should be 5 boxes
(GopuffCustomers - It should accept in Dashboard page
case of eaches are 5 box's or less than 5 4. Click on Create DN Debit under My task or TODOs
box's) section and redirected to DN - Debit Entry page
7. Enter eaches as 5 box's
(It should not accept in case of Food Dashboard page
Service migration - eaches more than 5 4. Click on Create DN Debit under My task or TODOs
box's) section and redirected to DN - Debit Entry page
7. Enter eaches more than 5 box's

(It should accept in case of Food Service Dashboard page
migration - eaches is 5 box's) 4. Click on Create DN Debit under My task or TODOs
7. Enter eaches as 5 box's

Product code - 076840100040(Eaches per 1. Launch the app .
Normal Customers - it should accept any Dashboard page
value 4. Click on Create DN Debit under My task or TODOs
7. Enter any value in eaches box
Duns number - 0574990490069 Sub – Distributor Missing

it should not accept id Sub- DT is missing 3. Click on any DT and navigate to that particular DT
Dashboard page
Duns number - 0574990490102 Verify Rule No 18 - if Sub - Distributor is mapped

Dashboard page
PO - Should start with GUS and have 6 2. Login with DT Administrator valid data
digits(GUS556678) 3. Click on any DT and navigate to that particular DT
Dashboard page
4. Click on Create DN Credit under My task or TODOs
section and redirected to DN - Credit Entry page
PO - Should have 6 digits but should not 2. Login with DT Administrator/DT with valid data
start with 'GUS'(SWQ987567) 3. Click on any DT and navigate to that particular DT
Dashboard page
Customer Banner - AFEES Verify If user try to submit the form without giving any
Customer DUNS - 6955681032216 Customer PO in Customer PO field for AEFIS(Banner
PO - Should start with 'VON' and have 9 (ex. starts with Gus and has 6 char(AEFIS(Banner group) ),
char(VON988876543) PO start digits/letters, length.)
1. Launch the app .
Dashboard page
Customer PO number.
For Customer Banner - AFEES Verify Rule No 1 - If Customer groups don't have prefix
(pattern)
Distributor - ARC (A3) 1. Launch the app .
Customer DUNS - 6955681032216 2. Login with DT Administrator/DT with valid data
Delivery Date 3. Click on any DT and navigate to that particular DT
PO - Should not start with 'VON' and have Dashboard page
9 char(NER985433345) 4. Click on Create DN Credit under My task or TODOs
6. Click on validate and submit button with/without any
data giving any Customer PO number.
For Customer Banner - Family Dollar Verify If user try to submit the form with less than
6charCustomer PO in Customer PO field for
PO - With any value or without value 2. Login with DT Administrator/DT with valid data
Dashboard page
Customer Banner - Go Puff Verify If user try to submit the form with less than
PO - Should start with 'GUS' but have less 1. Launch the app .
than 6 digits(GUS99274) 2. Login with DT Administrator/DT with valid data
Dashboard page
Customer Banner - Go Puff Verify If user try to submit the form with greater than
PO - Should start with GUS but have more 1. Launch the app .
than 6 digits(GUS9033456) 2. Login with DT Administrator/DT with valid data
Dashboard page
Customer Banner - AFEES Delivery ticket no missing

PO - Should start with 'VON' and have less 3. Click on any DT and navigate to that particular DT
than 9 char(VON345765) Dashboard page
6. Click on Validate and submit button without delivery
ticket number
Customer Banner - AFEES Verify by entering the existing Customer PO number of
Customer DUNS - 6955681063710 same Customer
PO - Should start with 'VON' and have 2. Login with DT Administrator valid data
more than 9 char(VON4456934567) 3. Click on any DT and navigate to that particular DT
Dashboard page
Customer Banner - Go Puff Verify by entering the existing Customer PO number of

Customer DUNS - 0574990490069 different Customer 1. Launch the app .
DT - BK 2. Login with DT Administrator valid data
PO - Should be empty 3. Click on any DT and navigate to that particular DT
Dashboard page
Customer Banner - AFEES Duplicate delivery ticket no

PO - should be empty 3. Click on any DT and navigate to that particular DT
Dashboard page
6. Enter existing delivery ticket number in delivery ticket
text box and click on Validate and submit button.
Customer Banner - Family Dollar "Verify Rule No 9 - by giving Unique delivery ticket no (DN
Customer DUNS - 2447263112614 Credit)
Dashboard page
6. Enter any unique delivery ticket number in delivery
ticket text box and click on Validate and submit button."
DUNS number - 1457889201478 Duplicate Line Item

Product code - 2. Login with DT Administrator valid data
1st line item - 077567132819 3. Click on any DT and navigate to that particular DT
2nd line item also - 077567132819 Dashboard page
In this case it should not accept the same 4. Click on Create DN Credit under My task or TODOs
product item to 2nd line item section and redirected to DN - Credit Entry page
product and again give same product code in 2nd line
product code field and click on Validate and submit
button.
DUNS number - 1457889200008 Invalid Customer
It should not accept any invalid DUNS 2. Login with DT Administrator valid data
number. 3. Click on any DT and navigate to that particular DT
Dashboard page
DUNS number - 1457889201478 Verify Rule No 12 - by giving valid Customer(DN Credit)

Dashboard page
5. enter valid Customer DUNS number in DUNS number
DUNS number - 2133964866600 Verify Rule No 14 - by selecting delivery date (DN Credit)
Delivery date - Empty 2. Login with DT Administrator valid data
It should not accept if delivery date field is 3. Click on any DT and navigate to that particular DT
empty. Dashboard page
button.
DUNS number - 2133964866600 Verify Rule No 14 - by selecting delivery date (DN Credit)
It should accept if delivery date is selected 3. Click on any DT and navigate to that particular DT
Dashboard page
button.
DUNS number - 2133964866600 No line item.

Product code - Empty 3. Click on any DT and navigate to that particular DT
It should not accept if product field is Dashboard page
empty 4. Click on Create DN Credit under My task or TODOs
6. Click on validate and submit button without
Selecting products.
DUNS number - 2133964866600 Verify Rule No 15 - by giving any line item (DN Credit)
Delivery date (MM/DD/YYYY) 2. Login with DT Administrator valid data
Product code - 077567001559 3. Click on any DT and navigate to that particular DT
It should accept if products date is Dashboard page
selected 4. Click on Create DN Credit under My task or TODOs
6. Click on validate and submit button with
Selecting products.
DUNS number - 2133964866600 Total quantity exceeds

DT - A8 total eaches threshold - Requires verification
Delivery date (MM/DD/YYYY) 1. Launch the app .
Eaches- 55 It should give pop up message 3. Click on any DT and navigate to that particular DT
as "The total quantity exceeds the Dashboard page
allowable quantity of 50 eaches. Unilever 4. Click on Create DN Credit under My task or TODOs
is required to approve this credit ticket. section and redirected to DN - Credit Entry page
Do you want to Save?" 5. Enter any DUNS number and select any store
6. Enter product code in product code field.
7. Enter eaches more than 50.
8. Click on validate and submit button
DUNS number - 2133964866600 Total quantity not exceeding

DT - A8 total eaches threshold - Does not require verification
Delivery date (MM/DD/YYYY) 1. Launch the app .
Eaches- 49 3. Click on any DT and navigate to that particular DT
It should accept based on the eaches. Dashboard page
6. Enter product code in product code field.
7. Enter eaches less than 50.
8. Click on validate and submit button
Save the form with any error Verify by clicking Save button after clicking on validate and
Ex:- submit button with errors for DN Debit form
DUNS number - 2133964866600 1. Launch the app .
Delivery date (MM/DD/YYYY) 3. Click on any DT and navigate to that particular DT
Product code - 077567001559 Dashboard page
Delivery ticket number - empty 4. Click on Create DN Debit under My task or TODOs
6. Click on validate and submit button with errors and after
click on save button
Expected Result
Actual Result
It should not show any error message in Customer PO
field if we receive valid Customer PO number from
BOOMI for EDI
It should show an "Customer PO does not meet pattern."

error message in Customer PO field if we receive invalid
pattern from BOOMI for EDI

BOOMI for EDI

field.
It should show an "Customer PO smaller than length."

It should show an "Customer PO larger than maximum

length" error message in Customer PO field if we receive
invalid pattern from BOOMI for EDI
It should show an "Customer PO smaller than required

It should show an "Customer PO required." error

message in Customer PO field if we receive empty PO
from BOOMI for EDI for go puff
It should show an "Customer PO required" error

from BOOMI for EDI.

field.
Customer PO will be same as DN ticket number
It should show an " Date outside retailer's operation
date " error message on delivery date field if we receive
delivery date less than start date(Customer Hierarchy)
from BOOMI for EDI file.

date " error message on delivery date field if we receive
delivery date greater than end date(Customer Hierarchy)
from BOOMI for EDI file.
It should not show any error message in Delivery date

field if we receive any date (old 90 days from current
date.) in between start and end date of Customer
Hierarchy.
It should show an "Delivery date should not be greater

than system date.' error message in Delivery date field if
we receive any future date as delivery date from BOOMI
for EDI
field if we receive valid delivery date from BOOMI for EDI
It should show an "Delivery date less than allowable days

of current date " error message in delivery date field If
user receive delivery date older than 90 days from
current date from BOOMI for EDI

If user receive empty delivery ticket number from

BOOMI for EDI then it should show "Delivery ticket no
missing" error message in Delivery ticket field.
If user receive delivery ticket number from BOOMI for
EDI then it should not show any error message in
Delivery ticket field.
If user receive any existing Customer PO number from

BOOMi for EDI
for same Customer then it should show "Duplicate
Customer PO" error message in Customer PO field

BOOMi for EDI for different Customer then it should not
show any error message in Customer PO field
If user receive any unique Customer PO number from

BOOMi for EDI for existed Customer then it should not
If user receives any existed delivery ticket number from

BOOMi for EDI in delivery ticket field then it should
shows an "Delivery ticket number already used" error
message in Delivery ticket number field.
If user receives any unique delivery ticket number from
BOOMi for EDI in delivery ticket field then it shouldn't
show any error message in delivery ticket number field.
If user receives same product code as 2nd line item from

BOOMi for EDI in product code field then it show an
"Duplicate Line Item" error message on product code
field
If user receives different diff line item from BOOMi for

EDI in product code field then it should not show any
error message on product code field
if user receives eaches other than multiples of "eaches

per box" from BOOMi for EDI then it should show
"Eaches not in full boxes" on eaches box.
if user receives eaches multiples of "eaches per box"

form BOOMI for EDI then user shouldn't get show any
error message.
If user revives Invalid Customer DUNS number in DUNS
number field from BOOMi for EDI then it should show
"Invalid Customer" error message on DUNS number field
If user revives empty Customer DUNS number in DUNS

If user revives valid Customer DUNS number in DUNS

number field from BOOMi for EDI then it should not
show any error message on DUNS number field
If user receives Invalid Product code in Product code

field from BOOMI for EDI then the it should show
"Invalid product " error message on product code field.
If user revives empty in product code field from BOOMi

for EDI then it should show "Invalid product" error
message product code field.
If user receives valid Product code in Product code field
from BOOMI for EDI then it should not show any error
message on product code field.
If user receive the form without any delivery date from

BOOMi for EDI then it should show "no delivery date"
error message on delivery date field.
If user receive the form with any valid delivery date from
BOOMi for EDI then it should not show any error
message on delivery date field
If user receive the form without any line items from

BOOMi for EDI then user should show " Product line
items are missing "error message

BOOMi for EDI then user should not show any error
message.
If user receives product code that is not mapped to the
retailer in the product code field, from BOOMI for EDI
then it should show “Product not listed” error message
on product code field.
If user receives product code that is mapped to that

retailer in the product code field from BOOMI for EDI
then it should not show any error message on product
code field.
If user receives more than 5 boxes for GopuffCustomers

from BOOMI for EDI then it should show "Quantity
exceeds box Threshold " error message in eaches box.
If user receives less than or equals 5 boxes for

GopuffCustomers from BOOMI for EDI then it should not
show any error message in eaches box.
If user receives more than 5 boxes for Food Service

migration from BOOMI for EDI then it should show
"Quantity exceeds box Threshold " error message in
eaches box.
If user receives less than or equals 5 boxes for Food
Service migration from BOOMI for EDI then it should not
show any error message in eaches box.
If user receives eaches in more than or less than 5 boxes

from BOOMI for EDI then should show any error
message.

BOOMI for EDI


BOOMI for EDI

field.




from BOOMI for EDI for go puff

from BOOMI for EDI.
field.

we receive any future date as delivery date from BOOMI
for EDI


current date from BOOMI for EDI

BOOMI for EDI then it should show "Delivery ticket no
missing" error message in Delivery ticket field.
If user receive delivery ticket number from BOOMI for

EDI then it should not show any error message in

BOOMi for EDI

BOOMi for EDI for different Customer then it should not
BOOMi for EDI for existed Customer then it should not

BOOMi for EDI in delivery ticket field then it should

BOOMi for EDI in delivery ticket field then it shouldn't
show any error message in delivery ticket number field.

BOOMi for EDI in product code field then it show an
"Duplicate Line Item" error message on product code
field
If user receives different diff line item from BOOMi for

EDI in product code field then it should not show any


number field from BOOMi for EDI then it should not
show any error message on DUNS number field

BOOMi for EDI then it should show "no delivery date"
error message on delivery date field.
BOOMi for EDI then it should not show any error
BOOMi for EDI then user should show " Product line
items are missing "error message

BOOMi for EDI then user should not show any error
message.
If user receives eaches more than 50 from BOOMi for

EDI then it should show "The total quantity exceeds the
allowable quantity of 50 eaches. Do you want to approve
and submit the form?" error message
If user receives eaches more than 50 from BOOMi for

EDI then it should show "The total quantity exceeds the
allowable quantity of 50 eaches. Do you want to approve
and submit the form?" error message

pattern from MuleSoft for Flat file



field.

invalid pattern from MuleSoft for Flat file


from MuleSoft for Flat file for go puff

from MuleSoft for Flat file.

field.

date " error message.
on delivery date field if we receive delivery date less
than start date(Customer Hierarchy) from MuleSoft for
Flat file.
date " error message.
on delivery date field if we receive delivery date greater
than end date(Customer Hierarchy) from MuleSoft for
Flat file .

field if we receive any date (old 90 days from current
date.)

we receive any future date as delivery date from

field if we receive valid delivery date from MuleSoft for
Flat file
current date from MuleSoft for Flat file

Flat file

MuleSoft for Flat file then it should show "Delivery ticket
no missing" error message in Delivery ticket field.
If user receive delivery ticket number from MuleSoft for

Flat file then it should not show any error message in

MuleSoft for Flat file for different Customer then it
should not show any error message in Customer PO field

MuleSoft for Flat file for existed Customer then it should
not show any error message in Customer PO field

MuleSoft for Flat file in delivery ticket field then it should

MuleSoft for Flat file in delivery ticket field then it
shouldn't show any error message in delivery ticket
number field.
MuleSoft for Flat file in product code field then it show
an "Duplicate Line Item" error message on product code
field
If user receives different diff line item from MuleSoft for

Flat file in product code field then it should not show any
if user receives eaches other than multiples of "eaches

per box" from MuleSoft for Flat file then it should show
"Eaches not in full boxes" on eaches box.
if user receives eaches multiples of "eaches per box"

form MuleSoft for Flat then user shouldn't get show any
error message.
number field from MuleSoft for Flat file then it should
show "Invalid Customer" error message on DUNS
number field

number field

not show any error message on DUNS number field
If user receives Invalid Product code in Product code

field from MuleSoft for Flat file then the it should show
"Invalid product " error message on product code field.
If user revives empty in product code field from

MuleSoft for Flat file then it should show "Invalid
product" error message product code field.
If user receives valid Product code in Product code field
from MuleSoft for Flat file then it should not show any
error message on product code field.

MuleSoft for Flat file then it should show "no delivery
date" error message on delivery date field.
MuleSoft for Flat file then it should not show any error

MuleSoft for Flat file then user should show " Product
line items are missing "error message

MuleSoft for Flat file then user should not show any
error message.
If user receives product code that is not mapped to the
retailer in the product code field, from MuleSoft for Flat
file then it should show “Product not listed” error
message on product code field.
If user receives product code that is mapped to that

retailer in the product code field from MuleSoft for Flat
file then it should not show any error message on
product code field.
If user receives more than 5 boxes' for GopuffCustomers

from MuleSoft for Flat file then it should show "Quantity
exceeds box Threshold " error message in eaches box.
If user receives less than or equals 5 boxes' for

GopuffCustomers from MuleSoft for Flat file then it
should not show any error message in eaches box.
If user receives more than 5 boxes' for Food Service
migration from MuleSoft for Flat file then it should show
"Quantity exceeds box Threshold " error message in
eaches box.
If user receives less than or equals 5 boxes' for Food

Service migration from MuleSoft for Flat file then it
should not show any error message in eaches box.
If user receives eaches in more than or less than 5 box's

from MuleSoft for Flat file then should show any error
message.




field.



from MuleSoft for Flat file for go puff

from MuleSoft for Flat file.

field.

we receive any future date as delivery date from
Flat file

current date from MuleSoft for Flat file

Flat file

MuleSoft for Flat file then it should show "Delivery ticket
no missing" error message in Delivery ticket field.
If user receive delivery ticket number from MuleSoft for
Flat file then it should not show any error message in


MuleSoft for Flat file for different Customer then it
should not show any error message in Customer PO field

MuleSoft for Flat file for existed Customer then it should
not show any error message in Customer PO field

MuleSoft for Flat file in delivery ticket field then it should
MuleSoft for Flat file in delivery ticket field then it
shouldn't show any error message in delivery ticket
number field.

MuleSoft for Flat file in product code field then it show
an "Duplicate Line Item" error message on product code
field
If user receives different diff line item from MuleSoft for

Flat file in product code field then it should not show any

number field

number field
not show any error message on DUNS number field

MuleSoft for Flat file then it should show "no delivery
date" error message on delivery date field.
MuleSoft for Flat file then it should not show any error

MuleSoft for Flat file then user should show " Product
line items are missing "error message

MuleSoft for Flat file then user should not show any
error message.
If user receives eaches more than 50 from MuleSoft for
Flat file then it should show "The total quantity exceeds
the allowable quantity of 50 eaches. Do you want to
approve and submit the form?" error message
If user receives eaches more than 50 from MuleSoft for

Flat file then it should show "The total quantity exceeds
the allowable quantity of 50 eaches. Do you want to
approve and submit the form?" error message
User should be able to launch DT site.
DT user should be able to directly login to DT dashboard

page.
DT administrative should be redirect to Select the DT

account to proceed page
User should be redirected to particular DT Dashboard

page.
User should able to redirect to "DN - Delivery ticket"

page.
If user give any invalid pattern in Customer PO text field

and try to submit the form then user should get
"Customer PO does not meet pattern." error message.
(ex. starts with Gus and has 6 char(GoPuff), PO start
digits/letters, length.)
If user give any invalid pattern for GopuffCustomers in
Customer PO field and try to submit the form then user
should get "Customer PO does not meet pattern." error
message.
If user give any invalid pattern for GopuffCustomers in

Customer PO field and try to submit the form then user
should get "Customer PO does not meet pattern." error
message.
If user try to submit the form without giving any

Customer PO in Customer PO field for GopuffCustomers
then user should get an error message "Customer PO
does not meet pattern"
If user give any invalid pattern for AEFIS(Banner group)

Customers in Customer PO field and try to submit the
form then user should get "Customer PO does not meet
pattern." error message.
If user give any invalid pattern for AEFIS(Banner group)
Customers in Customer PO field and try to submit the
form then user should get "Customer PO does not meet
pattern." error message.
(AEFIS - Starts with 'VON' - 9 digit},
If user try to submit the form without giving any

Customer PO in Customer PO field for AEFIS(Banner
group) Customers then user should get an error message
"Customer PO does not meet pattern"
If user try to submit the form with/without any data

then it should not show any error message for Customer
PO field.
If user give length that is Greater than or Less than 9 in

Customer PO text field and try to submit the form then
user should get "Customer PO larger than maximum
length" error message.
ex.AEFIS - 9 digit
Go Puff - 6 Digits
If user try to submit the form with giving less than
6CharCustomer PO in Customer PO field for
GopuffCustomers then user should get an error message
If user try to submit the form with giving greater than

If user try to submit the form with giving less than

AEFIS(Banner group) Customers then user should get an
error message "Customer PO does not meet pattern"
If user try to submit the form with giving greater than

AEFIS(Banner group) Customers then user should get an
error message "Customer PO does not meet pattern"
If user try to submit the form with/without any data
PO field.
If user select delivery dates less than start or greater

than end date(Customer Hierarchy) and try to submit
the form then then user should get " Date outside
retailer's operation date " error message.
If user select delivery dates less than start (Customer

Hierarchy) and try to submit the form then then user
should get " Date outside retailer's operation date "
error message.
If user Select any greater than end date of Customer

Hierarchy (Customer Hierarchy) and try to submit the
form then then user should get " Date outside retailer's
operation date " error message.
If user select delivery dates in between start or end
date(Customer Hierarchy) and try to submit the form
then it show any error message
Standard check - Future delivery dates should be

disabled in Calendar
If user selects delivery date greater than or equal to 90

days from current date and try to submit the form then
user should get "Delivery date less than allowable days
of current date " error message.
If user doesn't enter any delivery ticket number and try

to submit the form then user should get " delivery ticket
number is missing" error message.
If user give any existing Customer PO number for same

Customer and try to submit the form the user should get
"Duplicate PO number " error message.
If user give any existing Customer PO number for
different Customer and try to submit the form then user
should not get any error message, it should accept the
form if no errors are there.
If user give any existing delivery ticket number in

delivery ticket text field and try to submit the form the
user should get "Duplicate delivery ticket number " error
message.
If user give any unique delivery ticket number in delivery

ticket field and try to submit the form the user shouldn't
get error message and from should be submitted if no
error are there.
If user give same product code as 2nd line item in

product code field and try to submit the form the user
should get "Please remove duplicate product code or
line items " error message.
if user enter eaches other than multiples of "eaches per

box" then user should get "Eaches not in full boxes"
[{"multiples":"eaches"}] - it should accept only multiple
of eaches per box
if user enter eaches multiples of "eaches per box" then
user shouldn't get any error message and form should
be submitted if no errors. [{"multiples":"eaches"}] - it
should accept only multiple of eaches per box
if user submit the form with eaches multiples of "eaches

per then it should not any error message.
If user enter Invalid Customer DUNS number in DUNS

number files and try to submit the form then the user
should get "Invalid Customer " error message.
If user submit the form without Customer then it should

number field
If user enter valid Customer DUNS number in DUNS

should get an auto pop of that particular Customer
If user enter Invalid Product code in Product code field
and try to submit the form the user should get "Invalid
product " error message.
If user enter valid Product code in Product code field and

try to submit the form then the user should get auto
populated of that particular product.
If user try to submit the form without selecting any

delivery date in delivery date box then user should get
"Delivery date is an mandatory field." error message
If user try to submit the form with selecting any delivery

date in delivery date box then user shouldn't get any
error message and form should be submitted if no errors
are there.
If user is trying to submit the form without selecting any

product code, then user should get “Product line item is
Missing” error message.
If user is trying to submit the form with selecting any
product code, then user shouldn't get any error message
and form should be submitted if not errors are there in
the form while submitting.
If user enter product code that is not mapped to the

retailer in the product code field, and try to submit the
Form then user should get “Product not listed” error
message.
If user enter eaches more than 5 box then user should

get error message.
If user enter eaches as 5 box then user shouldn't get

error message.
If user enter eaches more than 5 box then user should
get error message.

error message.

error message.
If user enter DUNS number and select any store, if the Working as expected
store Is not mapped to any Sub- Distributor, user should
get default as “NONE”(not an error).
If user enter DUNS number and select any store, if the Working as expected
store Is mapped to any Sub- Distributor, user should get
that mapped sub DT (not an error).
If user give any invalid pattern for AEFIS(Banner Working as expected
group) Customers in Customer PO field and try to submit
the form then user should get "Customer PO does not
meet pattern." error message.
If user give any invalid pattern for AEFIS(Banner Working as expected

group) Customers in Customer PO field and try to submit
the form then user should get "Customer PO does not
meet pattern." error message.
If user try to submit the form without giving any Working as expected
Customer PO in Customer PO field for AEFIS(Banner
group) Customers then user should get an error message
(AEFIS - Starts with 'VON' - 9 digit}
If user try to submit the form with/without any data Working as expected
PO field.
If user give length that is Greater than or Less than 9 in Working as expected
Customer PO text field and try to submit the form then
user should get "Customer PO larger than maximum
length" error message.
ex.AEFIS - 9 digit
Go Puff - 6 Digits
If user try to submit the form with giving less than Working as expected
If user try to submit the form with giving greater than Working as expected
If user doesn't enter any delivery ticket number and try Working as expected
to submit the form then user should get " delivery ticket
number is missing" error message.
If user give any existing Customer PO number for same Working as expected
Customer and try to submit the form the user should get
"Duplicate PO number " error message.
If user give any existing Customer PO number for Working as expected

different Customer and try to submit the form then user
should not get any error message, it should accept the
form if no errors are there.
If user give any existing delivery ticket number in Working as expected

delivery ticket text field and try to submit the form the
user should get "Duplicate delivery ticket number " error
message.
"If user give any unique delivery ticket number in Working as expected
delivery ticket field and try to submit the form the user
shouldn't get error message and from should be
submitted if no error are there.
If user give same product code as 2nd line item in Working as expected
product code field and try to submit the form the user
should get "Please remove duplicate product code or
line items " error message.
If user enter Invalid Customer DUNS number in DUNS Working as expected
number files and try to submit the form the user should
get "Invalid Customer " error message.
If user enter valid Customer DUNS number in DUNS Working as expected

should get an auto pop of that particular Customer
If user try to submit the form without selecting any Working as expected
delivery date in delivery date box then user should get
"Delivery date is an mandatory field." error message
If user try to submit the form with selecting any delivery Working as expected
date in delivery date box then user shouldn't get any
error message and form should be submitted if no errors
are there.
If user is trying to submit the form without selecting any Working as expected
If user is trying to submit the form without selecting any Working as expected
If user enter eaches more than 50, then user should get Working as expected
“Total quantity exceeds total eaches threshold - Requires
Verification” pop up message.
If user enter eaches less than 50, then user should not Working as expected
get
any verification pop up message.
If any validation fails delivery notes then that will be Working as expected
created with an error flag. Such delivery notes should
not be pushed to SAP. (Line level/ Header level errors)
Executed Executed
Status Date By Remarks
failed 10/27/2022 Sreekanth
Pass 10/27/2022 Sreekanth
Fail 10/27/2022 Sreekanth





Book 4

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Book 4

Uploaded by

Copyright:

Available Formats

Test Scenario Description

Applicatio Test cases

Verify whether user able to launch

Verify whether DT user is able to

Customer Banner - Go Puff Verify Rule No 2 -Customer PO larger than maximum

Customer Banner - Go Puff Verify Rule No 2 -Customer PO larger than maximum

Verify Rule No 1 -Customer PO does not meet pattern (DN

Verify Rule No 1 -Customer PO does not meet pattern (DN )

Verify Rule No 1 - For Customer groups that don't have any

Verify Rule No 4 - Date outside retailer's operation date

Verify Rule No 7 - Delivery ticket no missing (DN Debit)

Verify Rule No 8 - by receiving Duplicate Customer PO (DN

Verify Rule No 8 - by receiving Duplicate Customer PO (DN

Verify Rule No 8 - Duplicate Customer PO (DN Debit) for

Customer DUNS - 2447263101707 Verify Rule No 12 - Invalid Customer(DN Debit) from

Customer DUNS - 2447263101707 Verify Rule No 12 - Invalid Customer(DN Debit) from

Customer DUNS - 8473400010001 Verify Rule No 17 -Quantity exceeds box Threshold -

Customer DUNS - 8473400010001 Verify Rule No 17 -Quantity exceeds box Threshold -

Customer DUNS - 2133964801700 Verify Rule No 17 -Quantity exceeds box Threshold -

Customer DUNS - 2133964802300 Verify Rule No 17 -Quantity exceeds box Threshold -

Customer Banner - Go Puff Verify Rule No 2 -Customer PO larger than maximum

Customer Banner - Go Puff Verify Rule No 2 -Customer PO larger than maximum

Customer Banner - AFEES Verify Rule No 2 -Customer PO larger than maximum

Customer DUNS - 8473400010001 Verify Rule No 7 - Delivery ticket no missing (DN

Customer DUNS - 8473400010001 Verify Rule No 7 - Delivery ticket no missing (DN

Verify Rule No 8 - by receiving Duplicate Customer PO (DN

Customer DUNS - 8473400010001 Verify Rule No 8 - by receiving Duplicate Customer PO (DN

Customer DUNS - 6955681032216 Verify Rule No 9 - by receiving Unique delivery ticket no

Customer DUNS - 6955681032216 Verify Rule No 10 - Duplicate Line Item(DN Credit)from

Customer DUNS - 2447263101707 Verify Rule No 12 - Invalid Customer(DN Credit)from

Customer DUNS - 2447263101707 Verify Rule No 12 - Invalid Customer(DN Credit)from

Customer Banner - Go Puff Verify Rule No 2 -Customer PO larger than maximum

Customer Banner - AFEES Verify Rule No 2 -Customer PO larger than maximum

Verify Rule No 1 -Customer PO does not meet pattern (DN )

Verify Rule No 1 - For Customer groups that don't have any

Verify Rule No 4 - Date outside retailer's operation date

Verify Rule No 7 - Delivery ticket no missing (DN Debit)

Verify Rule No 7 - Delivery ticket no missing (DN Debit)

Verify Rule No 8 - by receiving Duplicate Customer PO (DN

Verify Rule No 8 - Duplicate Customer PO (DN Debit) for

Customer DUNS - 2447263112614 Verify Rule No 9 - by receiving Unique delivery ticket no

Customer DUNS - 2447263101707 Verify Rule No 12 - Invalid Customer(DN Debit) from

Customer DUNS - 2447263101707 Verify Rule No 12 - Invalid Customer(DN Debit) from

Customer DUNS - 8473400010001 Verify Rule No 17 -Quantity exceeds box Threshold -

Customer DUNS - 8473400010001 Verify Rule No 17 -Quantity exceeds box Threshold -

Customer DUNS - 2133964801700 Verify Rule No 17 -Quantity exceeds box Threshold -

Customer DUNS - 2133964802300 Verify Rule No 17 -Quantity exceeds box Threshold -

Customer Banner - Go Puff Verify Rule No 2 -Customer PO larger than maximum

Customer Banner - AFEES Verify Rule No 2 -Customer PO larger than maximum

Verify Rule No 7 - Delivery ticket no missing (DN

Verify Rule No 8 - by receiving Duplicate Customer PO (DN

Verify Rule No 8 - by receiving Duplicate Customer PO (DN

Verify Rule No 8 - Duplicate Customer PO (DN Credit)for

Customer DUNS - 6955681032216 Verify Rule No 10 - Duplicate Line Item(DN Credit)from

Customer DUNS - 2447263101788 Verify Rule No 12 - Invalid Customer(DN Credit)from

Customer DUNS - 2447263101707 Verify Rule No 12 - Invalid Customer(DN Credit)from

Verify whether user able to launch DT site.

Verify if DT administrative is able to login to the site

Verify by clicking on Create DN Debit under My task or

Customer Banner - AFEES Verify Customer PO larger than maximum length

Verify Date outside retailer's operation date (DN Debit)

Verify Rule No 4 - Date outside retailer's operation date