Before continuing on our Software Testing Interview Questions and Answers series, one thing you might have noticed is that we don’t segregate questions and answers in categories like Manual Testing, Selenium, Mobile Testing or HPE UFT. The idea is to keep up with the changing times when the gap between Manual and Automation Testing is blurring, organizations are looking for resources with both Manual and Automation Testing knowledge. Let’s get started…
Software Testing Interview Questions and Answers
You all must have tried moving apps to external storage and noticed that Move to SD Card option might be greyed out for some apps. Ever wondered why some apps can be moved to SD card and some can’t?
- System Apps
- App Developer Choice
- Widget Support
- Syncing, Service, or Account Interface
- Effective & Efficient Apps
Sensor is nothing but a converter that measures a physical quantity and converts it into a signal which can be read by an observer or by an instrument.
- GPS (Global Positioning System)
- The Accelerometer & Gyroscope
- The Proximity
- The Compass or Magnetometer
- The Light sensor
- The Fingerprint
- The Barometer, Thermometer and Pedometer
- The Heart rate sensor
- Back-Illuminated sensor
- Detect Harmful Radiation
If you have segments of code that you need to use several times in your tests, you may want to create a function and then call that function from within the main action. Say you want to display a message box repeatedly >> Just create a function and reuse it every time. By using functions, tests are shorter, easier to design, read and maintain.
On the 3rd day of April 1973, the first mobile phone call was made by Martin Cooper of Motorola to Dr. Joel S. Engel of Bell Labs. That device or instrument weighed 1.1 kg and measuring (23 x 13 x 4.45) cm. Fast forward to today, Mobile communication is so integrated into our lives that many people feel uncomfortable without a cell phone. Once upon a time, the most popular functions of phones were calling and sending texts. Then came the era of “Mobile applications”. Mobile applications date back to the end of the twentieth century. Typically, they were small arcade games, ring tone editors, calculators, calendars, and so forth. The beginning of the new millennium saw a rapid market evolution of mobile content and applications. Let’s go over some of the major ingredients that led to the rise of modern mobile design.
Everything has a life cycle – 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 Life cycle’!
Note: Generally a Defect Management tool (HP ALM, JIRA, Bugzilla, etc.) is used for capturing and maintaining defects throughout their life cycle.
View – the ability to see something or to be seen from a particular perspective. In UFT context, it is the GUI view to facilitate automation scripting.
In laymen terms – Expert View is the editor where you actually write a VB script code, i.e. each line represents a Test Step in VB Script. For e.g.
The Keyword View is comprised of a table-like view where each step is a separate row in the table and each column represents different parts of the steps. You can modify the columns displayed to suit your requirements. When you add or modify a step, you select the test object or other step type you want for your step, select the method operation you want to perform, and define any necessary values for the selected operation or statement. Working in the Keyword View does not require any programming knowledge.
Defect Life cycle varies from organization to organization and is governed by the software testing process the organization or project follows and/or the Defect tracking tool being used. Let’s look at the industry-standard. Please note that the change in status responsibility is mentioned in the brackets.
1. New (Tester >> Lead)
2. Assigned (Test / Development Lead >> Developer)
2.a. Deferred (Team Lead, Business Team)
2.b. Rejected (Test / Development Lead)
3. Open (Developer)
4. Fixed (Developer)
5. Ready for Test (Developer >> Tester)
6. Closed (Tester)
6.a. Reopen (Tester >> Developer)
As they say “The art of life is a constant readjustment to our surroundings.” – being Agile! To stay relevant, you need to readjust. You need to be swift & responsive to the client demands, changing technology and flexible workplace. How? Simple! As in life – Develop >> Review >> Feedback >> Change >> Adjust >> Next development.
What do you think is better? Developing a custom website for Client in 6 months just to know that technology has evolved in the background and now the client wants a Mobile App OR getting a continuous feedback and then readjust the strategy after 2 months to eventually develop a Mobile App in 7 months? Yeah! The choice is simple.
Agility is the ability to adapt and respond to change…Agile organizations view change as an opportunity, not a threat!
Deferred as in delayed or postponed. After initial analysis it is observed that a particular defect will not be fixed as of now, i.e. in this release. It will be fixed in some future release. Therefore, the Lead will change its status to ‘Deferred’ and it will not be picked up as part of this release but some future release. And why do you think a defect will be deferred? There are multiple factors and there can be multiple reasons – very low priority, lack of time, not part of current requirement, technical dependencies, etc. Generally it’s a standard practice to get sign-off from the business team before marking a defect as ‘Deferred’. After all, they know the best about the business impact.
Agile methodology is an alternative to waterfall, or traditional sequential development. “Agile Development” is an umbrella term for several iterative and incremental software development methodologies like Extreme Programming (XP), Scrum, Crystal, Dynamic Systems Development Method (DSDM), Lean Development, and Feature-Driven Development (FDD). While each of the agile methodology is unique in its specific approach, they all share a common vision and core values & principles expressed in the Agile Manifesto.
Agile methodology is described as “iterative” and “incremental” – assess the direction of a project throughout the development lifecycle. This is achieved through regular cadences of work, known as sprints or iterations. Every aspect of development — requirements, design, etc. — is continually revisited throughout the lifecycle. When a team stops, inspect and adapt the direction of a project every two weeks, there’s always time to steer it in another direction. Working software is the primary measure of progress.