Thursday, March 6, 2014

Test Cases for Sign in and Sign up.

1. Username
a. Requirements Check
- Check with requirements if special character could be used for username else Special character keys in textfield should be disabled i.e. if user taps on any special character key in keyboard no operation should be performed (dead key). If special character keys are not disabled then "Special characters are not allowed" alert message has to be displayed when used as username.
- Check with requirement for minimum number of characters allowed for username. If user enters less than the minimum number of character then proper alert message has to be displayed.
- Check if username is case sensitive or case insensitive. If its case sensitive then if 1 person has a username 'Christ' then if another person signs up using 'cHrist', alert message has to be displayed.
- Check with requirements if 'space' could be used for username. 

b. Test cases 
- Use username which already exists.
- Don't enter any character in username field.
- Use other language character such as Arabic or Chinese.
- Use hidden special characters. 
Ex : If u tap and hold character L in keyboard you would get a special character. If special characters are disabled as per requirements then developers should make sure to disable hidden special characters also. Try experimenting with different hidden keys :)
- Test for Case sensitive
- Use less than minimum number of character.
- Use more than maximum number of characters.
- Use space key in-between letters
- Copy paste a special character from Note or Safari.
- Finally a positive test case use correct username :)

2. Password 
a. Requirements Check.
- Check with the requirements for minimum character and maximum character which could be used for password field. Mostly it would be 6 for min and 32 for maximum. 
- Password field should be shown in Asterisk (****) as you type.  

b. Test Cases
- Use less than minimum number of character.
- Use more than maximum number of characters.
- Copy text to password field (Shouldn't work) 
- Use special characters, numbers and letters.

3. Email Address
a. Requirements 
- Check with minimum and maximum number of characters which could be used for email address.
- Only letters numbers period and underscore should be allowed for Sign up. Its better for developers to disable rest all keys in keyboard.
- Email Address should always start with letter.

b. Test Cases
- Use special character like @! as email address.
- Use wrong email address.
- Use valid Email Address

4. Others 
- Forgot password feature should be used. If customer has not asked for it, insist customer to have this feature.
- Clear button should be present so as the user could clear the textfield by tapping clear button.
- It better to disable Copy and Paste option in textfield.
- Its better to have remember me check box so that it would remember the email address.
- Sign in / Sign up button should be enabled only if all textfield are filed. If requirements is such that all button should be enabled then if user taps on Sign in / Sign up button proper alert message has to be displayed.
- Appropriate alert message has to be  displayed if any error is found. Each error should have a separate alert message. 

Thursday, February 27, 2014

5 reasons why a developer cannot test his own application better than a tester!

1. Attachment with source code
- As everyone know developers are emotionally attached to their code which makes them not to test like a tester. "A developer would never degrade his own baby" :P Its just like how we tester are emotionally attached to a bug. Don't we get angry when a developer counters us telling that the bug reported is never a bug? :D

2. Concentrates only on positive cases 
- Most developers would normally think only about positive and straight forward scenarios whereas testers mentality would be always in breaking the code and concentrating more on negative test cases.

3. Lack of End user experience
- Testers would normally check many applications & game and would exactly know what is required, as they would have already experienced checking similar kind of application whereas most developers wouldn't ( If a developer is reading this he would surely crib about not having time to check other applications Gotcha! )

4. Not much exposure to bugs: 
- A tester would have experience in testing many application and would know when a code could break whereas a developer wouldn't have much exposure to bug which make a developer fail in testing.

5. Tight schedule: 
- Most companies wouldn't give sufficient time to developers which leads them to not test the whole application.

So what do you think can a developer test his own application better than a tester ?

Monday, February 17, 2014

Myths of Game testing.

1) You just play around, nothing technical!
Fact: While testing games, it is important to know what logic the developer has used which in turn helps you to find an unusual sequence.

2) You get to play games before it is released!
Fact: Its true that you get to play it before release but the amount of time spent to test the game really makes you sick about the game and sometimes even to hate the game

3) You have lot of fun while testing!
Fact: Though you would feel good about it initially but, would you have fun circling round a same F1 circuit for 100 times! No right!

4) You get paid for playing games!
Fact: You spend most of the time creating test documents, logging defects, regressing defects, testing with localization, testing in different devices.. the list will go on!

5) You can change whatever you want in game!
Fact: This is not true at all! Even if you feel that certain features are required for easy gameplay your ideas would either be rejected by development team because of time constraint or by customer if he feels it is not so cool!

Thursday, February 13, 2014

What do we normally do when we are free from work!

1. Check social networking sites
2. Window shop in online stores
3. Watch videos in Youtube
4. Read some technical blog for about 2 minutes and then again stick to point number 1 2 and 3
5. Read 2 pages of C / C++ / Java
6. Forward mails
7. Check if any new girl has joined in internal website
8. Stare at the monitor
9. Read some cricket / football news
10. Read political news
11. Tweet the news
13. Disturb a developer / designer
14. Search for a device to play games
15. Wander around to see if anyone is free as you.
16. Point out some mistake in some other project.
17. Chat with a girl in the wing
18. Create some funny face in Photo booth
19. Plan 4 weekend trip
20. WIKIPEDIA

So what do you do when u r free from work ??? 

P.S

I just forgot to add point number 12 :P If you dint figure this out, you really need to concentrate while reading my blog :D

Thursday, February 6, 2014

How to enjoy testing and give a defect free product.

Recently our team figured out that we are able to produce more and more bugs and simultaneously enjoy what we do. Here you go!
We started to have competition on who would log most number of valid defects. Initially my teammates were really uncomfortable to log very minor defects. But i constantly told my teammates, even though the defects are small, these are the defects which would be found by producers and customers and we are blamed for not finding those defects. So as we started competing against each other, we had a quality product where we were damn confident the not even a minor glitch was left behind and simultaneously we enjoyed testing due to this competitive behavior. Recently we were assigned to individual project where 1 QC was assigned to test the 1 application but even after that we used to compare our defect count and try to find more defect.
So what do you think about this idea ?

P.S
This post was written in 2011.