Everything has a lifecycle – it’s the law of nature, a series of changes in form that an organism undergoes, returning to the starting state. Birth >> Infancy >> Childhood >> Teenage >> Adult >> Mature >> Old age >> Dead end. A ‘Defect’ in Software Testing also follows a pre-defined stage transitions from its identification till its closure. In Software Testing terms, we call it as ‘Defect Status transition’ or a ‘Defect Lifecycle’!
What are the pre-requisites to writing automation scripts in Selenium? Obviously, you need the tools first. Additionally you need to finalize the programming language you will be using to write test scripts and install the associated IDE. As ‘Java’ is the most popular & widely used programming language across the world (both for development & automation testing) – we will be focusing on writing scripts in Java using Selenium. For that first you need to have the ‘Java Development Kit’, Eclipse IDE and Selenium WebDriver. Let’s start with installing ‘Java Development Kit’, popularly known as JDK.
Why was this not tested? Aaah! QAs were accustomed to testing Apps only on a selection of devices, but carriers required more money for procurement. OMG! Mobile Testing is completely different compared to Desktop Testing. If we understand the distinction and challenges of testing Mobile Apps, it will be a bit easier to tackle.
Independence & Freedom – everybody likes it. Wants it. Fights for it. And finally celebrates it. It gives you the objectivity to express your views & opinions. It is essential for a thriving society where the mind is without fear & the head is held high. As India celebrates its ‘Independence Day’ on August 15th, let’s see what it means for a Test team.
The world is driven by beliefs. It may be in God or Technology. Over a period of time every society lay down a set of philosophies or values for better organization & operation. Similarly, any technology has its own fundamental principles which have been proven right as the time elapsed. ‘Software Testing’ is no different – it also has a set of 7 fundamental principles that are proven right over the time.
Will you start testing in parallel with development or only after the development is completed? What about testing at the code-level? i.e. code reviews to ensure best practices are followed. Will it only be reviews or will you actually run the application to identify defects? How about utilizing some automation tool to ease the process? Or will it be hybrid?
Agree or not, once in a while every one of us enjoy criticizing something – a person or a situation. A conflict between a developer & a tester is not new – it has been there since the inception of Software Testing. After all, nobody likes it when their mistakes are pinpointed & written on the wall. What they don’t understand is – it’s not about ‘You’, it’s about the ‘Software’!
Without wasting any space, getting straight to our Manual Testing Interview Questions & Answers Series’ – Part I. Q1. What is Software Testing? Say you want to transfer 10K INR to your friend via Net banking. You make the transaction & inform your friend. But when you check your SMS, it says 11K INR has […]
What’s your strategy & approach to career development? Already planned it? Or still planning? You can surely utilize some industry-proven techniques, right? Similarly ‘Software Testing’ is also a process which involves strategy, approach, proper planning & using the best techniques. But before jumping on to these terminologies, first & foremost – Test Strategy & Test Plan are actual documents whereas Test Approach & Test Technique are conceptual. Test Strategy document will include your project’s particular Test Approach, apart from other details.
Let’s take a simple example to understand what is Test Automation Framework. How do you think Indian Democracy, the second largest in the world, is functioning? Is it ad-hoc? Nah! There are basic processes and structures that drive Indian democracy – The constitution of India. What if Constitution wasn’t there? What if people weren’t driven by any guidelines? Yeah! Total Chaos.
This topic may seem simple to many, but despite of hundreds of web articles – Smoke, Sanity, Retesting & Regression are the most misunderstood topics in Software Testing. There is enormous amount of literature on the subject, but most of them are confusing. The following article makes an attempt to address the confusion. Before understanding these terminologies, first & foremost you need to understand the concept of Software Build.
How do you ensure test coverage? – One of the most common interview question. After all, client doesn’t want anything skipped in testing & then face the embarrassment of end-user failure in live application. What’s the basis for the Test coverage? Yeah! Requirements – functional, technical & non-functional – every single requirement needs to be tested. What if by mistake the Test team over-looked one of the requirement & didn’t write test cases for it? How will a Test Manager or Client come to know about it? ‘Requirement Traceability Matrix’!
First of all, the question ‘What’s the average salary of Software Test Engineer’ is like asking ‘What’s the average house rent in Bengaluru, India?’ You tell me…Can’t? Yeah! You need some more filters to arrive at the rent – the house type (whether it’s a 1BHK/2BHK/Villa/etc.), the locality, furnishing status, society amenities, etc. In the same way, the pay scale for Software Testing domain (in fact for any technology) varies depending on multiple factors.
‘Methodology’ – means the same in Software Engineering as in English, a procedure. Yeah! You might be wondering then what’s all the fuss about it. Why so confusion. I too feel the same way. It’s just that too many methodologies have evolved since the inception of Software development & testing – different procedures applied to structure, plan & control the process (i.e. inception, requirement gathering, design, coding, testing & go-live).