Is that a comment on the title or the content of the video?

@@EvilTester Tittle

True. But the role is requiring us to be more technical than usually expected. within the last 2 years, I have seen 2 colleagues get terminated in 2 different companies cause they couldn't catch up with tech stuff, ie code.

Change te title please!

​@@last_samurai6690So they wanted automation testers. Why hire manual testers then?

How did you get started ? I have no experience but interested in learning more but dont know where to start.

Yeah how??

QA is often used as a catch all term. Sounds like you've mainly worked in environments where it is used to mean "Testing", so I'd suggest it is less likely that the QA department would be made redundant :)

@@EvilTester More like it became apparent that testing was not enough to describe what the QA team actually did. Testing was one of the main tools. But not the only one. More like a hammer for a carpenter

Interesting thoughts.... Exploratory testing just by itself saves so many bugs. Also automation frameworks are the big thing but they aren't that reliable... They're flakey due to many reasons selectors and page loading issues to start. Automating imo should just be happy path for regression.

Thanks Kim :)

Hey Kim. I know in Auckland. are you still doing qa coaching? a friend of mine has been asking me how she can become a QA but I didn't know where to start.

For strategic automation... I'd recommend sticking with the language that you know best and the one which you think you want to continue using most. Which in your case might be JavaScript. This keeps your options open for your career path programming/testing and gives you continued practice with the language. For tactical automation e.g. writing quick scripts to do stuff, which might be throw away, Python is a very good option because it has a lot of excellent language support. All languages are fine, but it is easier to use a language you know because then you aren't having to learn a tool, and a language at the same time. Additionally, JavaScript can be used as an embedded language in tools like Postman so the skills you have developed can be re-used. Also check out the free courses on testautomationu.applitools.com/ and initially look for courses that cover the languages you know.

@@EvilTester thank you EvilTester, I appreciate the insight.I enjoy JavaScript an I feel moat at home with this language you were correct. My experience only extends to web development. I will try out the link and postman, thank you for the recommendation.

@@EvilTester I'm happy to hear that I can stick with a language I'm most comfortable with. I've been studying Android development and learning Kotlin up until now. I know that Java is used a lot in testing and since Kotlin is interoperable with Java I look forward to implementing it in my projects. I've already found some good resources online utilizing Kotlin for this purpose.

That's great. Pushing the boundaries... finding the 'one' input that makes difference... looking one level further down to observe, or inspect, and find something that doesn't meet expectations... following the 'but what if...'... all of these are important, someone has to have that attitude.

Did you watch the video? In the video I advocate for more and better testing.

@@EvilTester I know but you didn’t say about these things. I think that is a kind obvious to have a qa engineers in a team. And I think this is a good question at the interview 😊 can we ?

I'm assuming you didn't watch the actual video. But if you did, then I'd be interested in reading a longer comment describing where you thought my analysis in the video went wrong.

I'd start by looking at the type of jobs you want to do and seeing what skills they are looking for. Then picking one of the basic courses on free code camp for those skills. See which of the skills you like doing and keep going.