Automation is everywhere. Automation experts are in high demand. Nah! Not in high demand, ONLY Automation Engineers are in demand. All job descriptions mention a set of automation tools and frameworks. Interviews revolve around Java, Python, C#, Selenium, UFT, Appium, Frameworks, Algorithms, and what not. Literally ‘Everybody’ is looking for an Automation engineer.
Cut the crap! Whatever be the debate but still Manual testers are finding it hard to stay relevant in today’s job market. Why? A simple argument – ‘Manual Testing’ & ‘Manual Testers’ are two separate entities. Agree that ‘Manual Testing is NOT dead’, and it never will. But what about Manual Testers?
Recently I saw a Job description with title ‘Lead QA Developer’. In my view this is the perfect depiction of today’s changing QA landscape where a Tester is expected to – Lead, i.e. planning, strategy, team management and reporting – Quality Assurance, i.e. Test methodology, process, defects management, agile, requirements analysis, test techniques, etc. and – Developer, i.e. hands-on knowledge of programming languages like Java, Python, C#, etc. to build automation frameworks and tools for validation.
Current competencies are important, but we need to have a long-term vision. It’s important to be aware of the IT industry trends. The industry will change. Choice is yours – up-skill now (relatively easy) OR up-skill when you get stuck (it’s hard, believe me).
Automation is mostly employed for regression, i.e. to gauge the impact of changes on ‘already-working’ functionality. The same Manual test cases are automated and executed. Automation is for confirmation. What if you want to find issues/defects? Yeah! Manual testing is the first approach. After all, end-user is not a scripted machine. Simulating end-user behavior, testers explore the application with some alternate flows & on-the-fly data.
Defect tracking is a testing-critical strategy that QA engineers utilize to understand the loopholes in the product’s quality and what further improvements it requires to reach the desired results. Software testing has to be intuitive and vast, and thus it has to be logical and yields measureable results. That’s the reason why the success of SDLC greatly depends on accurate bug tracking. In this domain, a fine defect tracking tool is crucial in software testing activities to streamline bug reporting, while accelerating delivery silos.
As soon as you write Selenium Automation in your resume, interviewer is bound to give you a sheet of paper & ask write a Java program. Though Selenium doesn’t require extensive Java knowledge but still there is a set of basic Java programs that you should be able to write on-the-spot. Continuing on our Java interview series for Selenium Automation, this article covers five of the common Java Sort programs frequently asked in the basic technical interview. The questions are easy, but don’t forget to mark these java programs in your to do list before attending any entry-level technical interview for Selenium automation testing.
Formerly known as HP QuickTest Professional (QTP), Unified Functional Testing (UFT) provides functional and regression test automation. It uses the Visual Basic Scripting Edition (VBScript) as its scripting language. UFT automates testing through an intuitive, visual user experience that ties manual, automated, and framework-based testing together in one IDE. This article is to introduce few basic concepts of UFT Automation.
Exploratory Testing has gained popularity in past few years. There are several studies and has also received much of professional attention from the industry. Exploratory Testing gives power to the tester together with responsibility; it offers great freedom and opportunity to the tester for exploring and identifying areas for improvement. But why do we need exploratory testing if we’re already doing a good level of scripted testing? We’re writing test scenarios in each story, running them on different builds until they all pass, and we’re also running them in regression to make doubly sure that the product is still working. Sound good and thorough – what’s the point in doing more software testing on top of that? Well, there are a few good reasons to do exploratory testing in addition to the regular, scripted testing. It exposes the underlying issues within your product, app or website and allows testers to literally explore the functionality.
FinTech, a buzzword today. Though it has been around from the start of 21st century, recently it has gained unprecedented momentum. Why? Due to the emerging disruptive technologies. But what exactly is FinTech? And how it should be perceived as a Tester? What’s the role of a FinTech Tester? What’s the scope of FinTech Testing? These are some of the doubts testers working in the Finance domain come across daily. This article tries to answer these questions in simple terms. The Finance. The Technology. What’s FinTech? The role of a FinTech QA. And its scope. Let’s deep dive…
Yeah! A thought that crosses every tester’s mind who is searching for a better QA opportunity. Why am I not getting selected? Simple! Because you were not the best fit. Best fit in terms of technology, experience, salary, attitude, skills, behavior, etc. Only QA knowledge is not enough to land you a job. Yes, companies look for the ‘Best Fit’ among the available candidates. Some look for tech-savvy candidates, other focus more on the learning attitude. Every company has its own set of guidelines – what we call as company culture. With this article, I try to elaborate on some of the perspectives around Software Testing interview. It has helped me, and I hope this helps fellow testers as well in their quest for the next dream job.
The Software testing community experienced an exciting year of 2017 with many trends taking shape. Applications of artificial intelligence (AI) and automation, continuing trend in adoption of DevOps, increasing test automation, shortening release schedules, and the lack of time for testing. The prevailing state of software testing is getting more challenging with every day passing. With the huge demand for high-quality products within a short time span, the role of testing has grown beyond just another process. Not a single software product could be released without its quality testing and bug fixing. The Software testing industry is always evolving and transforming to new horizons that’s why it’s better to forecast and predict such trends ahead of everyone. This article makes bold predictions for Software Testing trends of 2018.
Sometimes systems crush. And when they crush, they become headline news. The past few years have seen a sharp increase in the number and severity of software glitches at major companies. These newsworthy software “fails” have a negative impact on customer satisfaction & public reputation. The aftermath of each new failure is frequently projected across the internet, and can follow businesses around for years. The results of a phenomenally simple software error can affect the life of millions of people in the most negative way. Let’s take a look at some of the top Software glitches of 2017 to serve as a reminder of just how important Software testing is.
Any technology or tool is worthless unless it is being used by ‘some’ organization somewhere. It all starts from organizations adopting the new technology or a tool and then it gets popular slowly. In that sense QA Job Descriptions are a great source of current technology, i.e. practical tech. being used by IT organizations. Be it Selenium, Protractor, Appium, API tools, Big Data Testing, etc. Everything is embedded in the QA Job descriptions, you just need to mine some data 😉 But don’t worry. Continuing on our “JD Talks” series – we mine hundreds of QA Job descriptions to come up with latest tools, technology, languages and concepts. Let’s see what the second set of JDs talk about…