functionality testing protocol

7/24/2019 Functionality Testing Protocol

1/12

Chapter: 4.[Access restrictions]

Process:

When it comes to rules, PRS customers should be noted in particular, as very strictrestrictions on deliveries and/or collections may apply. For example the driver mustwear appropriate protective clothing, or the truck is not allowed to have any otherload carries on it. hese restrictions/rules must be stored at the contact and passedon to the haulier in the event o! a movement

Test Case: "reated a #ew $ocation Rules and attaching the $ocation Rules with the

existing contact and #ew "ontacts. ried attaching multiple $ocation Rules de%ned ,!or &ne "ontact. 'id a 'uplicate entry !or the Record already exist, to veri!y (alidation "heck

in $ocation Rules "ard Page. ried attaching the $ocation Rules , which is already attached to "ontact and

veri%ed (alidation "heck in "ontact "ard.

Verdict:

Location Rules is working fne.


2/12

Chapter 4. : Vehicles

Truck:

Process: he management o! vehicles is a use!ul extension !or many areas o! the system. )tcan be used !or %nding the right haulier or de%ning access restrictions.

$oad *uantities may vary depending on the load carrier to be transported. hisin!ormation must be Stored accordingly.

he allocation o! a vehicle to the various types o! contacts will thus be evaluateddi+erently. For hauliers, in con unction with the vehicle count, this corresponds tothe -eet. For customers or other types o! delivery addresses, it is the de%nition o!access restrictions.

Test Case:

"reated a #ew ruck, and attaching the same with existing contact and !or#ew contact "reated. ttaching ultiple ruck details !or one "ontact. 'id a duplicate entry !or the ruck record already existing. o veri!y validation

check in ruck "ard Page. ried attaching the ruck details, which is already attached to the "ontact and

veri%ed (alidation "heck !or the same.


3/12

"reating a #ew ruck Record and tested !or Field wise (alidation "heck in ruck "ard Page.

"reated a )tem $ist !or the #ew ruck Record and check !or validation in ruck)tem $ist Page.

Verdict: !ot "orking #ine. Field Wise (alidation "heck is not working, when

creating a #ew ruck Record in ruck "ard Page. !ot "orking fne !or Field Wise (alidation check in ruck )tem $ist Page.


4/12

Chapter 4.$.$%: &o'e(ent Location

&o'e(ent Role:

Process:

$oad carriers are transported !rom one place to another, which is part o! thebusiness o! Pooling Partners. 0very location where load carriers are loaded orunloaded, is also a contact.

he contacts there!ore need to be classi%ed according to their roles. his de%nitionallows the appropriate !unctions within the movements to be assigned acorresponding contact.

Test Case: "reated a #ew ovement Role and attaching the same with #ew "ontact and

0xisting "ontact. ttaching ultiple ovement Role With &ne "ontact. "reated a 'uplicated ovement Role 0ntry which is already existing. ried ttaching the ovement Role ttached with the "ontact, which is

already attached. "reated and deleted ovement Role $ocation entry , and checked the

Same ,whether it re-ects in the ovement Role Fact 1ox in "ontact "ard.


5/12

Verdict:&o'e(ent Role Location is working fne Chapter 4.$.$) [*ption o+ a &o'e(ent Location]

Process:

)! a contact has been declared as a movement location, more detailedcon%gurations can be made here

,-a(ple:

contact is assigned the role 2"ollection Point2. )n the options you can alsospeci!y whether he cooperates with Pooling Partners or not.

Test Case: "reated a #ew ovement Role &ption and attached the same with 0xisting

contact and #ew "ontact . ried attaching ultiple ovement Role &ption to ovement Role $ocation o!

a "ontact. "reated a 'uplicate ovement Role &ption entry !or already existing entry. "reated a #ew ovement Role entry and tried attaching the same with

ovement Role $ocation o! a "ontact.


6/12

"reated and deleted a #ew ovement Role &ption , to check whether it isre-ecting in the ovement Role &ption Fact box in ovement Role $ocationPage.

Verdict:&o'e(ent Role *ption is "orking fne.Chapter 4.$.$4: [Capacit / "arning 0uantities]Process:

For optimal planning and monitoring o! movement locations, it is necessary tode%ne possible capacity and *uantity warnings which trigger de%nedwork-ows in the event o! excesses or short!alls.

he !ollowing *uantities must be de%ned3

4 aximum *uantity

5 inimum *uantity

6 Reporting *uantity

he values must be speci%ed !or each type o! load carrier.

Test Case: "reated a #ew "apacity 7uantities !or warning linking the same with "ontact. ttaching ultiple )tem created with "apacity 7uantities !or "ontact. 'id a 'uplicate entry o! already created item o! "apacity 7uantities, !or

checking validation.


7/12

'id a #ew entered !or an item with capacity *uantities and checked !or %eld(alidation.

Verdict:

Capacit 0uantities is not working fne. Filed Wise (alidation "heck ismissing.Chapter 4.$.%$: [Appro'ed load carriers andacti'ities]Process:0specially in depots, it is possible that only certain load carriers 8such as 0uropallets9 are accepted. his in!ormation must be managed in a system 2White$ist2. )n addition, certain activities such as repair 80P $ certi%ed9 may or maynot be executed.

Test Case: "reated a #ew )tem ctivity !or a item with activity code and attaching the

same with a contact. "reated a #ew ctivity "ode in ctivity $ist Page and attaching the same in

)tem activity Page. 'id a 'uplicate entry in )tem ctivity Page !or already existing record, !or

validation check. 'id a #ew entry !or the )tem ctivity by selecting ctivity code !or existing

and new contact. 'id a 'uplication entry in ctivity Page !or validation check.


8/12

Verdict:1te( Acti'it is working fne.

Chapter 4.2 [Lanes]Process:

$ 3eneral

$anes describe %xed routes between two movement locations or between two:ones.

% Pre+erred hauliers

)PP ;< also uses lanes to assign them to pre!erred hauliers. With thisin!ormation, the system is able to automatically select a haulier !or a matchwith this lane.


9/12

0ach haulier2s prices per lane are entered here. scaled pricing can beentered according to number o! units 8*uantity o! load carriers9. )t is alsoimportant to speci!y a !avoured haulier !or each lane. hus the !avouredhaulier with its respective price can be displayed !or the respective lane,which is created by the oining o! supply and release in the match.

TestCase:o "reated a #ew $ane "ard )n!o with separate Pre!erred ransporter .o "reated a #ew Pre!erred transporter with priority .o esting "alculate $aneso esting $anes $ocation in map. #ewly created Pre!erred ransporter is Shown in Fact box and when

deleted , it gets deleted and re-ects the same in Fact 1ox. 'id a 'uplication entry !or already existing record !or validation check. "reated a #ew $ane record , !or %eld validation check.Verdict:

!ot working #ine . Field wise validation check is missing.


10/12

Chapter 4.2 [Alternate Address]Process 3

he address data in these %les do not always !ully coincide with the storedaddress o! a contact. )t is necessary to assign these addresses correctly inorder to link the movement data to the correct contact account numbers.

Verdict:This #unctionalit is alread a'aila le in 5tandard !a'ision %6$7.


11/12

Chapter 4.$.) 3eo 8ata

Process : he geographical relationship o! addresses plays a ma or role, e.g. !orsupplying customers with load carriers, there!ore it is necessary to store thegeographic data o! an address.

he geo=data !or a newly entered address is determined asynchronouslyusing a background Service. his is based on 1ing aps, the online mapservices by icroso!t.

$ongitude and latitude o! the input address is *ueried and stored. timestamp, also stored, indicates when the *uery was executed.

3eo 8ata Card

Test Case: he >eo 'ata is calculated based on the ddress and Show in ap

based on Proper Setup done, in >eo dd=ins Setup. wo andatoryFields ?$ocate Web Service ;R$@ and ?$ocate ap ;rl@ needs to be%lled in.


12/12

he "ontact with Full ddress , 0specially andatory Fields like ddress, "ity,"ountry needs to be %lled in , in order to execute the !unction ?"alculate >eo'ata@ 8 fg9% 9and then ?Show on ap ? fg9); in >eo 'ata "ard.

)! any o! the mandatory %elds is missing, the validations are throwing errorand it is working %ne.

his ?"alculate >eo 'ata@ !unction works with or without $ongitude and$atitude value.

Verdict:

3eo 8ata is not working #ine. (alidation "heck !or ?$ocate ap ;R$@ %eld ismissing.

functionality testing protocol

Documents