So why Java? From my previous posts, I was at the cross roads between becoming a more technical QA Engineer or switching gears to becoming a Junior Mobile Developer (being on the side of Android). With Java, I can continue going towards my path of a software developer or using Java as the language to use for an automation framework. However, I was introduced to a role I haven't heard of before - Software Engineer in Test. This brings a strong software development knowledge into the QA role that goes beyond unit testing. Well, what does that even mean - beyond unit testing? This includes automation, integration, scalability, performance and reliability as well as writing tools that would help both the software developer and QA. I was told by a friend, don't throw away your QA knowledge and experience to become a developer, learn how to use development as a way to further invest in your QA career and skills. That definitely wasn't verbatim, but that was message - and he was right.
Quality Assurance can be viewed differently among different organizations and it seems to be in par with how a company prides itself in upholding a particular set of standards. Not everyone takes quality as a pillar of support to uphold a company brand - similar in how some companies view security or customer support. Understanding how quality translates to a customer transcends the barrier of the value or price of a product. Take Apple for example, despite being a generally more expensive as well as being mentally conceived as more expensive, users are happier putting in a bit more money for the quality of a solid product in both design, hardware and software.. These are returning customers and quality is one of the major factors of such.
Though equipped with python and some Java from the books I've studied from and the online classes I have taken, the class itself was initially intimidating, The first thing the class does is ask the student to take a short quiz to gauge the level of understanding you have of Java - and after taking it, I was a lot less cautious about moving forward and instead, a lot more excited..
I believe for any QA that wants to go beyond the black box, picking up a language is necessary. I personally believe that all QA needs to start with python if they do not have any programming experience - check out Zed Shaw's Learn Python the Hard Way. I think paying the $40 to get videos alongside with the pdf is worth it, but if you don't want to shell out money that costs less than a video game, he does offer the pdf for free! After an introduction to Python, I highly recommend researching the language that makes sense for your current profession or your potential future profession. For me, it';s Java.
Feel free to ask me any questions you might have about getting started in learning a programming language or your thoughts on QA in the software development industry!