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

Serial No.	Device Name	Operating System	RAM	Storage
1	Nokia Lumia 520	Microsoft Windows Phone 8 , upgradeable to WP8 Amber	512MB	8GB
2	Nokia Lumia 521	Microsoft Windows Phone 8 , upgradeable to WP8 Amber	512MB	8GB
3	Nokia Lumia 525	Microsoft Windows Phone 8 Black	1GB	8GB
4	Nokia Lumia 610	Windows Phone 7.5	256MB	8GB
5	Nokia Lumia 620	Microsoft Windows Phone 8, upgradeable to WP8 Amber	512MB	8GB
6	Nokia Lumia 625	Microsoft Windows Phone 8, upgradeable to WP8 Amber	512MB	8GB
7	Nokia Lumia 720	Microsoft Windows Phone 8, upgradeable to WP8 Amber	512MB	8GB
8	Nokia Lumia 800	Microsoft Windows Phone 7.5 Mango, upgradable to v7.8	512MB	16GB
9	Nokia Lumia 810	Microsoft Windows Phone 8, upgradeable to WP8 Amber	1GB	8GB
10	Nokia Lumia 820	Microsoft Windows Phone 8, upgradeable to WP8 Amber	1GB	8GB
11	Nokia Lumia 822	Microsoft Windows Phone 8, upgradeable to WP8 Amber	1GB	16GB
12	Nokia Lumia 920	Microsoft Windows Phone 8, upgradeable to WP8 Amber	1GB	32GB
13	Nokia Lumia 925	Microsoft Windows Phone 8, upgradeable to WP8 Amber	1GB	16GB 32GB
14	Nokia Lumia 928	Microsoft Windows Phone 8, upgradeable to WP8 Amber	1GB	32GB
15	Nokia Lumia 929	Microsoft Windows Phone 8 Black	2GB	32GB
16	Nokia Lumia 1020	Microsoft Windows Phone 8, upgradeable to WP8 Black	2GB	32GB 64GB
17	Nokia Lumia 1320	Microsoft Windows Phone 8 Black	1GB	8GB
18	Nokia Lumia 1520	Microsoft Windows Phone 8 Black	2GB	32GB
19	Huawei Ascend W1	Windows Phone 8	512MB	4GB
20	Huawei Ascend W2	Windows Phone 8	512MB	8GB
21	Huawei Ascend W3	Windows Phone 8	1GB	-
22	Samsung ATIV S	Windows Phone 8	1GB	16/32GB
23	Samsung ATIV S Neo	Windows Phone 8	1GB	16GB
24	Samsung ATIV Odyssey 1930	Windows Phone 8	1GB	8GB
25	Samsung ATIV S I8750	Windows Phone 8	1GB	16/32GB
26	Acer Allegro	Microsoft Windows Phone 7.5 Mango	512MB	8GB
27	Htc 8S	Microsoft Windows Phone 8, upgradeable to WP8 Amber	512MB	4GB
28	Htc 8X	Microsoft Windows Phone 8, upgradeable to WP8 Amber	1GB	16GB
29	Htc 8XT	Windows Phone 8	1024MB	8GB
30	Htc Windows Phone 8X CDMA	Microsoft Windows Phone 8, upgradeable to WP8 Amber	1GB	16GB
31	Nokia Lumia 2520	Windows RT	2GB	32GB
32	Samsung ATIV Tab P8510	Windows 8	2MB	16/32GB
33	Acer W4-820-Z3742G03aii	Windows Phone 8.1	2GB	32GB
34	Acer W4-820-Z3742G06aii	Windows phone 8.1	2GB	64GB
35	Lenovo IdeaPad Yoga 13	Windows 8	4 to 8GB	128 or 226 GB
36	Lenovo IdeaPad Yoga 11	Windows RT	2GB	64GB
37	Lenovo IdeaPad Yoga 11S Ultrabook	Windows 8 , Windows 8 Pro	Upto 8GB DDR3L	256 GB SSD HDD
38	Lenovo IdeaPad Z500	Windows 8 64	4GB,6GB,8GB(DDR3)	HDD: 500GB.1TB
39	Lenovo IdeaPad Z580	Windows 8	4GB,6GB,8GB(DDR3)	HDD: 500GB.1TB
40	Microsoft Surface 2	Windows 8.1 pro 64-bit	2GB	32GB,64GB
41	Microsoft Surface	Windows RT upgradable to Windows RT 8.1	2GB	32GB,64GB
42	Microsoft Surface Pro 2	Windows 8.1 pro 64-bit	4GB,8GB	64Gb,128GB,256GB,512GB
43	Lenovo ThinkPad Helix	Windows 8 pro ,Windows 8	8GB DD3	128GB,180GB,256GB SSD SATA3
44	Lenovo ThinkPad DataSheet	Windows 8 pro ,Windows 8	8GB DD3	128GB,180GB,256GB SSD SATA3
45	Lenovo Lynx	Windows 8, Office Home & Student 2013	2GB DDR2	Upto 64GB eMMC

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 ?

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.

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

How do you convince a developer to fix a defect!

I know this would be a question every quality tester would have in their mind. I had the same question in my mind when i started my career. I believe these points below would be helpful to you (may be).

1) Firstly you need to follow the process. If your company has a defect tracking tool, make maximum use of it. Log every single defect(even very low defect) in tracker so as to maintain a report of the defects found. Do not have any verbal communication because most of the developers will just forget about the defect or pretend to forget.
2) Make sure you have written the steps properly. When u log a defect in tracker, do read the steps twice and try analysing if the other person could understand the steps. Most developer will drop fixing few defects if they cannot analyse the steps.
3) When it comes to severity make sure it is properly marked. Some developers don't even look into low defects. If you feel that the defect needs to be fixed by next build mark it as medium.
4) This point may not be applicable to some but I feel this is the most important thing, being more friendly with your developer could lead him/her not fixing the defects. Working with developer who is a stranger is more useful than a developer who is a friend. Developer who is a friend would normally force you to forget about certain defects. So I feel bringing personal relationship to work is a strict NO NO. Have a strict work life. If you have a good friend as a developer in your project, make it clear to him that work is work, work cannot get compromised.
5) Have a chat with the developer and inform him the severity of the defect and why it needs to be fixed. But when you approach a developer make sure he/she is not in a bad mood. Always be modest by asking "Are you busy? Can I have a 10 mins chat with you about the defects"
We normally tend to forget that even developers would be busy (or they pretend to be busy) and we just start blabbering about the defect. Just imagine if someone comes up to you and informs you about how bad you look or how ugly you are, Bad isn't it :) So when you start with conversation make sure you tell these words "Can you check if this feature is working properly, I believe this sequence will crash the application. Please have a look, I will regenerate in front of you" Looks simple but very hard to execute. We normally tend to blame or put some allegation on developer as soon as we approach them
6) If your defect status is still New, make a note of those defects and call for a meeting with higher official or supervisor. Meetings and discussion solves most of the problem as developers are forced to listen to their supervisors. But when you conduct meeting make sure you have a super valid points noted down to put forward in a meeting. Normally when I feel I am losing my hold on meeting I convey this dialog " I know most of the users wouldn't perform this sequence, but 1 in 100's will surely do. You see I believe that every user is important.( Last sentence is purely fictional :P)
7) Some defects would be very hard to regenerate, Our normal tendency is to run to a developer and inform about the random crash or behavior. But as usual some developers will not give a damn to this as there is no sequence for the defect.
So i would recommend you to not rush to developer immediately. Firstly if its crashing quickly save the crash log, or if you find a glitch take a screenshot as a proof. Now try regenerating it by remembering the last 10 steps. For this you need to be 100% active while testing. If you are not able to find the sequence nth time don't lose hope. Note it down in a sticky and continue testing other features rather than sticking to 1 single defect.  Finally if you cannot find it just go to developer and follow kindness behavior mentioned in point no 5 and provide maximum information about the defect and log it in tracker.
8) If its still not fixed, just send a mail to developer with cc to producers, supervisors and team member just to be in a safer side, i.e if the same defect is reported by the user, you can just forward the mail back again :P Witty isn't it :)

"A best tester is not the one who logs maximum number of defect. The best tester is one who get most of the bugs fixed"

"Every bug is reproducible, if it has occurred once"

- Bharath Shenoy

P.S

Following are the dialogs which you can use on a developer to fix defects ( make it filmy :P )
- I just conveyed this defect to the manager and he has asked you to fix this defect. (A big Lie)
- I read in one of the technical blog that an application got bad review just for not integrating this feature.
- I was telling everyone that you are a good developer and you fix all the defects.
- Don't you want your application to be a 100 % bug free. We can boast about this with other teams.
- I was telling my fellow tester that you cannot fix this defect.
- My previous developer used to fix all the defects which I reported, good na :) :)

Adios