Richard Gunn – Just another WordPress site
The Extended vanRhee Family Site
Code & QA – (codeandqa.com)
Account Suspended
“Selenium automates browsers”. So goes the introductory line on Seleniumhq.org. To what extent is this a limitation? The topic of the blog provokes questions – Can we structure a Selenium-based test framework to test beyond GUI browsers? If not, at the very least, how can we improve test-effectiveness by extending an existing Selenium test-suite to work with other test-actions that do not use browsers? The first question above needs in-depth technical discussion. We focus on the second one here which can be
Writing automated tests is more than just a luxury for any agile software development team. It is a need and is an essential tool to find bugs quickly during the early phases of software development cycles. When there is a new feature that is still in the development phase, developers can run automated tests and see how other parts of the system are affected by those changes. Through test automation, it is possible to lower the cost of bug fixing and bring overall improvement to quality assurance (QA) proce
Often in the testing of web applications, every form on a page is described as a separate entity (object) – usually, one single form (in most cases it represents an isolated functionality) is equal to a separate class. All these objects/classes consist of web element instances (various web elements located on the related web form) and methods for interaction with the elements. Let’s imagine there is a Login form in a web application. The form may be described as: public class Login { IWebDriver driver; publ
Richard Gunn – Just another WordPress site
The Extended vanRhee Family Site
Code & QA – (codeandqa.com)
Account Suspended