Software Testing is a process of verifying and validating an application against the specified requirements, mostly functional requirements. The non-functional aspects of an application such as performance are considered only after functional. Testing a software for both functionality and performance becomes a value addition to its quality before its launch into the market.
Recently a lot has been written & talked about the future of Manual Testing. Manual Testing is indispensable part of ensuring a high quality software. On the other hand, Automation Tests help you cut down the release cycle time. But usability & human behavior cannot be automated. With reduced time-to-market there is an added pressure on enterprises to seek automation alternatives. With the rise & growth of new technologies, people are more interested in scripting. But Manual Testing is the input to Automation scripts. Unless AI technology matches a human brain, Manual tests are best kept ‘manual’. You cannot automate everything. Cut the crap! Whatever be the debate but still Manual testers are finding it hard to stay relevant in today’s job market. Why?
I have a strong functional test experience but no automation. I ‘know’ automation testing but don’t have the project experience. I am a Test lead but didn’t write any automation scripts. Analytical & logical but never did project coding. Found in-numerous bugs but didn’t prepare automation reports. Managed a big team but didn’t learn performance testing. Documented every report but didn’t produce framework guides. Enjoyed exploratory tests but didn’t script pre-defined test cases. Helped BAs and even developers (in debugging) but never developed automation framework. Understood domain & application flows but didn’t write code. Open to learning but no opportunity. Self-learned programming & tools, but didn’t get practical project experience. Passionate about Software testing but now it’s Software Developer in Test.
The goal of every IT organization is to deliver a quality software to their clientele, and to complement their goal they give the highest priority to Software Testing. Automation testing acts as an accelerator to their time to market by saving time and effort, and manual testing will remain as the core for quality software delivery. In today’s changing technology landscape, Manual testers are being pushed to learn automation skills. But how? How to empower Manual Testers to do Automation Testing?
In an agile business, automation is becoming an essential process. Companies are now taking advantage of automation testing tools to increase their efficiency and productivity. Automation is frequently evangelized as the cure-all of software quality woes. Some of the benefits that accrue from automated tests include test reusability, repeatability and coverage besides the savings on effort, time and cost it takes for execution (compared to manual testing). However it’s NOT the answer for everything. Test automation, while being able to improve numerous aspects of software development, has limitations that developers and quality assurance teams should be aware of from the start. Understanding these limitations of automation testing will help us devise an efficient & effective automation strategy.
‘Mobile App’ is the new buzzword. Then how can one stick to the traditional Test Plan template? The purpose of the Mobile App Test Plan is to define how the testing effort for the App release is planned, executed, and controlled. It is critical to have a rigorous Mobile App Test Plan before the App is deployed. The idea is simple, focus on the value it offers – boil Test planning down to only the essentials and cut all fat and fluff. Test Plan shouldn’t be like any other dead document (resulting in wasted effort) – written, reviewed, referred to a few times and then cast aside as the project moves ahead. A comprehensive Plan gives customers the confidence that an efficient Test process is adopted to ensure optimum App Quality! Let’s have a look…
While scripting you might encounter a scenario which requires the automation script to download a file with Selenium Webdriver (say MS Excel, MS Word, Zip file, PDF, CSV, Text file) from web application. What happens when you click on ‘Download’? Yeah! A pop-up window is displayed asking user to either open, save or ‘save as’ the file. If you have noticed, this is NOT a browser HTML pop-up but Windows OS pop-up. And Selenium Webdriver is a ‘Web Browser’ automation tool, i.e. it works only in the browser. We cannot access operating system’s native windows with Selenium Webdriver. Ooops! A blocker! Does this mean we cannot automate the File download scenario? Nah! It simply means we need to find a workaround 😉 In this article let’s explore how to download a file with Selenium Webdriver using Firefox Profile.
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.
There is no such statement as ‘I am now prepared for the interview‘. When facing a Testing interview no matter how many interview questions and answers you have gone through – there is always more to read 🙂 Continuing on our Testing Interview questions series, let’s see some more interesting FAQs…
After successfully running several automation scripts now we are stepping towards grasping the essential ‘Get’ commands in Selenium. We will precisely and briefly discuss each of these Selenium commands so as to make you capable of using them effectively whenever required. Thus we are going to discuss about various driver.get in Selenium WebDriver that we would be using in our day to day automation testing. driver.get in Selenium WebDriver are used to collect various information about the page that we deal with. Here are some important “get” commands you must be familiar with,
If you are somewhat familiar with Selenium automation, you would know the importance of XPath. For those who are just starting with Selenium – XPath is one of the most popular element locator technique in Selenium along with CSS selector, i.e. mastering XPath or CSS is essential for the Selenium test automation. Yeah! You can extract the XPaths from Firepath-like tools but these cannot be used directly for dynamic web elements. And we think getting the basics is a must >> Tools can be used afterwards. This article is an introduction to XPath along with some XPath examples.
Web page uses HTML Document Object Model. XPath is used to navigate & locate elements in an XML. So how are XPath examples relevant for a web page?
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.
Every automation tool just provides a way to navigate >> identify >> perform >> repeat. So before moving further on our Selenium series, let’s look at the most common Page elements & User actions to automate.
How does automation script identify different elements on an application page? We call it Element Locators in Selenium Webdriver – The Eyes (Senses)!