Sunday 10 February 2013

What are the common problems/challenges testers face?

eeing tester i was facing lots of problems in my initial carrier,few people was asking me about my intrest i was little bit confuse but have only answer for this question was need develop the intrest. after some time i was realise that what is the different between need and intrest.I had joined one of the gaming company as a tester,but i am telling u i was not intrested in gaming,i always prefer outdoor games like football,cricket etc...

When i joined my first company i had an idea about gaming but not about game testing.but my friends was working in gaming domain so i was updated,one month just i was reading bugs in a bugtrackingtool and read docs in google.it was a small company and the size of team is 10 member.
After one month team lead had given one game to test in j2me device.j2me devices was very popular.so mostly companies was doing porting.already application was tesed with sr tester.i just review the previous bugs behalf of bugs i had written some bugs.from begning mobile gaming companies are practicing agile method.there is no documantation only utc criteria is given by NSTL and for CDMA brew is given by TBT.with the help of this docs we performed.Sometimes we were not able to decide its a bug or functionality.That is really chalanging task some times tester gave a game concept.

sprint time is very less with in 2 to 3 months companies promise to deleaver the game so so many round of testing and porting we have to do.so in a short time span we can not able to create a req docs,test plan,test case,smoke test case.once concept is ready do coding test properlly and release.

In a gaming or application environment three things are imp Globalization,UI,functionality.globlization covers help and menu text.UI covers images and animation,functionality covers key handling as well as LSK and RSK.
Some times developer and tester will fight on sevirity and prority given by the tester.be very concious while writting severity because some times it hurt the developer then he will not give u a any response.
so if u are not aware about better u will consult with the developer.
Some times tester will write a bug but developer will "write not a bug" please tell to write a reasion before closing the bug,behalf of developer comment close the bug. before giving the severity staus tester should know
Who uses the product and under what circumstances?
What are the different flows a user can work with the product?
How knowledgeable are the users in order to find workarounds to specific bugs?


Rejected Many companies use a REJECTED status that gives developers a way to request more information about the issues.don't be panic because of his lazyness developer is unable to reproduce.
What information are you looking to get from your defects?
Bug tittle
step to reproduce
Simple discription
severity and other as per bug tracking tools available in amarket.
Few things are imp while starting the testing product
Does the product recognize if some necessary component is missing or insufficient?
Effective analysis of the real business needs and identification of requirements that truly meet those needs
Does bug tracking option is cover all aspect?
Does resource are available to test the build?
Does tranning required?
does Hardware Compatibility is available?
does Exit criteria is defined?
Time management is also imp factor in agile env..

one most imp thing update your manager regarding project progress.So he can able to track the progress.
Lack of documantation
Even tester and developer both will suffer without project related docs so better make a genaral test case add and delete as per requirement and placed in a centre so people can see and review the docs.

better u will create a acceptance test createria before launch app on development server.or make a check list go nogo build.once it will pass then launch the app on development server.

No comments:

Post a Comment

Related Posts Plugin for WordPress, Blogger...