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?
Feeling stagnant? Want to come out of your comfort zone but can’t? Who doesn’t want to succeed. Who doesn’t want to be a Leader. But that doesn’t come easy – you need to be open to learning and improve each and every day. To charge you up, let us introduce you to our Daily Motivational Quotes series to change your Professional life…Get Started…!!
SDET, expands to Software Development Engineer in Test OR Software Design Engineer in Test. Don’t get confused. In simple terms – the SDET is a tester and also a developer. Haha! Confused? I too felt the same. No one is crystal clear about the SDET role – I guess not even an SDET himself/herself 🙂 a fancy word adopted by Microsoft and every one going Gaga o
Independence & Freedom – everybody likes it. Wants it. Fights for it. And finally celebrates it. It gives you the objectivity to express your views & opinions. It is essential for a thriving society where the mind is without fear & the head is held high. As India celebrates its ‘Independence Day’ on August 15th, let’s see what it means for a Test team.
Agree or not, once in a while every one of us enjoy criticizing something – a person or a situation. A conflict between a developer & a tester is not new – it has been there since the inception of Software Testing. After all, nobody likes it when their mistakes are pinpointed & written on the wall. What they don’t understand is – it’s not about ‘You’, it’s about the ‘Software’!
First of all, the question ‘What’s the average salary of Software Test Engineer’ is like asking ‘What’s the average house rent in Bengaluru, India?’ You tell me…Can’t? Yeah! You need some more filters to arrive at the rent – the house type (whether it’s a 1BHK/2BHK/Villa/etc.), the locality, furnishing status, society amenities, etc. In the same way, the pay scale for Software Testing domain (in fact for any technology) varies depending on multiple factors.