Selenium is a open-source web based automation tool. Selenium enables user to automate browsers.
Selenium supports only web automation, and it doesn't support automation of desktop applications. Let's understand what the components present in the selenium webdriver architecture are.
Selenium WebDriver imitates real-world user behavior as closely as possible. Since the real-world user is not able to interact with any invisible element or elements not rendered yet, neither does the web driver.
So we need to always make sure that the web element is in the right status before we try to interact with it.
Dotted Lines represent a class implementing an interface. Solid Lines represents class implementing class or Interface implementing the interface.
Search Context is the topmost interface in web driver, Webdriver Interface extends the Search Context, Remote Webdriver class implements the Webdriver Interface, Browser classes (FirefoxDriver, ChromeDriver..) extends the Remote Webdriver Class.
This is a problem though because the browser is getting a script from Selenium(http://localhost:9000/selenium), which tells it what it wants to fetch resources from https://websitetotest.com. The browser says, "hey, this script came from localhost, and now it's requesting a resource from some outside website. This violated the same-origin-policy.
Same Origin Policy With Selenium RC : Selenium RC tricked the browser by proxy, and the browser considered that both webpage and server are from the same host, so the browser lets the Selenium RC to run.
Same Origin Policy With Selenium Webdriver : Webdriver provides native OS-level support in controlling the browser automation, so the browser feels like there is only a webpage. (with RC and Core it was Webpage and server)
Human Way of Same-origin Policy :
Selenium Core: Consider you are the webpage, your manager/wife could be the server which tells you to do this, do that. At some point, your body realizes that no need to follow them, as your mind does not generate these, this was the problem with Selenium Core.
RC example : Someone hypnotized you, and they are just asking you do to some job, and you are doing them this is selenium RC, hypnotization is nothing but the proxy.
Webdriver : You have been told what to do when something occurs from your childhood. Now you will do the same thing even after becoming an adult. But you will never realize that you were doing something that someone taught you long back. The only thing that you feel is, this the way of doing.
The most significant difference between selenium 3.0 and selenium 2.x is, In Selenium 3, all the major browser vendors are providing their own WebDriver implementations (Apple, Google, Microsoft, and Mozilla) instead of being developed by Selenium project (Selenium 2.x) and because they know their browsers better than anyone else, their WebDriver implementations can be tightly coupled to the browser, leading to a better testing experience for you.
Most Unfortunate thing is, all the browsers are updated now, so selenium 2.x is not supported by them which forces users are forced to use Selenium 3.0 version
Mozilla has made changes to Firefox that mean that from Firefox 48 user must use their geckodriver to use firefox browser, regardless of whether you're using Selenium 2 or 3.
Selenium 3 is more mobile automation focused, maybe in future Selenium replaces Appium or Appium replaces Selenium.
HtmlUnitDriver is now packaged separately, means for headless testing we need to add the htmlunitdriver
Selenium (3.8.0) doesn't support for PhantomJS, and it's recommended to use headless Firefox or Chrome instead
Below are a few scenarios where we go for automation:
The type of testing selenium supports are basically Functional Testing and Regression Testing of Web Applications
I believe that instead of looking into a Selenium automation career, you should aim at something more significant.
Selenium automation is basically programming with an automation library, so instead of becoming a specialist in a library, why not do that for the language?
In selenium terms, Apache POI is a library, if you become very expert in that apache poi, do you think, you know everything, NO.
Similarly, Selenium is also a Library/Framework in the language(selenium framework is there in different languages).
Focusing on only selenium may help in shorter-term (6-8 years), but for the long term, benefits learn the language and learning a library will not be difficult if you know the language
What is the name of someone who specializes in using a programming language? Ah, yes, a programmer.
So why not aiming at being a programmer since then you have a lot of options?
You could do test automation but not only with Selenium WebDriver but any other automation library or tool.
Why bet your career on using one library? No one can tell if Selenium will be here in 5 or 10 years because no one has the ability to look into the future.
Maybe Selenium Project Manager(selenium's official dev team) will decide at some point that he does not want to manage the Selenium project and then the project’s quality goes way down.
With low quality, fewer and fewer companies will use it, and not many will need Selenium automation experts.
Many companies will not have in the future dedicated staff for test automation; Developers will do some of it, dev-ops will have a slice of the automation pie as well, maybe some testers will join in.
What a good programmer combines the selenium with some open-source Robotic Process automation tool, then every company will remove the test programmer as they anybody can drag and drop elements in RPA.
I would suggest you not only to learn selenium but also put more focus on language and analytical skills for solving the problem.
1. Selenium does not offer any certification.
2. Selenium was introduced for free; they support it for free.
3. Some folks in the technology field who have studied Selenium are selling it out, but which is not considered as a certification.
4. If you really want to do the certification, then do the certification on the Programming Language, which you use for selenium.
1. Becoming a Selenium automation expert in 4 months, I took almost 6 Years to become such a level and still learning. So stop becoming an expert in 4 months, because you cannot do so.
2. Learning selenium for certification, because there is no such thing called certifications for selenium.
3. Starting selenium scripting without even learning the Programming language, learn programming language first
4. Believing a learning website as ideal for learning everything about selenium, I own this site, but I still suggest my reader not to stick to this site as this site is a replica of my views or learning on selenium.
5. Believing Selenium IDE is basic to Selenium Webdriver, Selenium IDE aka SIDE has no influence on Selenium Webdriver.
6. Not asking for help, I have seen people who are scared that If I ask this question, then my senior or SME may identify me as a guy do not have knowledge. Know this, knowledge is nothing but knowing the subject, but if you do not read or ask anyone, how you will know anything. Ask the expert/experienced guy.
7. Only preparing for interviews, when you don't know the subject you cannot survive in a company even though you cracked an interview
I am Pavankumar, Having 8.5 years of experience currently working in Video/Live Analytics project.