Name Testcase Type

Login
UIUX
Click into Username Field Positive

Click into Password Field Positive

Click into Capcha Field Positive

Check Login Button Positive

Login Button Positive

Login Button Positive

Language Icon Positive

Language Icon Positive

Validation

Enter username with less than 6 letters,more than Positive

12 letters, password and captcha is correct.

Enter password less than 6 letters, more than 20 Positive

letters. In Addition there is not a special letters
and capitalization letters.

Enter correct username and password but captcha. Positive

All field wrong input type. Positive

All field was blank. Positive

Input invalid partner ID Positive

Check Clear button Positive

Field Validation - New Partner type drop down
list
Check New Partner Type drop down list when Positive
original type is Agent

Check New Partner Type drop down list when Positive

original type is Sub Agent-Merchant

Check New Partner Type drop down list when Positive

original type is Super Agent

Check New Partner Type drop down list when Positive

original type is Advance Master Merchant

Check New Partner Type drop down list when Positive

original type is Matrix Master Merchant
Check New Partner Type drop down list when Positive
original type is Matrix Master Merchant

Check New Product drop down list Positive

Check Choose user drop down list Positive

Field Validation - Role account

Click Add wallet role but not choose account Positive

Click Add wallet role but not tick role Positive

Check button Add wallet role Positive

Check button Add wallet role Positive

Check button Delete in wallet role table Positive

Click Add CASA role but not choose account Positive

Click Add CASA role but not tick role Positive

Check button Add CASA role Positive

Check button Delete in CASA role table Positive

Check button Save new account role Positive

Check button Delete in table of user Positive

Check button View detail in table of user Positive

Not saved new account role for enough user of Negative

partner

Save new account role with user has already Negative

added in table of user
Delete record in table of user then save again Positive

Happy Case
Change partner type from Agent to Sub Agent- Positive
Merchant

Change partner type from Sub Agent-Merchant to Positive

Agent
Change partner type from Super Agent to Master Positive
Agent-Merchant

Change partner type from Advance master Positive

merchant to Matrix master merchant
Change partner type from Matrix master merchant Positive
to Advance master merchant

View detail of request after adding new Positive

View detail of request after adding new Positive

Check GL-Gl transaction after changing Partner Positive

type

Check role of user when login to parter portals Positive

after changing Parter Type

Exception Case
Add new a request successfully duplicate with one Positive
Rejected

Add new a request successfully duplicate with one Positive

Finish

Add new a request fail duplicate with one Pending Negative

Check detail of partner after adding new one Positive

request but have not approve
Check detail of partner after adding new one Positive
request but have not approve

List
UIUX
Check UI when user does not have List Positive
permisison

Check UIUX of List screen Positive

Check UIUX of List screen when choose Positive

language is Burmese

Check date picker Created date Positive

Check button Clear after input search parameter Positive

Check button Clear after search request Positive

Functional
Check dropdown list Partner type Positive

Check dropdown list Status Positive

Check data shown in grid table Positive

Input incorrect Partner ID Negative

Input space character after a correct Partner ID Negative

Input incorrect partner name Negative

Input incorrect partner name Negative

Input incorrect Business name Negative

Choose incorrect Parter type Negative

Choose incorrect Status Negative

Choose incorrect Created date Negative

Search request by input correct partner ID Positive

Search request by input correct partner name Positive

Search request by input a part of correct partner Positive

name
Search request by input correct Business name Positive

Search request by input a part of correct Business Positive

name

Search request by choose one Parter type Positive

Search request by choose one Status Positive

Search request by choose one Created date Positive

Search request by input all correct parameter Positive

Saerch request by not input any parameter Positive

Check page size Positive

Check button next page, previous page Positive

Check button last page, first page Positive

Approve
UIUX
Check UI when user does not have Approve Positive
permisison

Check default UIUX Positive

Check UI when click on button Reject Positive

Check UI when click on button Cancel Positive

Check Back button Positive

Check UI when approver is not same branch with Positive

created user

Field Validation
Check drop down list Notification type when Positive
partner has only phone number

Check drop down list Notification type when Positive

partner has both phone number and email
Check drop down list Notification type when Positive
partner has both phone number and email

Not choose Notification type Negative

Check drop down list Reason list Positive

Not choose reason list Negative

Not input Description Positive

Not input Description Positive

Input special characters to Description Positive

Happy Case
Approve request successfully Positive

Reject request successfully Positive

Check sms notification Positive

Check email notification Positive

Check notification when choose type = ALL Positive

Exception Case
Approve request when not same branch with user Negative
created
Approve request in case Partner is Deleted Negative

Approve request which status is Finish Negative

Approve request which status is Reject Negative

Reject request which status is Finish Negative

Reject request which status is Reject Negative

Detail
Check UI when user does not have View detail Positive
permisison

Check default UIUX Positive

Check UIUX of List screen when choose Positive

language is Burmese
Check button Back Positive

View detail of request successfully Positive

View detail of request is Rejected Positive

 Test Script (Step-by-Step)
Application Precondition - Step

Shwe Bank 1. User click in Username input

field
1.User access to login page

2. Check UI
Shwe Bank 1. User click in Username input
field
1.User access to login page

Shwe Bank 1.User access to login page 1. User click in Capcha input
field

Shwe Bank 1. User already enterd all field by

correct way. 1.User entered all field
2. Click on Login button after
fill all field.

Back Office 1. User already enterd all field by

correct way but authentication
fail 1.User entered all field

1. Click on Login button after

fill all field but authentication
fail.
Shwe Bank 1.User miss to input a/an filed 1. User input 1 or 2 filed but not
last one.
2. Click button Login

Shwe Bank 1. User Access to login page

1.User click to language icon.
Shwe Bank

2.User select a language

Shwe Bank 1.User access to login page

1. User access login page

2. User click into Username

field and enter less than 6 letters
3. Click on Login button
Shwe Bank 1.User access to login page 1. Enter Username, Password,
Captcha.
2. Entered correct username, 2. Click Login Button

Shwe Bank 1.User entered correct username, 1.User enter correct username
pwd but captcha and password field but not
captcha..
2. Click Login Button

Shwe Bank 1. User enterd incorrect all field

1. User enter username,password
and captcha.
2. Click Login Button

Shwe Bank 1. User Access to login page 1. User do not enter any at 3
field
2. Click Login Button

Back Office 1. User has permission to Add

new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Input invalid partner ID into

Partner information field
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Input valid partner name into

Partner information field
 4. Choose one partner in
dropdown list
5. Click Clear button

Back Office 1. User has permission to Add

new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new
3. Choose Partner information =
Agent
4. Check dropdown list new
Partner type
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Choose Partner information =

Sub Agent-Merchant
4. Check dropdown list new
Partner type
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Choose Partner information =

Super Agent
4. Check dropdown list new
Partner type
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Choose Partner information =

Advance Master merchant
4. Check dropdown list new
Partner type
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new
Back Office

3. Choose Partner information =

Matrix Master merchant
4. Check dropdown list new
Partner type
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Choose Partner information

4. Check dropdown list New
Product
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Choose Partner information

4. Check dropdown list Choose
user

Back Office 1. User has permission to Add

new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Input valid other fields, Click

Add wallet role but not choose
account
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Input valid other fields, Click

Add wallet role but not tick role
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new
Back Office

3. Input valid other fields, Click

Add wallet role but not choose
account
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Input valid other fields, Click

Add wallet role
4. Click button Delete in wallet
role table
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Input valid other fields, Click

Add CASA role but not choose
account
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Input valid other fields, Click

Add CASA role but not tick role
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Input valid other fields, Click

Add CASA role but not choose
account
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Input valid other fields, Click

Add CASA role
 4. Click button Delete in wallet
role table
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Input valid other fields, click

Save new account role
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Input valid other fields, click

Save new account role
4. Click button Delete in table of
user
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Input valid other fields, click

Save new account role
4. Click button View detail in
table of user
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Input valid other fields, but

Not saved new account role for
enough user of partner
4. Click Add new button
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Save new account role with

user has already added in table
of user
 4. Click button Save new
account role
Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Click button Add new

3. Input valid other fields, click

Save new account role
4. Click button Delete in table of
user
5. Link account right for that
user again
6. Click Add new button

Back Office 1. User has permission to Add

new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office

2. Click button Add new

3. Choose Parter is Agent, New

partner type = Sub Agent-
Merchant; input valid other
fields then click button Add new
4. Approve request has just
added

5. Check detail of partner in

menu Partner management

6. Do transactions with the

partner has just changed type

7. Check posting of transaction

Back Office 1. User has permission to Add
new request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office

2. Click button Add new

 3. Choose Parter is Sub Agent-
Merchant, New partner type =
Agent; input valid other fields
then click button Add new
4. Approve request has just
added

5. Check detail of partner in

menu Partner management

6. Do transactions with the

partner has just changed type

7. Check posting of transaction

Back Office 1. User has permission to Add 1. Access menu Partner /
new request for Change Partner Change Partner Type
Type
2. Login to Back Office 2. Click button Add new

3. Choose Parter is Super Agent,

New partner type = Master
Agent-Merchant; input valid
other fields then click button
Add new

4. Approve request has just

added
5. Check detail of partner in
menu Partner management

6. Do transactions with the

partner has just changed type

7. Check posting of transaction

Back Office 1. User has permission to Add 1. Access menu Partner /

new request for Change Partner Change Partner Type
Type
2. Login to Back Office 2. Click button Add new
 3. Choose Parter is Advance
master merchant, New partner
type = Matrix master Merchant;
input valid other fields then click
button Add new

4. Approve request has just

added
5. Check detail of partner in
menu Partner management

6. Do transactions with the

partner has just changed type

7. Check posting of transaction

Back Office 1. User has permission to Add 1. Access menu Partner /

new request for Change Partner Change Partner Type
Type
2. Login to Back Office 2. Click button Add new

3. Choose Parter is Matrix

master merchant, New partner
type = Advance master
Merchant; input valid other
fields then click button Add new

4. Approve request has just

added
5. Check detail of partner in
menu Partner management

6. Do transactions with the

partner has just changed type

7. Check posting of transaction

Back Office Have added one request for 1. Access menu Partner /
change parter type Change Partner Type

2. Search request has just added

Back Office Have added one request for
change parter type

3. Click on hyperlink at Parnter

ID column
Back Office 1. Have added one request for
change parter type
1. Access report portal
2. Account of partner still have
balance 2. Check General Ledger
statement detail report
Back Office Have added one request for
change parter type

1. Access partner portal

2. Check role of user

Back Office 1. User has permission to Add 1. Access menu Partner /

new request for Change Partner Change Partner Type
Type
2. Login to Back Office 2. Click button Add new
3. Input information duplicate
with one request Rejected, then
click button Add new

Back Office 1. User has permission to Add 1. Access menu Partner /

new request for Change Partner Change Partner Type
Type
2. Login to Back Office 2. Click button Add new
3. Input information duplicate
with one request Finish, then
click button Add new

Back Office 1. User has permission to Add 1. Access menu Partner /

new request for Change Partner Change Partner Type
Type
2. Login to Back Office 2. Click button Add new
3. Input information duplicate
with one request Pending, then
click button Add new

Back Office Have added one request for 1. Access menu Partner / Partner
change parter type management
Back Office Have added one request for
change parter type
2. Search the partner have just
add request for change partner
type

3. Click on hyperlink Partner ID

to view detail

Back Office 1. User has permission to List

request for Change Partner Type

2. Login to Back Office 1. Access menu Partner

Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office 2. Check UIUX

Back Office 1. User has permission to List

request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office 2. Check UIUX
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office 2. Click on date picker Created
date
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office
2. Input search parameter
3. Click Clear button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office
2. Input search parameter, click
Search button
 3. Click Clear button

Back Office 1. User has permission to List

request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office
2. Click on Partner type field
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office 2. Click on status field
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office 2. Click Search button
3. Check data shown in grid
table

Back Office 1. User has permission to List

request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office
2. Input incorrect Partner ID,
click Search button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office 2. Input space character after a
correct Partner ID, click Search
button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
Back Office

2. Login to Back Office

2. Input incorrect partner name,
click Search button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office
2. Input incorrect Business
name, click Search button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office
2. Choose incorrect Parter type,
click Search button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office
2. Choose incorrect Status, click
Search button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office
2. Choose incorrect Created
date, click Search button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office 2. input correct partner ID, click
Search button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office
2. input correct partner name,
click Search button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office
2. input a part of correct partner
name, click Search button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office
2. input correct Business name,
click Search button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office 2. input a part of correct
Business name, click Search
button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office 2. input correct partner ID, click
Search button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office 2. input correct partner ID, click
Search button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office 2. input correct partner ID, click
Search button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office
2. input all correct parameter,
click Search button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office 2. click Search button
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office 2. click Search button
3. Choose page size
Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office
2. click Search button

3. Click button next page >

4. Click button previous page <

Back Office 1. User has permission to List
request for Change Partner Type 1. Access menu Partner /
Change Partner Type
2. Login to Back Office
2. click Search button

3. Click button last page >|

4. Click button first page |<

Back Office 1. User does not have permission

to Approve request for Change
Partner Type
1. Access menu Partner /
Change Partner Type
2. Login to Back Office 2. Search request status is
Pending
3. Hover at the last column of
record
Back Office 1. User has permission to
Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending

3. Hover at the last column of

record, click Approve button

Back Office 1. User has permission to

Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending
 3. Hover at the last column of
record, click Approve button
4. Click Reject button
Back Office 1. User has permission to
Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending

3. Hover at the last column of

record, click Approve button
4. Click Reject button
5. Clieck Cancel button
Back Office 1. User has permission to
Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending

3. Hover at the last column of

record, click Approve button
4. Click button Back
Back Office 1. User has permission to
Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending
3. Hover at the last column of
record

Back Office 1. User has permission to

Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending

3. Hover at the last column of

record, click button Approve
4.Check dropdown list
Notification type
Back Office 1. User has permission to
Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
Back Office

2. Login to Back Office 2. Search request status is

Pending

3. Hover at the last column of

record, click button Approve
4.Check dropdown list
Notification type
Back Office 1. User has permission to
Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending

3. Hover at the last column of

record, click button Approve

4. Not choose Notification type

Back Office 1. User has permission to
Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending

3. Hover at the last column of

record, click button Approve
4. Click button Reject
5. Check dropdown list Reason
list
Back Office 1. User has permission to
Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending

3. Hover at the last column of

record, click button Approve
4. Click button Reject

5. Not choose reason list

6. Choose reason list then clear

Back Office 1. User has permission to
Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
Back Office

2. Login to Back Office 2. Search request status is

Pending

3. Hover at the last column of

record, click button Approve
4. Click button Reject
5. Not input description, click
button Reject
Back Office 1. User has permission to
Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending

3. Hover at the last column of

record, click button Approve
4. Click button Reject

5. Input special characters to

Description, click button Reject

Back Office 1. User has permission to

Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending

3. Hover at the last column of

record, click button Approve

4. Choose notification type, then

click Approve button
5. Check informarion shown in
list screen
Back Office 1. User has permission to
Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending

3. Hover at the last column of

record, click button Approve
 4. Click button Reject, choose
reason then click button Reject
5. Check informarion shown in
list screen
Back Office 1. Approve request for change
Partner type successfully
1. Access sms portal
2. Choose notification type = 2. Search phone number of
SMS partner
3. Check notification sent to
partner
Back Office 1. Approve request for change
Partner type successfully

1. Access email inbox

2. Choose notification type = 2. Check notification sent to
Email partner
Back Office 1. Approve request for change
Partner type successfully 1. Check notification sent to
phone number of parter
2. Choose notification type = 2. Check notification sent to
ALL email of partner

Back Office 1. User has permission to

Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending

3. Hover at the last column of

record, click button Approve

4. Access BO with other user in

other browser, change branch of
approver

5. At screen of step 3: press F5

then click Approve button
Back Office 1. Already added request for 1. Access menu Partner /
change parter type Change Partner Type
2. Delete the partner has been
added request for change type
2. Search that request

3. Hover at the last column of

record, click button Approve

4. Choose notification type, then

click Approve button
Back Office 1. User has permission to
Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending

3. Hover at the last column of

record, click button Approve
(open screen in 2 tabs)

4. Click Approve button at tab 1

5. Click Approve button at tab 2

Back Office 1. User has permission to
Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending

3. Hover at the last column of

record, click button Approve
(open screen in 2 tabs)

4. Click Reject button at tab 1

5. Click Approve button at tab 2

Back Office 1. User has permission to
Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending
 3. Hover at the last column of
record, click button Approve
(open screen in 2 tabs)

4. Click Approve button at tab 1

5. Click reject button at tab 2

Back Office 1. User has permission to
Approve request for Change 1. Access menu Partner /
Partner Type Change Partner Type
2. Login to Back Office 2. Search request status is
Pending

3. Hover at the last column of

record, click button Approve
(open screen in 2 tabs)

4. Click Reject button at tab 1

5. Click Reject button at tab 2

Back Office 1. User does not have permission

to View detail request for Change
Partner Type
1. Access menu Partner /
Change Partner Type
2. Login to Back Office 2. Search request
3. Click on hyperlink at column
partner ID
Back Office 1. User has permission to View
detail request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Search request
3. Click on hyperlink at column
partner ID

Back Office 1. User has permission to View

detail request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Search request
3. Click on hyperlink at column
partner ID
Back Office 1. User has permission to View
detail request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Search request
3. Click on hyperlink at column
partner ID
4. Click button Back
Back Office 1. User has permission to View
detail request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Search request
3. Click on hyperlink at column
partner ID
Back Office 1. User has permission to View
detail request for Change Partner 1. Access menu Partner /
Type Change Partner Type
2. Login to Back Office 2. Search request
3. Click on hyperlink at column
partner ID
Test Script (Step-by-Step) -
Expected Result Priority Labels Owner

Focus on Username Field High UIUX JIRAUSER10203

Focus on Password Field High UIUX JIRAUSER10203

Focus on Capcha Field High UIUX JIRAUSER10203

Success and access to next sceen High UIUX JIRAUSER10203

Appear a message about fail High UIUX JIRAUSER10203

authentication.

Show a message about lack of a field High UIUX JIRAUSER10203

Change Normal UIUX JIRAUSER10203

Change Normal UIUX JIRAUSER10203

Show message: Username must be 6- Normal Field JIRAUSER10203

12 letters. Validation

Show message: Password must be 6- Normal Field JIRAUSER10203

12 letters, contain a special letters and Validation
capitalization.

Show message: Wrong captcha! Normal Field JIRAUSER10203

Validation

Show message: Password must be 6- Normal Field JIRAUSER10203

12 letters, contain a special letters and Validation
capitalization.Wrong captcha!
Username must be 6-12 letters.

Show message: Please fill all Normal Field JIRAUSER10203

information. Validation

Show msg: No data to show Normal Field JIRAUSER10203

Validation

Clear all partner information field Normal Field JIRAUSER10203

Validation
Show list includes: Sub Agent- Normal Field JIRAUSER10203
Merchant Validation

Show list includes: Agent Normal Field JIRAUSER10203

Validation

Show list includes: Master Agent- Normal Field JIRAUSER10203

merchant Validation

Show list includes: Matrix Master Normal Field JIRAUSER10203

Merchant Validation

Show list includes: Advance Master Normal Field JIRAUSER10203

Merchant Validation
Show list includes: Advance Master Normal Field JIRAUSER10203
Merchant Validation

Show list product following customer Normal Field JIRAUSER10203

type "Partner" have been configured Validation

Show list all users of partner Normal Field JIRAUSER10203

Validation

Show error toast: Please choose one Low Field JIRAUSER10203

account Validation

Show error toast: Please choose at Low Field JIRAUSER10203

lease one role Validation

Show account role in the table below Normal Field JIRAUSER10203

Validation
Show account role in the table below Normal Field JIRAUSER10203
Validation

Delete account right from the table Normal Field JIRAUSER10203

Validation

Show error toast: Please choose one Low Field JIRAUSER10203

account Validation

Show error toast: Please choose at Low Field JIRAUSER10203

lease one role Validation

Show account role in the table below Normal Field JIRAUSER10203

Validation

Delete account right from the table Normal Field JIRAUSER10203

Validation
Show user with new account right in Normal Field JIRAUSER10203
the table below Validation

Delete user with new account right in Normal Field JIRAUSER10203

the table Validation

Show detail: user with new account Normal Field JIRAUSER10203

right Validation

Show error toast: Please link new Normal Field JIRAUSER10203

account right for enough user of Validation
partner

Show error toast: User has already Normal Field JIRAUSER10203

linked new account right Validation
Add new request successfully Normal Field JIRAUSER10203
Validation

3. Add new request successfully. High Happy JIRAUSER10203

Status of request is Pending Case

4. Approve request successfully.

Status of request is Finish

5. Show correct information with the

new type and new account right

6. Do transaction successfully

7. Transaction is posting to new GL

account

3. Add new request successfully. High Happy JIRAUSER10203

Status of request is Pending Case

4. Approve request successfully.

Status of request is Finish
5. Show correct information with the
new type and new account right

6. Do transaction successfully

7. Transaction is posting to new GL

account

3. Add new request successfully. High Happy JIRAUSER10203

Status of request is Pending Case

4. Approve request successfully.

Status of request is Finish

5. Show correct information with the

new type and new account right

6. Do transaction successfully

7. Transaction is posting to new GL

account

3. Add new request successfully. High Happy JIRAUSER10203

Status of request is Pending Case

4. Approve request successfully.

Status of request is Finish
5. Show correct information with the
new type and new account right

6. Do transaction successfully

7. Transaction is posting to new GL

account

3. Add new request successfully. High Happy JIRAUSER10203

Status of request is Pending Case

4. Approve request successfully.

Status of request is Finish

5. Show correct information with the

new type and new account right

6. Do transaction successfully

7. Transaction is posting to new GL

account

Show correct information High Happy JIRAUSER10203

Case
Show correct information High Happy JIRAUSER10203
Case

Transfer the balance amount from old High Happy JIRAUSER10203

GL to new GL Case

Show menu, feature following the High Happy JIRAUSER10203

new role of user Case

Add new request successfully High Exception JIRAUSER10203

Case

Add new request successfully High Exception JIRAUSER10203

Case

Show error toast: Parnter has already Normal Exception JIRAUSER10203

added request for change partner type Case

Have not changed Partner information Normal Exception JIRAUSER10203

Case
Have not changed Partner information Normal Exception JIRAUSER10203
Case

Do not show sub mernu: Change Low UIUX JIRAUSER10203

partner type

Displays: Low UIUX JIRAUSER10203

- Title
- Breadcrumb
- Button Add new
- Search parameter: Partner ID,
Partner name, Partner type, Created
date, Status
- Data grid table
- Paging
Display content in selected language Low UIUX JIRAUSER10203

Have no error in interface

Show date picker below field Low UIUX JIRAUSER10203

Clear all search parameter Low UIUX JIRAUSER10203

Clear all search parameter and grid Low UIUX JIRAUSER10203

table
Show list of parnter type configured Low Functional JIRAUSER10203
in menu Customer type

Show list: Pending, Finish, Rejected Low Functional JIRAUSER10203

Display: Low Functional JIRAUSER10203

- Parnter ID: hyperlink

- Parnter name

- New partner type

- Date created: date time in format
24h
- User Created
- User Approve
- Status
- Action button: Show button
folowing status
+ Status Pending: show Approve
button
+ Status Finish: none
+ Status Rejected: none
Show error toast: Record not found Normal Functional JIRAUSER10203

Show error toast: Record not found Normal Functional JIRAUSER10203

Show error toast: Record not found Normal Functional JIRAUSER10203

Show error toast: Record not found Normal Functional JIRAUSER10203

Show error toast: Record not found Normal Functional JIRAUSER10203

Show error toast: Record not found Normal Functional JIRAUSER10203

Show error toast: Record not found Normal Functional JIRAUSER10203

Show error toast: Record not found Normal Functional JIRAUSER10203

Show records match with saerch Normal Functional JIRAUSER10203

parameter

Show records match with saerch Normal Functional JIRAUSER10203

parameter

Show records match with saerch Normal Functional JIRAUSER10203

parameter
Show records match with saerch Normal Functional JIRAUSER10203
parameter

Show records match with saerch Normal Functional JIRAUSER10203

parameter

Show records match with saerch Normal Functional JIRAUSER10203

parameter

Show records match with saerch Normal Functional JIRAUSER10203

parameter

Show records match with saerch Normal Functional JIRAUSER10203

parameter

Show records match with saerch High Happy JIRAUSER10203

parameter Case

Show list of all request High Happy JIRAUSER10203

Case

display correct number of records per Low Functional JIRAUSER10203

page
3. Show record of the next page Low Functional JIRAUSER10203

4. Show records of the previous page

3. Show record of the last page Low Functional JIRAUSER10203

4. Show records of the first page

Donot show Approve button Low UIUX JIRAUSER10203

Display Low UIUX JIRAUSER10203

- Title

- Breadcrumb

- detail of request
- Button Approve, Reject, Back

Hide button Approve Low UIUX JIRAUSER10203

Show panel Reject reason

Hide panel Reject reason Low UIUX JIRAUSER10203

Show button Approve

Go to the previous screen Low Functional JIRAUSER10203

Donot show Approve button Low UIUX JIRAUSER10203

Only show: SMS Low Field JIRAUSER10203

Validation

Show: SMS, Email, ALL Low Field JIRAUSER10203

Validation
Show: SMS, Email, ALL Low Field JIRAUSER10203
Validation

Disable button Approve Low Field JIRAUSER10203

Validation

Show list of reason configged in Low Field JIRAUSER10203

menu Reason list Validation

5. Disable Reject button Normal Field JIRAUSER10203

Validation

6. Show error msg below: Reason is

required

Reject request successfully Low Field JIRAUSER10203

Validation
Reject request successfully Low Field JIRAUSER10203
Validation

Allow to input all type of data Low Field JIRAUSER10203

Validation

Reject request successfully

4. Approve request successfully High Happy JIRAUSER10203

Case

5. Status of request is Finish

4. Reject request successfully High Happy JIRAUSER10203

Case

5. Status of request is Rejected

Display notification same as template High Happy JIRAUSER10203
configged in menu Notification Case
template management in BO

Display notification same as template High Happy JIRAUSER10203

configged in menu Notification Case
template management in BO

System sent notificaiton to both sms Normal Happy JIRAUSER10203

and email Case

Show correct template

Show error toast: You can not Normal Exception JIRAUSER10203

approve because different branch with Case
created user
Show error toast: Status of partner is Normal Exception JIRAUSER10203
invalid Case

Show error toast: Status of request is Normal Exception JIRAUSER10203

invalid Case

Show error toast: Status of request is Normal Exception JIRAUSER10203

invalid Case

Show error toast: Status of request is Normal Exception JIRAUSER10203

invalid Case
invalid Case

Show error toast: Status of request is Normal Exception JIRAUSER10203

invalid Case

Show access denied screen Low UIUX JIRAUSER10203

Display Low UIUX JIRAUSER10203

- Title
- Breadcrumb

- Detail of request
- Button Back
Display content in selected language Low UIUX JIRAUSER10203

Have no error in interface

Hide button Approve Low Functional JIRAUSER10203

Show panel Reject reason

Show correct information High Happy JIRAUSER10203

Case

Show correct information with reject High Happy JIRAUSER10203

reason Case
Folder