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.
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.
Appium is an open source, cross-platform Test automation tool for native, hybrid and mobile web apps, tested on simulators (iOS, FirefoxOS), emulators (Android), and real devices (iOS, Android, FirefoxOS). Appium drives various native automation frameworks and provides an API based on Selenium’s WebDriver JSON wire protocol. Android support uses the UiAutomator framework for newer platforms and Selendroid for older Android platforms.
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.
Recently I am observing a rise of API Testing in the Job descriptions. I once did Web Services testing using SOAP UI testing tool, i.e. verifying the XML request-response. Thought it would be a good time to refresh the concepts. Anyways it was on my list since I started STS. When we look at the Software Testing trends, API testing is rising in priority & relevance. Let’s deep dive into the world of API Testing…