Please enable JavaScript.
Coggle requires JavaScript to display documents.
Refactor Robot Test Scripts (Keywords (Define keyword naming rule (Keyword…
Refactor Robot Test Scripts
Test Data (SQL)
Group SQL Commands to create test data for all environments
Check then remove test data for test case -> Move to test suite If can
Keywords
Group common keywords
Optimize double wait cases (Ex: Wait untils keyword success.... Wait until element is visible....)
Define keyword naming rule
General rules
Begin with verv
Compact and meaning
Common keyword (Ex: Click on Button, Scroll To Element, Click on Mennu....)
Parameterized
Put in common_keywords
Keyword specific
Avoid parameter
Put in specific file
Keyword name should be have function name (Ex: Create test data for Settlement Merchant Page,...)
File/Folder Structure
Group env-dependency test steps into keyword to retry (Ex: Azure, action with slow/unstable response...) => Please do it carefully!
Group/Separate test suite
Test Behaviour/Scripts
Go to feature (screen) only one time for group of test cases
Clear form
Create test data for group of test cases
Remove the actions that have been tested in another test case
Focus to the test case that used to insert data into the database. Sometime the performance is not got -> The test case failed
Elements
Xpath should have the ID of the element
Element naming
(
rpt
) Reporting menu item
(his)
Transaction History menu item
(sett)
Settlement menu item
(merc)
Merchant menu item
(bo)
BO Replacement menu item
(recn)
Reconfiliation menu item (SAKAAR team)
(fld)
File download menu item
(po)
Payout menu item
(fi)
Fund-in menu item
(adm)
Admin menu item
(
po
) Payout menu item
(
prj)
SAP File Configuration menu item
(sap) Payout Operation menu item
(
pop)
Project Management menu item
(fi)
Fund-in menu item
(msg)
Manage Fund-in Messages menu item
(sys)
Portal Admin menu item
(perm)
Permission Management menu item
(auth)
Authorized Groups menu item