The most important yet confused concept – Defect Severity and Priority. Additionally it is one of the most popular Software Testing interview question.
Regression testing, one of the most important yet neglected Testing type. Why? Because we are bored of it. Why bored? Because we do it incorrectly or don’t follow the best practices. Most of the time it results into wasted efforts – repeated testing without any qualitative results. Have you ever tried to revamp your regression approach? Or to actually work on the challenges faced?
Manual & Automation Testing Interview series – we don’t segregate questions in categories like Manual Testing, Selenium, Mobile Testing or HPE UFT.
Encountering a gecko driver error as you start scripting for Mozilla Firefox using the latest Selenium 3.0.0 Beta release? Know what has changed now!
Once upon a time we had a finicky client manager with no understanding of testing logic. He just wanted us [a team of 4] to execute thousands of test cases in a week, that too maintaining quality. Is it possible in any real-world? No, right? There was a tiff between the Test Manager and Client Manager and that’s when I got the real-time exposure to Risk-based Testing, a win-win idea!
SDET, expands to Software Development Engineer in Test OR Software Design Engineer in Test. Don’t get confused. In simple terms – the SDET is a tester and also a developer. Haha! Confused? I too felt the same. No one is crystal clear about the SDET role – I guess not even an SDET himself/herself 🙂 a fancy word adopted by Microsoft and every one going Gaga o
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’!
HP UFT provides a COM interface that allows automation of UFT itself. This Automation object model enables user to write code to perform the core UFT tasks.
If you have segments of code that needs to be used several times, you may want to create a function and then call that function from within the main action.
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?