QA's approach 2 Selenium Web Driver - Web Driver API Architecture
Selenium Web Driver API Architecture:
Webdriver doesn't help us running the Test cases nor doesn't it help us in reports generation/batch running/ordering the test case execution/excel file reading but it just helps us to interact with the browser using the webdriver commandsWhat is “GeckoDriver”:
It is a WebDriver which is used to interact with WebApps. So, this means that all the drivers should have all the implementations which are contracted in the WebDriver interfaces and all the Drivers can be called as WebDriver.
Web Page composed of Web Elements and these Drivers’s will communicate with the Web Page. For communicating with Web Page means communication with Elements present on the Web Page like for example: “Textboxes”, Buttons”, “Links” etc. “WebElement” a sub interface of “SearchContext” comes into picture.
Webdriver doesn't help us running the Test cases nor doesn't it help us in reports generation/batch running/ordering the test case execution/excel file reading but it just helps us to interact with the browser using the webdriver commands
So for this we need a certain controller which facilitates the report generation, etc ->Junit/TestNG/Cucumber BDD/Jbehave
Maven -> Helps in maintaining the entire team to work with latest/common versions of all packages
->Allows us to run the framework from command prompt
Ant ->Will only allow us to execute the framework from command prompt
Now the code is mainatined at a common location ->Git
Jenkins
Now the framework is over -> in the maintainence phase, we need to schedule it using Jenkins. Also intimate all the users about a success/failure of the build emailed automatically.
Web Page composed of Web Elements and these Drivers’s will communicate with the Web Page. For communicating with Web Page means communication with Elements present on the Web Page like for example: “Textboxes”, Buttons”, “Links” etc. “WebElement” a sub interface of “SearchContext” comes into picture.
Webdriver doesn't help us running the Test cases nor doesn't it help us in reports generation/batch running/ordering the test case execution/excel file reading but it just helps us to interact with the browser using the webdriver commands
So for this we need a certain controller which facilitates the report generation, etc ->Junit/TestNG/Cucumber BDD/Jbehave
Maven -> Helps in maintaining the entire team to work with latest/common versions of all packages
->Allows us to run the framework from command prompt
Ant ->Will only allow us to execute the framework from command prompt
Now the code is mainatined at a common location ->Git
Jenkins
Now the framework is over -> in the maintainence phase, we need to schedule it using Jenkins. Also intimate all the users about a success/failure of the build emailed automatically.
Comments
Post a Comment