What is standard scaffolding for UI Test Automation (Page Object Model Pattern). I am using selenium with Page Object Model.
Biggest trouble I am facing is what and how should I name folder and files for methods which are common across the multiple test files and test cases. I do not like the name 'Util' or 'Helpers'.
Any suggestions for
Repositories
? DB Connection
? Some External Connection
? API Calls
?
Pageobject
? Page1
? Page2
Page Drivers or Page Actions (Helper/Utils)
This folder contains files which contains some helper methods involving either actions of pages and/or some assertions as well which can be shared among test classes.
? Helper class 1
? Helper class 2
?
Test (spec)
? Test Class 1
? Test Class 2
Any suggestions for naming conventions for No.3 above. Looking for some better way to name and organize code which is more meaningful then just Util or Helpers :).
question from:
https://stackoverflow.com/questions/65661721/ui-test-automation-scaffolding-and-naming-for-some-shared-code-between-test-clas 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…