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.
Exploratory testing, is all about discovery, investigation and learning. It’s like Machine learning, in concept. It empathizes on learning and adaptability. While the software is being tested, the tester learns things that together with experience and creativity generates new good tests to run. It emphasizes on personal freedom and responsibility of the individual tester. Exploratory testing is done without any specific plans and schedules. Test cases are not created in advance but testers check system on the fly. They may note down ideas about what to test before test execution. The focus of exploratory testing is more on testing as a “thinking” activity.
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.
This is one of the most common questions discussed among the Agile Community – What happens with the undone User Story of Current Sprint? Why does this happen? How should you deal with the undone user story? What should become of such stories? What should be done with the product backlog item itself? Should be it split or should it be carried into the next sprint? Should the team receive any velocity “credit” for completing a portion of the story? And how do you prevent it from happening again? This article addresses all of these questions.
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.
While writing this article, I am worried & concerned. Not about this article, nah! But about the future of Software Testing and Software Testers in particular. Recently during an interview drive, I came across a bunch of (yes, maximum of them) so-called Software testers who don’t even know the basics of Software Testing. Leave alone the required practical experience. It felt sad that testers don’t even know the basic QA terminologies, didn’t understand its importance, take it too lightly as a career, are not willing to learn, etc. At one end industry is moving towards Automated QA and on the other hand here we are with a bunch of novice testers for whom even the foundations are shaky.
Knowledge about fundamental Testing concepts is necessary to crack an interview. But now-a-days only knowledge is not enough. Interviews are not just about the theory anymore. Every interviewer is looking for candidates who have practical exposure to different kind of situations and is able to handle them effectively. Most of the companies will have it as one of their selection criteria. And yes, it doesn’t depend on the technology. For every technology there will be situations that an experienced professional knows how to tackle. In this article, we will look at some of the situational FAQ commonly asked in a testing interview. But we will need your help here. It is just a beginning, please comment any situational question that you might have faced in a recent or any past interview. This would help us to collate an informative list for the Testing community.
Definition of done is one of the Agile fundamental things. Yet many teams do not see its importance or are unsure what Definition of Done actually is. The term is also often confused with the acceptance criteria, leading to mis-communications and false expectations. So, let’s have a look at this important agile concept – the definition of done.
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 plays a vital role in the success or failure of any software automation project. For testers – it forms the foundation to a successful career. Software Testing involves multiple components like application-under-test, test cases, test data, test environment, etc. and a good automation framework needs to take care of all of these. In our pursuit to explore the topic of automation frameworks, let’s get started with collating different aspects of software testing that are to be taken care when designing a Test automation framework.
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!