Industry is sure moving to Automated Test execution. But as I say – Automation is confirmatory, Manual tests are more exploratory. Only Automation testing is not enough, so testers need to be good at finding bugs. “Finding Bugs” is one characteristic that differentiates a good tester from a mediocre tester. The basic principle is to combine things that programmers didn’t expect with common failure modes of your platform. Always remember, Testers don’t break the software. It is already broken. You just need to find those broken pieces and help make the software better.
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. Software Testing Studio has started a new series for you – “JD Talks” where we mine hundreds of Job descriptions to come up with latest tools, technology, languages and concepts. Let’s see what the first set of JDs talk about…
In continuation to our previous article introducing ‘Maven Build Tool’, this article describes some of the most common terms encountered while using Maven. These terms, that have an explicit meaning for Maven, can sometimes be confusing for newcomers. As an Automation QA, you should at least be aware of the below 20+ Maven terminologies – commonly asked in a technical interview as well.
Maven. You must have heard or read about this tool in your automation journey. Moving from a beginner to an automation expert requires knowledge of Selenium Tools Galaxy – Webdriver, Log4j, Extent Reports, Apache POI, TestNG, Maven, Jenkins and Cucumber. These tools serve different purpose in the automation galaxy and are a must-know if you really want to excel in your career as a Test Architect. This article is to introduce the ‘Maven’ tool, which is a Yiddish word meaning “accumulator of knowledge”. But what is being accumulated here? The Selenium Automation project’s build components. Let’s kick-off with our Maven understanding…
Selenium Drag and Drop is one of the common scenarios in Automation testing. Let’s say we have a web application where we need to drag an item from one location to another location. These kinds of complex actions are not available in basic element properties. Thankfully Selenium WebDriver has Advanced User Interactions API (Actions class) to perform this kind of advanced user interactions for rich applications.
Interview is the most important part of the employment process. It can make or break an opportunity. When it comes to Software Testing, almost all organizations are now looking for Automation engineers, SDETs, Selenium experts, Automation architects and what not. Since Manual testers are finding it tough to land a high-paying job switch, many have started learning the basics of Selenium automation (Yeah! Selenium is one of the most popular automation tool now-a-days). But interviewers demand practical experience. And interview questions reflect that view – starting from basic theoretical knowledge, slowly the interview will move towards – Explain Test Automation framework for your current project.
There are lot of people who have Manual testing experience. When there is a walk-in interview you could see thousands of people with more experience than you have. So you have to differentiate yourself from others by adding extra skills to your resume. In a world where the consumer expects fast-paced delivery, and solutions must support a myriad of devices and platforms, manual testing simply doesn’t enable the delivery pace that the market expects. The rise of automated testing in response to this has been rapid. Are you attempting a switch from Manual Testing to Test Automation? This transition won’t come overnight. It takes months/years to lay the groundwork.
Agile software testing is the requirement of a modern software development team. Choosing agile testing tools is not an option anymore, it’s a necessity. If you want the end product to be effective, speedy and sustainable simultaneously, you must go with a tool which provides agile testing solutions under a feasible budget.
Agile, Continuous Integration and Continuous Delivery methodologies have evolved in favor of delivering the software faster. Software Test automation blends perfectly with these methodologies for accelerating the time to market. But achieving a flawless test automation is same as preparing a delicious dish where essential ingredients play a vital role in the success.
Tables are one of the primary design tools for HTML documents. Tables allow for greater control over page layout, allowing creation of more visually interesting pages. Table has rows and columns to store the data. I guess 50% IT industry will come to a halt if Microsoft Excel stops working 😉 that’s the importance of tables in organizing data. Search results on many websites are often displayed in the form of table. E.g. try searching for a flight between X and Y on a travel website, what you get is a table of results. There are times when we need to access elements (usually texts) that are within HTML tables. In this article let’s see how to read data from a Web Table using Selenium.
Test Automation Framework, can make testing a lot systematic and increase the chances of your next career switch. We have been discussing what is Test Automation Framework and why do we need it. The goal is the rapid release of efficient, effective and reliable software, and realizing the benefits of automation testing requires adaptable methods and innovative software tools that optimize data. Test automation frameworks guide this convergence of methodology and technology. The framework provides the user with various benefits that helps them to develop, execute and report the automation test scripts efficiently. Moving on in our pursuit to learn more, this article attempts to cover different types of Test Automation frameworks.
Experts and Influencers from the Software Testing industry say that – Software Testing is one such process that has no end and it demands for improvement every now and then. Testing teams strive to deliver a well-tested software that can provide a seamless user experience in terms of functionality, performance and security. The ever-evolving scope of improvement in the Software Testing process to deliver a better-quality software compels to adopt new approaches. Manual Testers are finding it hard to stay relevant in today’s evolving technology landscape.
“How comfortable are you designing an Automation Framework from scratch?” – The very first interview question for a QA/Testing job opportunity now-a-days. What should I say? I am really good at Functional Testing? Nah! There is no space for manual testers. You HAVE TO start learning Automation. And it’s not just about Automation scripting, interviews are more driven towards programming & building an automation framework. So here I am penning down my answers to all those automation interviews in a series of Automation Framework focused blogs. It’s high time, really!
A peculiar but prominent distinction – Technical vs Domain Tester. Yeah! We know both are necessary for a successful QA career, but after certain years of experience your resume tend to incline towards one or the other. We are not Rajinikanth after all Who wins the Technical vs Domain Tester battle? Nah! It’s not a comparison between Deepanshu and Kanchan (we are together after all ;-)) but comparison between two different kinds of resume!