Test Automation With Selenium

Selenium RC Selenium Web driver Selenium RC is slower since it uses a JavaScript program called Selenium Core. This Selenium Core is the one that directly controls the browser, not you. Web Driver is faster than Selenium RC since it speaks directly to the browser uses the browser’s own engine to control it. Selenium Core, just like other JavaScript codes, can access disabled elements. Web Driver interacts with page elements in a more realistic way. Selenium RC’s API is more matured but contains redundancies and often confusing commands. Web Driver’s API is simpler than Selenium RC’s. It does not contain redundant and confusing commands. Selenium RC cannot support the headless HtmlUnit browser. It needs a real, visible browser to operate on. Web Driver can support the headless HtmlUnit browser. Selenium RC Has Built-In Test Result Generator. Selenium RC aut...

Webdriver is a tool for automating testing web applications. Webdriver makes direct calls to the browser using each browser’s native support for automation. Selenium Webdriver does not depends upon the server. We can directly run the scripts in the main method. Selenium Webdriver is very simple, easy to use. Advantages: 1) Support for iPhone and Android testing 2) Implementation of listeners - a much awaited feature 3) Better features for Ajax testing. 4) You can easily simulate clicking on front and back button of browser. 5) You can simulate movement of a mouse using selenium. 6) You can find coordinates of any object using Webdriver. 7) You have classes in Webdriver which help you to simulate key press events of keyboard. 8) Keyword driven framework is very easy to build in webdriver. 9) Selenium Webdriver supports various languages for example java, Python, C#, Ruby, Perl, Php, Java script. 10)  WebDriver is open source & it allows you to easily integrate with testing fra...

Microsoft Windows: Most versions of MS Windows that are currently still supported by Microsoft should work with Selenium. Altough here's the list of OS's we currently run tests against before each release:     Windows XP (to be unsupported on April 8, 2014)     Windows 7     Windows 8     Windows 8.1 If your version of windows is not listed, it does not mean Selenium won't attempt to support it. That only means we don't continually run tests on that particular version of Windows. Apple OS X : We currently do not use any version of OS X in our automated tests against the selenium project. However most developers on the project are using a recent version of OS X and we'll continue to support the current stable release and often the previous release. Linux: We test mainly on Ubuntu, but other variations of Linux should also work where the browser manufacturers support them. iOS : The first lines of the ...

 Following programming languages are supported by WebDriver     Java     .Net     PHP     Python     Perl     Ruby

Firefox: Support for Firefox is the latest release, the previous release, the latest ESR release and the previous ESR release. For example Selenium 2.40.0 (released on Feb 19, 2014) supports Firefox 27, 26, 24, 17. Selenium with Firefox can be run on any platform that Firefox supports for those versions, that also allow users to install a custom Firefox extension. Internet Explorer: Versions 6, 7, 8, 9 and 10 are supported. 11 is currently awaiting a fix for this issue. The selenium project tests each release on Windows XP, 7 and 8. Google chrome:  All versions. Safari: Safari Driver requires Safari 5.1+ and only runs on OS X. Opera: Opera Driver requires Opera 12.x and older versions.

Selenium first came to life in 2004 when Jason Huggins was testing an internal application at ThoughtWorks. Being a smart guy, he realized there were better uses of his time than manually stepping through the same tests with every change he made. He developed a Javascript library that could drive interactions with the page, allowing him to automatically rerun tests against multiple browsers. That library eventually became Selenium Core, which underlies all the functionality of Selenium Remote Control (RC) and Selenium IDE. Selenium RC was ground-breaking because no other product allowed you to control a browser from a language of your choice. While Selenium was a tremendous tool, it wasn’t without its drawbacks. Because of its Javascript based automation engine and the security limitations browsers apply to Javascript, different things became impossible to do. To make things worse, webapps became more and more powerful over time, using all sorts of special features new browse...

There are a few factors that have attributed to Selenium’s success. Since this is a free tool, it often is one of the few options for companies that do not have a lot of budget for Automation tools. Selenium was first written in Java but it also supports .Net, Ruby, Perl, PHP and Python. This is a big plus when you want to build your framework in a language that has the highest adoption in the organization it is being built within. Tools like QTP force you to use VBScript – which is almost never the preferred scripting language for developers. Since this instantiates and drives a real browser, as opposed to simulated browser solutions like HtmlUnit, this tool runs in a client that is closer to what a real user would use. This in turn provides more confidence that tests run with this tool would catch most issues that a real user would experience. It has support for all of the popular browsers like IE, Firefox, Chrome, Safari etc. It also supports several Operating S...

Selenium is one of the most popular tools for browser based testing. It is an Open Source project that has gained a lot of popularity in the last few years. Even though there are other Open Source (free) tools that can test a web application, like HttpUnit, HtmlUnit etc, this was one of the first tools that provided a real alternative to commercial tools like Quick Test Pro (QTP), WinRunner, Silk and others that had gained significant adoption by the QA Engineers .

Software testing is done by using two methods, manual and automation. In manual testing of software human intervention is a must. In Test Automation human factor is not as important as this is a prerecorded set of rules that can be reversed. In manual testing, bugs and errors cannot be easily identified, in automation testing bugs and errors are not only identified but it is fixed by developers. Automation testing is more useful in software development rather than manual testing. Manual testing is suitable for that software that does not have a large number of users. Automation testing is apt for that software that has to manage large data and a big number of users. Manual testing is time consuming because the entire process of software testing is repeated to modify the source code. In entire manual testing human involvement and effort is required, on the contrary in automation testing, test cases are executed on application several times, in order to get the expected behavior, and r...

Since not all projects require automation, you need to consider the efficiency of manual tests and see how much coverage the project entails. For instance, if the project is a small one, automation testing should not be a requirement since you may not have the money or resources needed to complete the project and hire an automation specialist. However, for larger projects, bringing in an automation expert is a necessary step in testing, even if it may be a little costly. Using simple automated scripts instead of manual tests with certain projects that use websites could be both cost and time effective. This would ultimately reduce the time spent on testing as a whole. Can reduce the time and cost of software testing Can improve software quality Can enhance manual testing efforts via increased testing coverage and replaces the manually mundane and labor intensive tasks Can achieve what manual testing can hardly accomplish, such as memory leak detection ...

Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not limited to the process of executing a program or application with the intent of finding software bugs (errors or other defects). It involves the execution of a software component or system to evaluate one or more properties of interest. In general, these properties indicate the extent to which the component or system under test:     meets the requirements that guided its design and development,     responds correctly to all kinds of inputs,     performs its functions within an acceptable time,     is sufficiently usable,     can be installed and run in its inte...