Though the aspiration for being a successful IT professional is strong, we assume that the word ‘IT professional’ is synonymous with ‘Developer’. When a testing opportunity presents itself, there are many doubts in our minds and we often wonder if it’s the right career move or not. While being a developer is great and has immense potential, it should not be concluded that being a tester means the exact opposite. Let’s explore the reasons behind the perception – Software Testing is inferior to Development,
Steve Jobs. J.K. Rowling. Walt Disney. Oprah. What do all these famous people have in common? They’ve all been fired. If you’re currently staring at your own pink slip – or anticipating one in the near future – you can take a tiny bit of comfort in knowing that you’re in illustrious company. In today’s tough economic times it’s inevitable that the season of joy and mirth brings news like this. Whatever the reason, getting fired sucks, big time. It can be one of life’s most stressful experiences, your feelings of self-worth and self-esteem are dealt a blow. The first reactions to getting fired are usually anger and pain, followed by feelings of confusion and disillusionment. It’s like getting dumped in a relationship, except you lose your paycheck too. However the good news is that losing a job is not the end of the world and with the right approach and perspective you could turn something bad into something positive. And that means taking a deep breath, getting yourself together, and looking at your situation.
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.
Quality – Why is this word so important for your software? Software teams today involve a number of people: developers, testers, support engineers, designers, product managers, and executive stake holders. A low quality software impacts all of these or in other words everyone in the team is responsible for the quality of software delivered. When we look into the overall effectiveness or cost manual testing still have a pivotal role to play. Unfortunately, very little discussion is only happening on how to improve efficiency of manual testing instead most of discussions are happening on how to increase the level of automation. Many of us would advocate the fact that Manual Testing is no longer needed, and I know it well why they think so. It is mostly because of the drawbacks and challenges associated with Manual Testing.
All across the globe, people are connecting to the Internet to access information, communicate with other people, and do business. But it’s not just people that are using the Internet: objects use it too. IoT. Internet of Things. You’ve heard it at some point. Everyone is talking about it. It’s going to change the world! The Internet of Things (IoT) is becoming an increasing topic of interest among technology giants and business communities. But you might be scratching your head figuring out what it is or what it means?
‘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.
Velocity: “the speed of something in a given direction.” And how do you measure it while driving? How do you know that your average velocity is 80 km per hour if you have traveled 160 kilometers in 2 hours’ time? I.e. kilometers traveled in one hour. The same goes for an agile project. Agile Velocity is an extremely simple, powerful method for accurately measuring the rate at which scrum development teams consistently deliver business value. This article explains the principles behind agile velocity tracking.
Also known as Verification and Validation model, the V Model is an extension of the waterfall model and is based on the association of a testing phase for each corresponding development stage. This means that the V Model demonstrates the relationships between each phase of the development life cycle and its associated phase of testing. There are Verification phases on one side of the ‘V’ and Validation phases on the other side. The Coding Phase joins the two sides of the V-Model. The horizontal and vertical axes represents time or project completeness (left-to-right) and level of abstraction, respectively. This is a highly-disciplined model and the next phase starts only after completion of the previous phase.
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.
Most of us have had an argument with friends or colleagues about which route is fastest from home to office or vice-versa. How’d you settle that bet? Yeah! Test it out. Leave the same place at the exact same time, via separate routes, and find out whose way is the best. Hope you got a brief idea about AB testing 😉 which is used by today’s designers & marketers to gain insight into visitor behavior and to increase conversion rate. Though one of the easiest and most effective technique for optimization, A/B testing is still not as common as Internet marketing subjects as SEO, Web analytics and usability. People just aren’t as aware of it. Let’s explore more about AB Testing.
In software testing, it is most important to measure the quality, cost and effectiveness of the project and the processes. Without measuring these, project can’t be completed successfully. The goal of testing is to determine if the requirements are met. During the course of testing, we find defects, or instances where the software does not meet requirements. Hence, in the area of software testing metrics, there has been abundant work in analyzing defects via different Defect metrics.
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…
As discussed in our earlier article Manual vs. Automation Testing – on a high level there are basically two methods to complete the software verification & validation – Manual and Automation testing. Each testing method has its pros and cons but the truth is that regardless of which side of the fence you sit on (manual vs. automated), the argument is largely irrelevant; to achieve high quality software and reduced time to market both methodologies are essential. Let’s explore the remaining key consideration…