Someone asked me about framework design :
My Answer might help anyone here- Mostly frameworks share same structure, they normally have:
BaseClass - Declare setup and teardown method here. And also initialize appium instance here.
ParametersFile - Declare all your global framework variables here like Url, username, pwd etc.
Locator class - keep your locators here or you can also create multiple locator classes like one class for one screen of your app.
Page classes - All the appium/Selenium code functions will be written here like for login, click on something etc. Again one class for one screen and related functions in that class.
Utils - if you are reading test data from excel or some file, keep that code here. Call this code wherever required.
Tests - All your test classes will be here. One Test Class for one functionality. Like for Dashboard screen DashboardTest class. And call the page functions here in your test functions by creating object of page classes. Like.,
DashPage objDash = new DashPage();
objDash.enterSomeValue();
And also extend/inherit BaseClass in your test classes. So, that setup and teardown are called by default.
Use TestNG as unittest framework. Refer Techlistic.com’s Testng tutorial
This is a high level interpretation of an automation framework.
Hope it helps! 👍🏻
My Answer might help anyone here- Mostly frameworks share same structure, they normally have:
BaseClass - Declare setup and teardown method here. And also initialize appium instance here.
ParametersFile - Declare all your global framework variables here like Url, username, pwd etc.
Locator class - keep your locators here or you can also create multiple locator classes like one class for one screen of your app.
Page classes - All the appium/Selenium code functions will be written here like for login, click on something etc. Again one class for one screen and related functions in that class.
Utils - if you are reading test data from excel or some file, keep that code here. Call this code wherever required.
Tests - All your test classes will be here. One Test Class for one functionality. Like for Dashboard screen DashboardTest class. And call the page functions here in your test functions by creating object of page classes. Like.,
DashPage objDash = new DashPage();
objDash.enterSomeValue();
And also extend/inherit BaseClass in your test classes. So, that setup and teardown are called by default.
Use TestNG as unittest framework. Refer Techlistic.com’s Testng tutorial
This is a high level interpretation of an automation framework.
Hope it helps! 👍🏻
Use case of Explicit wait in Selenium:
https://www.techlistic.com/2019/05/automate-google-search-using-selenium.html?m=1
https://www.techlistic.com/2019/05/automate-google-search-using-selenium.html?m=1
Techlistic
Automate Google.com using Selenium Webdriver
In this post you will learn to automate Google Search using Selenium Webdriver with Java. This is a real time example of Explicit wait comm...
If you want to interact with other Selenium Professionals, want to ask your doubts, want to give suggestion for techlistic.com or simply want to connect with me, then join following group-
t.me/SeleniumDiscussions
t.me/SeleniumDiscussions
For beginners, upvote if you like it - https://www.quora.com/Is-it-easy-to-learn-Selenium-if-I-dont-have-knowledge-of-Java/answer/Vaneesh-Behl?ch=10&share=26cf4a56&srid=uRkU3
Find complete series of tutorials on Selenium, Java, TestNG, latest automation trends, Interview preparation, demo websites for practice and many more at -
https://www.techlistic.com
https://www.techlistic.com
Tech Talkers pinned «Find complete series of tutorials on Selenium, Java, TestNG, latest automation trends, Interview preparation, demo websites for practice and many more at - https://www.techlistic.com»