Tag Info

Hot answers tagged

11

For Test Automation purposes, it's always been my belief that once you know 2 scripting languages, you are in very good shape. Being comfortable with 2 languages means you know how to automate, and that you know how to learn a new scripting language. As a hiring manager, I will be able to assume that you could easily pick up another new language as needed. ...


7

To paraphrase & quote Lessons Learned in software testing "We see no compelling reasons for vendor scripts." ... They make coding difficult They are hard to learn They interfere with the collaboration between developers and testers It is hard to build on the work of others See the book for the full description of these. I would ...


7

The programming language you pursue should be predicated on The technology space you are most interested in (web, platform, mobile, etc) The market trends in your area (e.g. what language skills are employers most looking for) On a side note, I don't know why some people get so focused on a particular "programming langauge." Instead, I recommend ...


7

See, you can learn Selenium with any language whether it is C#, Java, Ruby, Python etc. It doesn't matter application which you are going to test has been developed in which language, you can test the C# application in Selenium with Java. In addition to it, you don't need to learn any of these language completely for working with automation. You should know ...


5

I am assuming that you: want to become competent programmer, with goal to learn programming beyond Selenium automation. have nobody around to ask for guidance (if you do, ask locally) also want to be able to write simple tools supporting QA tasks, and beyond. Python is widely considered as best language for beginners (MIT among others). It works much ...


2

Welcome to SQA, Nitesh. In my market, what you tested and how you tested it would be at least as relevant as what programming language you used. I think having a variety of experiences will be more useful to you than specializing in one thing. However, your market might be different. For example, if you work in short-term contracting projects, ...


2

Well, the original question had two aspects. Proprietary testing languages and TTCN-3. While I totally agree with the answers towards the proprietary/vendor languages, I would definitely not include TTCN-3 into this discussion. TTCN-3 is a multi-purpose, internationally standardized and therefore nonproprietary test language. I frequently get the ...


2

Proprietary testing languages are beneficial for those who sell proprietary testing languages. They are also beneficial for certain consultants, technical book authors, technical conference speakers, and testers who need more words on their resume. For all others, not beneficial. One would not test screws with a hammer. In the same sense, for a given ...


2

I agree with Bruce - I see no benefits. I happen to be currently using a tool with a Basic-like proprietary language. It's a terrific tool and does much of what I need. The language is full-featured, easy to learn, and well suited to our tasks and our style. I have no complaints. Still, it would be even better if it were non-proprietary language.


1

There are two sides of your question which I am interpreting (and may be I am wrong), but this is how I see it : You can choose your language based on the ease of learning. You can choose your language based on the support for that particular implementation. Let's talk about first- I have used both Python and Java implementations and I agree with Peter, ...



Only top voted, non community-wiki answers of a minimum length are eligible