Cybertrax 2.1 Client (UAT)
From UG
(Difference between revisions)
(→Create User with Planner Role) |
(→Core Planner Functionality) |
||
Line 110: | Line 110: | ||
=== Create User with Planner Role === | === Create User with Planner Role === | ||
- | * case: | + | * case: No User Roles |
+ | ** Cannot allow Admin to save it, user must have at least 1 role | ||
+ | |||
+ | * case: Create Planner User | ||
** Bug | ** Bug | ||
*** IE - planner does not necessarily have to be a client at the same time | *** IE - planner does not necessarily have to be a client at the same time | ||
- | * case: Create Planner User Role | + | * case: Create Planner User Role plus shipper role |
** Bug | ** Bug | ||
*** IE - User can have multiple roles and does not have to be a client | *** IE - User can have multiple roles and does not have to be a client | ||
- | * case: Create Planner User | + | * case: Create Planner User with client role |
+ | ** OK | ||
+ | |||
+ | * case: Create Planner User with client role, plus shipper role | ||
+ | ** OK | ||
+ | |||
+ | * case: Create Planner User with client role, plus shipper role, plus planner role | ||
** OK | ** OK | ||
Revision as of 20:25, 12 July 2010
Contents |
Core Shipper Functionality
Create User with Shipper Role
- case: Shipper User created with "E0.ClientCompany:" = X; 1 month later "E0.ClientCompany:" is set to Y. What (should) happen?
- need to ask MO
- case: Shipper User created with "Shipper(T1):" = X; 1 month later "Shipper(T1):" is set to Y. What (should) happen?
- need to update spec
Create CT
- case: Shipper = Pick up Location
- OK
- case: Shipper NOT EQUAL TO Pick up Location
- OK
- case: commodity table PO = empty
- Bug
- case: commodity table PO = NOT empty
- OK
- case: commodity table Sku = empty
- Bug
- case: commodity table Sku = NOT empty
- OK
- case: commodity table Quantity = 0
- Bug, cannot be 0, must be a # greater than 0
- case: commodity table Quantity = NOT empty
- OK
- case: commodity table Item Description = empty
- Bug
- case: commodity table Item Description = NOT empty
- OK
- case: commodity table #plt = 0
- OK according to rule
- case: commodity table pkgs / plts = 0
- If # of pallets NOT = to 0, then # of pkgs CANNOT = 0
- case: commodity table = pkgs / plts NOT empty
- OK
- case: commodity table loose pkgs = 0
- OK according to rule
- case: commodity table TTL GW = 0
- Bug, cannot be 0, must be a # greater than 0
- case: commodity table TTL GW = NOT empty
- OK
- case: commodity table Piece Price = 0.00
- Bug, cannot be 0.00, must be a # greater than 0.00
- case: commodity table Piece Price NOT = empty
- OK
- case: commodity table = Total Value
- See above piece price
- case: commodity table Haz = N
- OK
- case: commodity table Haz =
- OK
- case: commodity table Stack = N
- Bug
- case: commodity table Stack = Y
- OK
View CTs
- case: search line
- Not working
- Clear button does not work
Edit CT
- case: checkbox CT, click edit CT
- OK
- case: edit ANY field = Y
- OK
- case: edit ANY field = N
- OK
View CT
- case: checkbox CT, click view CT
- OK
Clone CT
- case: checkbox CT, click clone CT
- OK
- case: change ANY field = Y
- OK
- case: change ANY field = N
- OK
Core Planner Functionality
Create User with Planner Role
- case: No User Roles
- Cannot allow Admin to save it, user must have at least 1 role
- case: Create Planner User
- Bug
- IE - planner does not necessarily have to be a client at the same time
- Bug
- case: Create Planner User Role plus shipper role
- Bug
- IE - User can have multiple roles and does not have to be a client
- Bug
- case: Create Planner User with client role
- OK
- case: Create Planner User with client role, plus shipper role
- OK
- case: Create Planner User with client role, plus shipper role, plus planner role
- OK
Set Status to CT
- case: Approve = 1 CT
- OK
- case: Approve = multiple CTs at the same time
- Bug
- case: Hold = 1 CT
- OK
- case: Hold = multiple CTs at the same time
- Bug
- case: Hold with a date = 1 CT
- OK
- case: Hold with a date = multiple CTs at the same time
- Bug
- case: Reject = 1 CT
- OK
- case: Reject = multiple CT at the same time
- Bug