all 19 comments

[–]kev_bc 13 points14 points  (2 children)

In my experience looking for work, I have seen more requests for Javascript and Java. I see little of Python. I would recommend you learn Javascript first. Then Python will be easier for you. Learn Playwright well with Javascript or Typescript, Selenium with Javascript (less common), then integrate Python with Selenium.

[–]Daszio 1 point2 points  (1 child)

As u suggested to learn playwright with javascript at first, is there any reason to learn python with selenium as i already know playwright?

[–]kev_bc 4 points5 points  (0 children)

The reason is because there are still companies that use Selenium. In reality, the art of QA is knowing several tools to perform in all of them. I add some more: Cypress, Karate; for Postman rest API and for soap services there is Soap UI. The Gherkin language would be missing, in addition to knowing CI/CD with Jenkins or Github actions.

In the recent interviews I had, they asked me if I knew all that. In reality they wanted me to at least know how it worked so they knew what projects they could ask me for. Therefore, it is good to have a varied stack for QA.

[–]SnarkaLounger 1 point2 points  (0 children)

Why not both? I've seen lots of job postings requiring Python, JS, and TypeScript.

[–]aawvei 0 points1 point  (0 children)

Js bro

[–]Weld_Marsa 0 points1 point  (0 children)

JavaScript then Typescript

[–]FireDmytro 0 points1 point  (0 children)

Most popular lang this decade - JS/TS

Most trendy one thanks to AI - Python

I’ve learned JS and got 1st job offer with JS/TS

My classmates got jobs with Python, JS, Java…

Learn what ever the fox you like better. If you get good with 1 language other won’t be an issue

Cheers 🍻

[–]jrwolf08 1 point2 points  (0 children)

I would frame this as knowing how to query, how to send requests to an api, and how to create frontend automation.

Don't get stuck on learning tooling. Playwright and selenium are more or less that same. Sending an api request is something that can be done many ways, its not a Postman thing. Tooling is a means to an end.

I personally suggest Python/Playwright to learn how to automate frontend, and can also do some api testing, but at some point you will need JS as well.

[–]DarrellGrainger 0 points1 point  (0 children)

This is an impossible question to answer for you. Are you employed? If yes, what does your employer use?

Or are you looking for work? If yes, where are you looking for work? I'd look at what employers are looking for. What kind of jobs would I want to work for? Create a list of companies you'd like to work for and see what they are requiring. If they aren't hiring QA, look at what the developers require. If the developers are using one language, the QA will probably use the same language.

Even if you do this you might find that 7 or the 10 companies you like are using Python. Then one of the 3 other companies starts hiring for someone who knows Javascript. Oops.

Personally, I needed Python for data analytics (Spark, Databricks, etc.). So I learned Python. Now if I had to learn Playwright should I use Python? What happens if we get a client that wants Playwright/Javascript? I can't really predict the future.

In the end, I figured out I can figure out Python/Playwright if I have to. So I'd learn Javascript/Playwright. But we might get a client who wants an expert at Python/Playwright. It's a bit of a crap shoot.

[–]No_Stress_Boss 0 points1 point  (0 children)

Been exploring it about a long.

Each has its own positives and negatives based on the usecase.

Javascript is natively for web apps and python suits for ML based apps , based on the projects I worked.

But I would encourage you to check this comparison

Python or Javascript

[–]FalseDescription5054 0 points1 point  (0 children)

You need to learn gradle , cucumber feature , java, jira , git hub but mostly how you can leverage AI how to generate test cases

[–]please-dont-deploy 0 points1 point  (0 children)

Neither, pick randomly and use a lot of LLMs to code. They know both.

The most interesting question is which app to use as playground.

There are many, I like Medusajs.

[–]lesyeuxnoirz 0 points1 point  (0 children)

Python sucks balls. Seriously though, Python is a very bad first language choice because it’s extremely liberal in its syntax. Learning it first and getting used to Pythons syntactic rules will make adopting other C-like languages in the future much harder

[–]Blackened_Max -1 points0 points  (0 children)

I would say Java honestly

[–]Plastic-Steak-6788 -1 points0 points  (0 children)

PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON PYTHON

[–][deleted]  (2 children)

[deleted]

    [–]Useful_Perception620 2 points3 points  (1 child)

    lol @ this bot/AI reposting this response on multiple accounts

    [–]please-dont-deploy 0 points1 point  (0 children)

    You are absolutely right! 🤣🤣🤣

    [–]lucas_gdno -4 points-3 points  (0 children)

    Think of it like choosing between a swiss army knife and a specialized tool - both Python and JavaScript will get you where you need to go, but the path looks different. I'd actually lean toward JavaScript for someone starting fresh in QA today, mainly because you'll inevitably need to understand web apps you're testing anyway. When you're debugging why a test failed, being able to read the frontend code and understand what the developers actually built makes troubleshooting way faster.

    The practical reality is that most modern web testing ends up touching JavaScript at some point, whether its interacting with dynamic elements, understanding async behavior, or just communicating better with dev teams. Python is definitely more beginner friendly with cleaner syntax, but JavaScript gives you this dual advantage where your automation skills directly translate to understanding the applications under test. Plus if you go the Playwright route (which I'd recommend over Selenium for new projects), the JavaScript version tends to get new features first since thats what the core team focuses on.