Answer:

Consider:

Positive

Negative

Boundary

Usability

Performance


32. How would you test a mobile application manually?

Answer:

I would consider:

Great interview addition:

“I would also test behavior during network transitions such as Wi-Fi to mobile data.”


33. How do you decide what test cases to execute first?

Answer:

I prioritize based on:

  1. Business criticality
  2. User impact
  3. Recent code changes
  4. Defect history
  5. Complexity
  6. Integration points
  7. Risk

This is better than saying:

“I always execute test cases in the order they are written.”


34. What is Boundary Value Analysis?

Answer:

Boundary Value Analysis focuses on values at the edges of an input range.

Suppose the allowed age is:

18–60

Important values could include:

17, 18, 19, 59, 60, 61

Why?

Defects frequently occur around boundaries.


35. What is Equivalence Partitioning?

Answer:

It divides input data into groups that are expected to behave similarly.

Suppose age must be:

18–60

Partitions could be:

Instead of testing every possible age, representative values can be selected from each partition.


36. What is Decision Table Testing?

Answer:

Decision tables are useful when application behavior depends on multiple conditions.

Example:

For a loan application:

IncomeCredit ScoreExpected
HighGoodApprove
HighPoorReview/Reject
LowGoodReview
LowPoorReject

This technique helps ensure combinations of conditions are covered.


37. What is State Transition Testing?

Answer:

It tests how an application behaves when moving from one state to another.

Example:

An online order may move through:

Placed → Confirmed → Shipped → Delivered

You should test:

For example:

Can a delivered order be moved back to “Placed”?


38. What is Exploratory Testing?

Answer:

“Exploratory testing is an approach where learning, test design and execution happen together. The tester explores the application based on product knowledge, risks and observations rather than following only predefined test cases.”

Example:

While testing checkout, you might discover unexpected behavior by changing quantities, navigating backward, refreshing the page or switching network conditions.


39. What is Ad-hoc Testing?

Answer:

“Ad-hoc testing is informal testing performed without detailed predefined test cases, usually based on tester intuition and product knowledge.”

Important:

Don’t confuse it completely with exploratory testing.

You can say:

“Exploratory testing is more structured around learning and investigation, whereas ad-hoc testing is generally more informal.”


40. What would you do if you couldn’t reproduce a reported bug?

Answer:

Don’t immediately reject the bug.

Say:

“I would collect more information such as environment, browser/device, user account, test data, timestamps, logs and exact steps. I would also try different environments and conditions. If I still cannot reproduce it, I would document the investigation and collaborate with the reporter or developer before deciding the defect status.”


Pages: 1 2 3 4 5

Leave a Reply

Your email address will not be published. Required fields are marked *