Most of the QA professionals are among the smartest people on this earth who often boast advanced degrees in engineering, mathematics or computer science. In some ways, we are like Superheroes – capable of breaking down a whole application and defeating an army of programmers with our defects, testing complex functions, juggling numerous technologies, ensuring customer ideas morphed into working software, all the while not breaking a sweat. So how is it that despite such technical savvy, programming prowess and quality driven attitude, we are defeated at test estimation front?
I have a strong functional test experience but no automation. I ‘know’ automation testing but don’t have the project experience. I am a Test lead but didn’t write any automation scripts. Analytical & logical but never did project coding. Found in-numerous bugs but didn’t prepare automation reports. Managed a big team but didn’t learn performance testing. Documented every report but didn’t produce framework guides. Enjoyed exploratory tests but didn’t script pre-defined test cases. Helped BAs and even developers (in debugging) but never developed automation framework. Understood domain & application flows but didn’t write code. Open to learning but no opportunity. Self-learned programming & tools, but didn’t get practical project experience. Passionate about Software testing but now it’s Software Developer in Test.
Though the aspiration for being a successful IT professional is strong, we assume that the word ‘IT professional’ is synonymous with ‘Developer’. When a testing opportunity presents itself, there are many doubts in our minds and we often wonder if it’s the right career move or not. While being a developer is great and has immense potential, it should not be concluded that being a tester means the exact opposite. Let’s explore the reasons behind the perception – Software Testing is inferior to Development,
Steve Jobs. J.K. Rowling. Walt Disney. Oprah. What do all these famous people have in common? They’ve all been fired. If you’re currently staring at your own pink slip – or anticipating one in the near future – you can take a tiny bit of comfort in knowing that you’re in illustrious company. In today’s tough economic times it’s inevitable that the season of joy and mirth brings news like this. Whatever the reason, getting fired sucks, big time. It can be one of life’s most stressful experiences, your feelings of self-worth and self-esteem are dealt a blow. The first reactions to getting fired are usually anger and pain, followed by feelings of confusion and disillusionment. It’s like getting dumped in a relationship, except you lose your paycheck too. However the good news is that losing a job is not the end of the world and with the right approach and perspective you could turn something bad into something positive. And that means taking a deep breath, getting yourself together, and looking at your situation.
In an agile business, automation is becoming an essential process. Companies are now taking advantage of automation testing tools to increase their efficiency and productivity. Automation is frequently evangelized as the cure-all of software quality woes. Some of the benefits that accrue from automated tests include test reusability, repeatability and coverage besides the savings on effort, time and cost it takes for execution (compared to manual testing). However it’s NOT the answer for everything. Test automation, while being able to improve numerous aspects of software development, has limitations that developers and quality assurance teams should be aware of from the start. Understanding these limitations of automation testing will help us devise an efficient & effective automation strategy.
Quality – Why is this word so important for your software? Software teams today involve a number of people: developers, testers, support engineers, designers, product managers, and executive stake holders. A low quality software impacts all of these or in other words everyone in the team is responsible for the quality of software delivered. When we look into the overall effectiveness or cost manual testing still have a pivotal role to play. Unfortunately, very little discussion is only happening on how to improve efficiency of manual testing instead most of discussions are happening on how to increase the level of automation. Many of us would advocate the fact that Manual Testing is no longer needed, and I know it well why they think so. It is mostly because of the drawbacks and challenges associated with Manual Testing.
Automation testing is a concept that is heavily marketed today. There has been a real convergence of tools and approaches in automation in recent years. It’s increasingly considered as integral to project delivery, rather than something that exists to cover business-as-usual regression testing after project completion. Faster releases, increased test coverage, frequent test execution, faster feedback to development team, just to name a few are being counted as some of the Test automation benefits. Automation is being portrayed as the silver-bullet in testing technology. But everything is not so ideal. Not every organization (or client) is reaping the actual benefits of Test automation. Certain Automation testing myths must be addressed in order to correctly apply it in the most effective & efficient manner. In this article we shall examine some of the most common automation testing myths and how these prevent organizations from succeeding in Test automation.
As discussed in our earlier article Manual vs. Automation Testing – on a high level there are basically two methods to complete the software verification & validation – Manual and Automation testing. Each testing method has its pros and cons but the truth is that regardless of which side of the fence you sit on (manual vs. automated), the argument is largely irrelevant; to achieve high quality software and reduced time to market both methodologies are essential. Let’s explore the remaining key consideration…
Software testing, though complex, is an integral part of any successful software project. On a high level there are basically two methods to complete the software verification & validation – Manual and Automated testing. While both types of testing are beneficial to web application development, there has been a plethora of speculation on whether software testing should be done manually or be automated. Creation of excellent software demands effective and timely quality testing; and in these times of production on the go, the debate continues on the purpose and efficiency of manual vs. automation testing. Each testing method has its pros and cons but the truth is that regardless of which side of the fence you sit on (manual vs. automated), the argument is largely irrelevant; to achieve high quality software and reduced time to market both methodologies are essential. Let’s explore the 19 key consideration…
The overwhelming evolution of the software testing industry is forcing testers to continuously strive to upgrade their skills. In the last couple of years, software testers have seen the writing on the wall: as test operations grow increasingly automated, scripting skills are essential to grow your career in Software Testing. Automation testing is the new ‘necessary’ trade you at least need to know about. Software testers with manual testing skills alone won’t cut it in today’s job market. It all started with Manual Testers, but as the supply grew (it’s really crowded now) the industry needed some measure of Tester’s capability apart from Manual concepts. The easiest was of course – scripting skills – after all IT is all about that ‘lines of code’ 😉 and hence Automation Testing became the new ‘Generic’. The fact remains that automation testing continues to rise.
2017 is here…what is your New Year resolution? New Year resolutions are often ignored for months, only considered again at the next New Year 🙂 Creating a list is a good place to start. Prioritizing that list and planning to invest in the most important can help accomplish the goals. This article summarizes the Top 10 latest trends in Software Testing for 2017. Unlike other lists focused on enterprises, this list is for ‘Software Testers’ to focus their energy on the right skill sets. The overwhelming evolution of the software testing industry is forcing testers to continuously strive to upgrade their skills. This list is based on our observations and experience with the current hiring market. After all everybody needs a respectable ‘Job’ first & professional growth thereafter – leverage these latest trends in Software Testing, re-strategize and re-skill.
Each industry is different when it comes to their way of business, hence the required skill set also varies not only from the technical perspective but also from the business perspective. In simple terms – Domain is basically a grouping based on the type of business rather than technology/platform. Almost all IT companies organize their projects in different verticals based on different domains. Some of the common domains are Banking, Retail, Insurance, Healthcare, E-commerce, Telecom, etc.
Regression is one of the most Important yet Neglected Test Type. Let’s see what are the Regression Testing Best practices for a successful project delivery!
Some say ‘Testing’ is not a skill set, I say Yes. It’s a ‘Mindset’! We have quite to learn from Virat Kohli, what makes up a solid Mobile App Tester?