Selenium components and their architectural differences.

I have seen many people asking a repetitive question in interviews if they see Selenium written on any Curriculum Vitae of a Test Engineer. Though I believe theoretical and conceptual knowledge is equally important as hand-on experience.

As a part of the hiring panel, I have observed this as a pet question of our hiring team: ‘How about the architectural difference between Selenium versions.’ Of course, once they are done with questions like ‘What you know all about selenium’ ?

Selenium generally comes in four different flavors:

• Selenium IDE,
• Selenium RC,
• Selenium Grid and
• Selenium Webdriver.

I will be sharing the best answer I got and the research which I did so as to understand the architecture of selenium.

Fitnium – Quick start !

Den her Romeo bløder
Men du kan ikke se hans blod
Det her er kun følelser
Som denne gamle hund gravede op

Ce Roméo saigne
Mais on ne peut voir son sang
Ce ne sont rien d’autre que quelques sentiments
Que ce vieux chien a réveillé

Bu Romeo kanıyor
Ama kanını göremezsiniz
Bazı duygulardan fazlası değildir
Bu yaşlı köpeğin tekmelediği

Nice song , yeah !!!

Which one of the above translation you find easy to understand. And how you can actually make this understand to all other unheralded persons who does not know ‘Always’ song or Bon Jovi for that matter.
The answer is you will translate the same in to a common language which everyone can understand like ‘English’ in a similar manner like this :

This Romeo is bleeding
But you can’t see his blood
It’s nothing but some feelings
That this old dog kicked up

Behavior Driven Development can make your life more relaxing.

In agile methodology, when we talk about delivery then it’s all about customer satisfaction and acceptance. Recently, I presented a session in an open forum stating what Behavior-driven development (BDD) can actually do and how can we start applying BDD in our day-to-day development.

BDD is an interface between a coder and a customer. It turns a requirement into a simplified language, which everyone can understand, and then in the backend, the required work is done.

Generally, the requirements are not clear initially and then the costs incurred to add changes are more in the long run, say, at the time of delivery. The best part of this technique is that we can bridge the gap and have a common understanding of the Definition Of Done between all; coder,  quality analyst, customer, end-user, business analysts. This applies to each and every person who is involved in the software development process right from the initial days to the delivery of the product.