If there is one myth in theautomation existence that drives me crazy it is that browser automation scripts need to be written in the same language as the application is write in. It appear like that should be a Good Idea; in principle, but in world it is actually responsible for a lot of & # x27; neglect & # x27; automation efforts.

Let & # x27; s choose a language to pick on. How about C # using ASP MVC; has a big user foot (especially in the enterprise space) and pretty mature stack to use. (We could have pickedanylanguage ...)

So now we have a nice ASP MVC application that we think is locomote to solve some customer & # x27; s combust want andof courseit & # x27; s nicely unit essay because you are doing some variant of TDD/BDD. Your browser mechanization scripts should naturally be written in C #, right?

No.

Well, really, & # x27; maybe & # x27;.

Ifbrowser mechanization is the duty of the developer who implement a particular lineament then it makes sentience for them to pen it in C # as they (in possibility) know that language and its nuances. And they can recycle the like runner and its idioms for hold the browser book. If they don & # x27; t know C # and are implement lineament, you might have a big job to solve than just browser automation ...

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

What happens more frequently though is that the developers are not responsible for browser-based trial. That falls to the test squad or some semi-autonomous group who is focused all on automation.

Do they know C #? Awesome. Use that words. Butif they do not then they should not.

Well, usually.

The vast majority of teams start with browser mechanisation either don & # x27; t receive programming skills or they are extremely rusty. Neither of those are predecessor of a successful project. This is about the point where someone has the magnificent idea of imagine they will & # x27; merely & # x27; learn the words to the creditworthy team. Ummm, ya. Have you e'er taught someone to programme at a professional level before? It & # x27; s not that easygoing. And good luck if you are utilise C # (or Java, or C/C++ or other ceremonial languages).

I spent 4-ish years consulting on largely this & # x27; getting started & # x27; trouble. Python, Ruby, and yes, PHP are the keys to getting teams up and running on browser mechanisation fast and effectively. Very little ceremony, powerful, large foundation to pull support from, and need only a fraction of the overall language to do effective browser mechanization. It is no real surprise that a number of university are now utilise those languages for the year one introductions to programming.

& quot; But! But! My Continuous Delivery Pipeline!!! & quot; you may be screaming. Yes? What about it? I & # x27; ve not seen anyplace that say all action in a pipeline motive to be the same lyric. Its just another item that happens to be a different language than a previous item.

Now with all all that having been said, there is actually one really full reason to write your handwriting in the like language as the application itself. And that is when there is a laughably complex algorithm implemented in that language that you want to leverage as constituent of your substantiation measure. But that is actually rarer than you might expect. I & # x27; ve really only encountered it once and that was with a crazy geo-fencing algorithm. (And even then, we cheated and used IronPython to enable us to use Python but withal slurp in the .NET assembly.)

Remember, your web server doesn & # x27; t care what kind of human is in front of the browser. Why the heck do you think it is travel to wish what form of programing words is driving the browser?Pick whichever words makes the most sense for the team authorship and maintaining the scripts and cease be such a lyric snob.