Posted by
Amit Kulkarni [Admin]
| Posted in
feature
,
mobile app testing
,
question
,
testers
| Posted on
2/06/2012 07:45:00 PM
Testers are not just to find bugs to provide a valuable suggestion, or point out a thing which is not a part of the application from the start. I always try to keep these things in mind when I test an application whether it is a web based application or mobile app. The reason for always keeping track of what is changed is helpful to determine to find more loop holes in the application. Sometimes developers just forgot to remove a feature which should not be a part of the overall app, but what if the app shipped and gone live. The user will try to use it and ultimately they will complain. For others, the option would be to just roll back to previous version for stability.
Recently I was testing a mobile app, which I love these
days. So, I sort of keep track of before updating to the latest build in order
to have good interactive experience. I found out that there is a feature which should not be a part of the
app, now this is just come from intuition as I could not find any mention of the same in requirements, where
it is mentioned that this feature will be a part of the app in this build. So
the first question? Is it worth to test then? But what if it not mentioned
explicitly but as a tester I need to make sure that I test it so that I could
cover up things which are not written in the requirements, as James Bach would call it
as an unwritten requirements.
It turned out that I
will test it, and at the same time question the developer whether this is a
part of the app, as the app supposed to make its way to store in few weeks. So,
if the developer has failed to catch this, as a tester this is my responsibility
to make sure that I am on a right way by letting them know that what I have
seen. Though I decided NOT to focus too much on the feature at this moment, as
first I need to cover up other parts of the app, and as the feature itself is
new in app, so it is kind of first understand about it, and then come up with
ideas. So, after exploring other part of the application and raising some
issues, I decided to move on to the new feature. I checked the help section of
the app, so somewhat sure that either this has been incorporated by mistake, or
there is no update on this in help section. I used my previous experience, and
found out what the feature is all about. The feature pretty much causing issues
with other parts of the application, so I thought of spending not much time on it before I get to hear from the developer.
I got to know from the developer pretty soon that the feature is incorporated by mistake and should not be there. I am glad that I did not spend too much time on testing that feature as that would have not given sufficient amount of time for me to test other parts of the app.
The takeaway over here for testers is to keep eyes open and find out for such anomalies first and raise your hand for questions!
I got to know from the developer pretty soon that the feature is incorporated by mistake and should not be there. I am glad that I did not spend too much time on testing that feature as that would have not given sufficient amount of time for me to test other parts of the app.
The takeaway over here for testers is to keep eyes open and find out for such anomalies first and raise your hand for questions!
Br.,
Amit
Started writing this blog on 02/06/2012 at 07:05 PM IST and completed the blog at 07:44 PM IST
Amit
Started writing this blog on 02/06/2012 at 07:05 PM IST and completed the blog at 07:44 PM IST
Comments (0)
Post a Comment