In our last post “UFTBasics #6: Object Identification via Mandatory & Assistive properties”, we briefed about how to identify objects in an application using their ‘properties’. The next obvious step is ‘How do you extract the ‘attribute-value’ pair for an object’s properties? This is where “Object Spy” comes to rescue!
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’!
As stated in previous post – Textbox, Button, Image, Checkbox, Dropdown, Hyperlink, etc. – everything which is visible in an application is known as “Object”. Automation is all about identifying these “Objects” in the application and the subsequent “Actions” to-be-performed on it. But the question is – How do you identify different ‘Objects’ in the application via HP UFT?
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).
As you all might know – HP UFT is a commercial (licensed) tool. There are two main types of UFT licenses – Seat and Concurrent.
UFT supports automation for wide range of development environment like Windows (.Net, Java), Web, SAP, Oracle, etc. And this is made possible by the corresponding UFT Add-ins you install. Its like knowing the requirements prior to the start of testing 🙂 Yeah! UFT add-ins are that important, so pay attention.
Looking for Software Testing Interview questions? Let us start with basics…What’s the difference between a defect & a failure? What Test methodology did you follow? Which all methods did you use? You have worked at which all Test levels? How did you organize different Test cycles? Involved in what all Testing types? What about the Test artifacts – did you prepare any? Which technique did you use for Test Design or execution? Confused with these fundamental Software Testing Interview questions?
Software Testing? Can’t you change your technology? Development is much better…A B.Sc. pass can also do Testing, do something good with your engineering degree…Testing is no more a skill set…Anyone can do that…It’s boring…At least learn Automation for survival…There is no career in Software Testing!
To make it right, you first need to identify what’s wrong. And when it’s about finding the wrong in software, we call it “Software Testing”!
Nothing in this world comes for free, except the trial version. Though UFT is commercial, it does not stop us from Learning the basics of automation.