a guideline to new test engineers

i am working in qa as a test enginneer for around 1 yr. when i have joined in test team i was alone in the team. so that time i am kind of lost. where i have to start ??

i have browsed lot of sites and lot of articles to know how to test? to know what is the characteristics of test engineers? to know which software to use for test automation?

we are following scrum so its hard for me to find out the perfect test automation tools for us. i have tried lot of test tools. but i didn't like any one of them, because some of them have limitations and didn't meet up my requirements.

suddenly our head of rnd (hasan bhai) told me about selenium and told me to try it out.

so i have downloaded it and tried it out. i just loved it with its first look. it looks so simple and so smart.

The major things that stuck me most of the time is ajax requests. and those software tools don't know how to handle it and goes to the next command and fails. i was stuck in selenium too, but then i have read some article and find out the "pause" function. which helps me to handle the ajax.

now i will come to the major part of this post:

which software is best for you if you are new in test team ?

when i have asked this question to some of the test engineers they just say its upto you to choose there is lot, and that it upto your requirement.

but i have to say its upto you for sure but i can give you a guideline to help you out to find a good tools for you.

the good thing in tools is, it help you to find out broken parts that passed before but not the new bugs that came out for any new builds.

so which tools??

i have to say because you are new in test or you just wanna start as a test engineer then try out the selenium IDE. it is simple to install, simple to record and easy to run.


but i have to tell you again test automation is not a solution to find out bugs. it only helps you to find out the broken parts based on a fixed scenario.

here is those links of different selenium tools.

• selenium IDE
• selenium RC
• selenium Grid

next post i will let you know about the good and bad about selenium.

facebook bug has been found again.

today suddenly i think of to login in facebook with my changed email address and suddenly i saw that i can login with the old email address even it is removed from my account.

ok now straight on the bug producing steps:

1. login with your email and password
2. go to settings
   
3. click on in section (fig: 1)
4. then write new mail address and click
   
5. it will send you a email to the new email address
   
6. click on the verify link on just now added mail address.
   
7. remove old email address. (fig: 2)
   
8. now you also can login with your new & old email address.
   

fig: 1
fig: 2

it may be seems that it is not a bug but when user change his/her email, it means there is some problem with that email thats why user change that. so i think that is a security problem of facebook.

testing expericence magazine issue

just found it in linkedin. its a magazine for professional testers. so i think to share it with all. that will help all the testers and developer. just download and read it. i hope that will help all developers and testers.

you can download it from the link below:
http://www.testingexperience.com/testingexperience01_09.pdf

what keeps me away from thinking

this is my first post in blogspot and today it just came in my mind wht keeps me away from thinking and what is blocking me.

first of all i just want to say that our company is following scrum for our development and i am in qa team as a test engineer

i think there will be some points from my view:

1. there are lot of completed tasks and the dead line is near.

2. lot of small bugs into the system that haven't been fixed yet which keeps coming infront.

3. sometime some one walked into and complain about bugs while i am in the middle of some other bugs.

4. concurrently i need to do report to our bug reporting system that takes a little time.

5. i am tesing lot of services which is depends on each other.

but i think most of the time number one is the most priority what is actually blocking me.

i think if we can do little more orginize ourself in development and also in testing like. following time and deadline, rather then walking in people do reporting in trac that will help us all.