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.

Monday, February 3, 2014

List of Windows phones and Tablets (Nokia Lumia and others)


Serial No.Device Name Operating SystemRAMStorage
1Nokia Lumia 520Microsoft Windows Phone 8 , upgradeable to WP8 Amber512MB8GB
2Nokia Lumia 521Microsoft Windows Phone 8 , upgradeable to WP8 Amber512MB8GB
3Nokia Lumia 525Microsoft Windows Phone 8 Black1GB8GB
4Nokia Lumia 610Windows Phone 7.5256MB8GB
5Nokia Lumia 620Microsoft Windows Phone 8, upgradeable to WP8 Amber512MB8GB
6Nokia Lumia 625Microsoft Windows Phone 8, upgradeable to WP8 Amber512MB8GB
7Nokia Lumia 720Microsoft Windows Phone 8, upgradeable to WP8 Amber512MB8GB
8Nokia Lumia 800Microsoft Windows Phone 7.5 Mango, upgradable to v7.8512MB16GB
9Nokia Lumia 810Microsoft Windows Phone 8, upgradeable to WP8 Amber1GB8GB
10Nokia Lumia 820Microsoft Windows Phone 8, upgradeable to WP8 Amber1GB8GB
11Nokia Lumia 822Microsoft Windows Phone 8, upgradeable to WP8 Amber1GB16GB
12Nokia Lumia 920Microsoft Windows Phone 8, upgradeable to WP8 Amber1GB32GB
13Nokia Lumia 925Microsoft Windows Phone 8, upgradeable to WP8 Amber1GB16GB 32GB
14Nokia Lumia 928Microsoft Windows Phone 8, upgradeable to WP8 Amber1GB32GB
15Nokia Lumia 929Microsoft Windows Phone 8 Black2GB32GB
16Nokia Lumia 1020Microsoft Windows Phone 8, upgradeable to WP8 Black2GB32GB 64GB
17Nokia Lumia 1320Microsoft Windows Phone 8 Black1GB8GB
18Nokia Lumia 1520Microsoft Windows Phone 8 Black2GB32GB
19Huawei Ascend W1Windows Phone 8512MB4GB
20Huawei Ascend W2Windows Phone 8512MB8GB
21Huawei Ascend W3Windows Phone 81GB-
22Samsung ATIV S Windows Phone 81GB16/32GB
23Samsung ATIV S NeoWindows Phone 81GB16GB
24Samsung ATIV Odyssey 1930Windows Phone 81GB8GB
25Samsung ATIV S I8750Windows Phone 81GB16/32GB
26Acer AllegroMicrosoft Windows Phone 7.5 Mango512MB8GB
27Htc 8SMicrosoft Windows Phone 8, upgradeable to WP8 Amber512MB4GB
28Htc 8XMicrosoft Windows Phone 8, upgradeable to WP8 Amber1GB16GB
29Htc 8XTWindows Phone 81024MB8GB
30Htc Windows Phone 8X CDMAMicrosoft Windows Phone 8, upgradeable to WP8 Amber1GB16GB
31Nokia Lumia 2520Windows RT2GB32GB
32Samsung ATIV Tab P8510Windows 82MB16/32GB
33Acer W4-820-Z3742G03aiiWindows Phone 8.12GB32GB
34Acer W4-820-Z3742G06aiiWindows phone 8.1 2GB64GB
35Lenovo IdeaPad Yoga 13Windows 84 to 8GB128 or 226 GB
36Lenovo IdeaPad Yoga 11Windows RT2GB64GB
37Lenovo IdeaPad Yoga 11S UltrabookWindows 8 , Windows 8 ProUpto 8GB DDR3L256 GB SSD HDD
38Lenovo IdeaPad Z500Windows 8 644GB,6GB,8GB(DDR3)HDD: 500GB.1TB
39Lenovo IdeaPad Z580Windows 84GB,6GB,8GB(DDR3)HDD: 500GB.1TB
40Microsoft Surface 2Windows 8.1 pro 64-bit2GB32GB,64GB
41Microsoft SurfaceWindows RT upgradable to Windows RT 8.12GB 32GB,64GB
42Microsoft Surface Pro 2Windows 8.1 pro 64-bit4GB,8GB64Gb,128GB,256GB,512GB
43Lenovo ThinkPad HelixWindows 8 pro ,Windows 88GB DD3128GB,180GB,256GB SSD SATA3
44Lenovo ThinkPad DataSheet Windows 8 pro ,Windows 88GB DD3128GB,180GB,256GB SSD SATA3
45Lenovo LynxWindows 8, Office Home & Student 20132GB DDR2Upto 64GB eMMC

Thursday, January 30, 2014

What a developer/programmer always have to say!

1. Have you installed a proper build!
2. I haven’t touched that module for weeks
3. It worked for me yesterday
4. This is not possible!
5. Must be a hardware issue.
6. I think this OS doesn’t support that.
7. I cant test everything. I need time for that
8. It works.
9. Somebody must have altered my code!
10. Why do you do it that way?
11. Check with the specs.
12. Code is not committed.
13. Is there any particular sequence?
14. It works in my simulator. Check it out
15. I am busy
16. Thats a minor bug
17. I have not noticed this before!
18. I have noticed this before!
19. User wouldn’t do that
20. Must be from designers end.
21. I will fix it when i have time.
22. Reduce the severity
23. Why do you log such simple bugs. Please mail such simple bugs.
24. Will check with supervisor.
25. Check with Requirements.

List goes on and on :P So What else does your developer say other than these 25 points ?

Thursday, January 23, 2014

Why some bugs are never found in testing phase.

Yes! Its true some bugs are never found during testing phase. Why cannot we track some bugs while an end user can identify it in app store build? This question would be a serious set back to testing career. So here you go for the solution.

1) Test every single detail in the screen.
You must be thinking, "you are kidding me, i test every single detail" but i say a big NO. We do not check with every single detail in the screen sometimes. Example: Details like pressed state for the button, pressed state audio, disabled state buttons. So be 100% sure that every single part of the screen is being tested.

2) Smoke Test
Create a smoke test plan for every project. By running SmTP you will be confident that main features are working as intended and then you can start performing system or ad-hoc testing

3) Run Test suite plan (TSP)
When you write test suite plan make sure you don't miss a single step/case. We always write positive test case and don't bother to write about negative test cases. So make sure you write both positive and negative test cases. By doing this you will be sure enough that every single module is being tested thoroughly.

4) Stop thinking like a quality tester, use application as an end user.
 If your company allows you to take company devices home, take the build and use the application as a normal user. I bet you will find some bugs and you will be surprised to find out that you never found those bugs while testing.

5) Ask for time if you have not completed testing.
Sometimes due to the tight schedule you would be forced to test quickly. Due to the pressure you will be completely fooled by some bugs as you will be in hurry to test the application. So if you feel like you need time, do talk to your supervisor and let him know that you require some extra time to test the application. If still not permitted run STP and if all modules are working raise a green flag for release and continue testing the application.

6) Test in all devices and OS 
Make sure you test application in all devices and OS present in your company. You may feel its tedious task but you will surely find some awesome bugs :)

7) Released build not tested*
Make sure your developer has not changed the code after u have approved for the release candidate build. Sometimes developers change code in the last minute and would never inform it to you as they feel its a minor change (I have personally experienced this). So do sit with the developer and make sure the build which you have tested is getting released in store to be in the safer side.

Thursday, January 16, 2014

Max supported OS for apple devices

1) iPhone
- iPhone 1 - 3.1.3
- iPhone 3G - 4.2.1
- iPhone 3GS - 6.1.3
- iPhone 4 - 7.0
- iPhone 4s - 7.0
- iPhone 5 - 7.0

2) iPod
- iPod 1G - 3.1.3
- iPod 2G - 4.2.1
- iPod 3G - 5.1.1
- iPod 4G - 6.1.3
- iPod 5G - 7.0

3) iPad
- iPad 1 - 5.1.1
- iPad 2 - 7.0
- iPad 3 - 7.0
- iPad 4 - 7.0
- iPad mini - 7.0