Tuesday 29 July 2014

Windows App Testing :: Overall Representation of Windows App components

This post contains the overall representation of "Windows Phone App Components". I will be sharing details about individual components in the upcoming blog series. Here is the list of components in pictorial representations. I  am just sharing my knowledge(what I have learnt so far) through this blog .It would be really helpful for me when you share your thoughts about my learning approach. "I share because I care.I hope the same from your end too" :).

Friday 25 July 2014

Windows App Testing :: Windows Phone Supported devices - Part- 6

Windows Phone (7, 8 and 8.1) Supported Devices:

Windows Phone 7
  • Dell Venue Pro
  • HTC 7 Pro
  • HTC 7 Surround
  • HTC 7 Trophy
  • HTC 7 Mozart
  • HTC HD7
  • LG Optimus 7
  • LG Quantum
  • Samsung Focus
  • Samsung Omnia 7


Windows Phone 7.5
  • Acer Allegro
  • Fujitsu Toshiba IS 12T
  • HTC Rader
  • HTC Titan (Ultimate/Eternity)
  • HTC Titan II
  • Nokia Lumia 510
  • Nokia Lumia 610
  • Nokia Lumia 710
  • Nokia Lumia 800
  • Nokia Lumia 900
  • Samsung Focus 2
  • Samsung Focus S
  • Samsug Omnia W
  • ZTE Orbit
  • ZTE Tania
  • Windows Phone 7.8
  • Nokia Lumia 505


     Windows Phone 8
  • HTC 8S
  • HTC 8XT
  • Huawei Ascent W1
  • Nokia Lumia 520, 521,525
  • Nokia Lumia 620
  • Nokia Lumia 625
  • Nokia Lumia 720
  • Nokia Lumia 810, 820, 822
  • HTC 8X
  • Nokia Lumia 920, 925,928
  • Nokia Lumia 1020
  • Nokia Lumia 1320
  • Samsung ATIV S, ATIV S Neo
  • Nokia Lumia Icon
  • Nokia Lumia 1520
  • Samsung ATIV SE


Windows Phone 8.1
  • Micromax Canvas Win W092
  • Nokia Lumia 530
  • Nokia Lumia 630, 636,638
  • Prstigio MultiPhone 8400 DUO
  • Yezz Billy 4.0
  • Micromax Canvas Win W121
  • Prrestigo MultiPhone 8500 DUO
  • Yezz Billy 4.7
  • Nokia Lumia 930 

Windows App Testing :: History of Windows Phone and its Version- Part 5

Windows Phone:
Windows Phone which is the successor to Windows Mobile is a smart phone OS developed by MS. It is incompatible with the older versions. It is primarily aimed at the consumer market rather than enterprise. It was first launched under Windows 7 OS.

Windows 7:
Windows 7 was released on 8th Nov, 2010. MS released an updated version of WP (Version 7.5) in May 2011.
Feature Included:
  • IE9 (that supports same as web standard)
  • Multi-tasking of third party apps.
  • Twitter Integration
  • Windows Live Sky Drive.
A minor update was released in 2012 under the code name “Tango”.

 Windows 7.8
In Jan 2013, Windows 7.8 was released
Features added:
  • Updated Started screen
  • Additional color schemes
  • Additional wallpaper options
Limitations:
Windows 7 was not up-gradable to Windows 8 due to hardware limitations. However not all the users have received the Windows 7.8 update.

 Windows Phone 8
MS released a new generations of OS in 29th Oct 2012. Windows Phone 8 brought support for the updated hardware which includes multi core processor and high screen resolutions. With the new hardware, Windows 8 could able to compete with Google and Apple.

Windows Phone 8.1:
It was released on 2nd April 2014.
Features:
  • Notifications Center
  • IE 11
  • Separate Volume controls
  • Options to skin and add a tile live to the start screen
Starting with release, MS has dropped the requirement that all Windows Phone OEMs include a camera button and physical button for back, start, and search.

Thursday 24 July 2014

Windows App Testing: History of Windows Mobile and its version -Part 4

Windows Mobile 5
Windows Mobile was released on 9th Dec 2005 under the code name “Magneto”. Microsoft offered a mainstream support for WM 5 through Oct 12, 2010 and extended their support through 13th Oct 2015.
It used the .NET compact framework 1.0 SP3. It also included the MS exchange server “Push” functionality. All the WM 5 devices supported Direct Push.
Feature:
  • Microsoft Office mobile which includes (PowerPoint, excel with graphing capability, Word mobile ability to insert tables and graphics
  • Windows media player 10
  • Blue tooth support
  • QWERTY keyboard support
  • GPS
  • Battery life

Windows Mobile 6
Windows mobile 6 was released on 12th Feb 2007.
It has come in three different versions.
  •  Windows Mobile 6 Standard for “Smart phones (Phones without touch screens)
  •  Windows Mobile 6 Professional for Pocket PCs with phone functionality
  •  Windows Mobile 6 classic for Pocket PCs without cellular radios.

WM6 was powered by windows CE 5. Windows mobile 6 was meant to be similar in design of Windows Vista.  Enterprise users’ business environment was targeted in large number.
Feature:
  • Support for Office 2007 document formats (pptx, docx, xlsx)
  • OneNote Mobile
  • HTML E-Mail  support in  outlook Mobile
  • Serve search on Microsoft Exchange 2007
  • Out of Office replies with Microsoft Exchange 2007
  • Search ability for contacts in a Exchange Server Address Book
  • Developers and users access to MS SQL Server 2005 compact edition
  • Storage and retrieval of information. 
  • MS SQL Server 2005 compact edition
  • Supports were added to IE Mobile.
  • Storage Card Encryption
  • Customer Feedback option
  • Unlicensed Mobile Access (UMA) support for select operators

Windows Mobile 6.1
Windows Mobile 6.1 was released on 1st April, 2008. It was a minor upgrade of Windows 6 which includes performance enhancements, Home screen featuring horizontal tiles. It was not supported in the professional editions.
Feature:
  • Threaded SMS
  • Full page zooming in Internet Explorer
  • 'Domain Enroll' were also added
  • Automatic links for telephone numbers in Tasks and Appointments
  • Improved bandwidth efficiency in its push-email protocol "Active sync" of "up to 40%"
  • Considerably improved battery life in many devices.

Windows Mobile 6.5
Windows mobile 6.5 was released on 11th may 2009. It was not the part of windows mobile road map and was released after the release of Windows 7.
Feature
  • Revamped GUI
  • Microsoft's Zune player with vertically scrollable labels (called 'Titanium')
  • WM6.5 also includes the new Internet Explorer Mobile 6 browser, with improved interface
  • Skybox", "Skyline", "Sky Market”, icon based soft buttons (rather than text based)
  • Updated contacts app
  • Native support for a-GPS improved threaded text messaging
  • Performance improvement
  • Native support for multi-touch
  • Touchable tiles replaced soft keys
  • Drag-and-drop start menu icons
  • Improved memory management and gesture smoothing.
  • Additional features include threaded email and Office Mobile 2010.

The work on a major Windows Mobile update begun in 2004 under the codename "Photon", but the work have moved slowly and the project was ultimately cancelled. In 2008, Microsoft reorganized the Windows Mobile group and started working on a new mobile operating system. The product was to be released in 2009 as Windows Phone.
New OS was developed and the name Windows Mobile was renamed as Windows Phone. MS released the OS under the version Windows 7.
– Referred from WIKI

Windows App Testing: History of Windows Mobile and its Version Part-3

Continuing from previous post, this post tells the features about next three versions of Windows Mobile. Below written are the next three releases.

Pocket PC 2002
Pocket PC 2002 was released on October 2001 under the codename “Merlin”. It was powered by windows CE 3.0. It was also used for pocket PC phones and smart phone for the first time. Pockets PC 2002 were mainly a GSM device. They meant to be similar in design of Windows XP.

Features
  • Windows media Player 8 with streaming capability
  • MSN Messenger
  • Microsoft Reader 2
  • Office mobile includes Spell checker, Word count tool in Pocket word
  • Improved Pocket outlook
  • Connectivity was improved with file beaming on non-Microsoft devices such as Palm OS, the inclusion of Terminal Services and VPN support
  • Ability to synchronize folders
  • Enhanced UI with theme support and savable downloads
  • WAP in Pocket IE


 Windows mobile 2003
Windows mobile 2003 was released on June 2003 under the codename “Ozone”. It was the first release under the windows mobile banner. Windows mobile 2003, was powered by Windows CE 4.20
It came under four editions:
  •  Windows Mobile 2003 for pocket PC Premium Edition
  •  Windows Mobile 2003 for Pocket PC Professional Edition
  •  Windows Mobile 2003 for smart phones
  •  Windows Mobile 2003 for Pocket PC Phone Edition



Features
  • Blue tooth –File beaming
  • Headset Support, Add-on keyboards
  • Picture application with viewing, cropping
  • E-mail
  • Multimedia improvement (MIDI file support as ring tone)
  • Windows media 9 with streaming optimizations
  • A puzzle game (Jaw breaker), GAPI, SMS reply.


Windows mobile 2003 SE
Windows Mobile 2003 SE is the second edition of Windows SE and was released on 24th March 2004. It was first offered on DELL Axim 30. This was the last version where the users allowed taking backup and restoring in an entire device through Active sync (A data sync app developed by Microsoft).

Features
  • Portrait, landscape modes
  • Single column layout in pocket IE
  • WI-Fi




Tuesday 22 July 2014

Windows App Testing: History of Windows Mobile and its Version-Part 2

Windows CE
Microsoft begins their Research work in 1990 for developing handheld device. The development of Windows CE began after two years. The OS and the UI were developed separately. The separate team which handed the UI has a code name (Win pad). Windows CE is based on Windows 95 and has strong pen support in making porting easy. But the Win pad was delayed due to performance and Prize.
 It was not released as a consumer product. But Alpha release was made in showcasing the many interface elements. During the Win pad development a separate team worked on the project called “Pulsar” which was designed to be a mobile communications method of Win pad. Both the projects were cancelled later. The two groups worked on the project called “Pegasus” in 1995. It focused on hardware side of Windows CE OS. This product was shipped in 1996.

Pocket PC 2000 
Pocket PC 2000 code named as “Rapier” was released on 19th April, 2000. It was based on Windows CE backward compatibility and was retained with palm size PC’s.
The only resolution supported by this release was 240 *320 QVGA (Quarter Video Graphic Array). Pocket PC was not standardized with the specific CPU architecture. So, Pocket PC 2000 was released on different CPU architecture SH-3, MIPS, ARM.

Features

  • IR files beaming
  • Microsoft Reader
  • Microsoft Money
  • Pocket Internet Explorer
  • Windows Media Player
  • Pocket office (Include Work, Excel, Outlook)

  •  For more information please refer to the link: http://en.wikipedia.org/wiki/Windows_Mobile

Wednesday 16 July 2014

Windows App Testing: History of Windows Mobile and its versions - Part 1

To begin with this article, I'm sharing my experience in learning Windows Mobile, Windows Phone and Windows App Testing. The focus of my learning will be intended towards testing (that is, I will be seeing from the perspective of Windows Phone App testing).  To be there, I need to understand why did Microsoft think about having mobile phone with their OS? It dates back to 1994-95's where people started to vision this. 

I don't know what exactly made Microsoft to think about it in 1990's (the year when research begins) to build the mobile platform. But, I want to know the history about Windows Mobile and Phone. So that, it would help me to understand the platform evolution and build the thought process of Windows App testing.

I will be sharing my learning on Windows Phone App testing as the series posts, this being the first post in the series. I found this detail which says why and how Microsoft thought about mobile devices on their platform and what made them to step back in initial days. It sounds interesting in knowing the attempts to bring the OS operating on a hand held OEM.  I have referred Wikipedia and earlier referenced website for this information.

History:
Company: Microsoft Corporation

Release Version:
Below mentioned are the Windows Mobile OS release details with its code name.
  • Windows CE (Embedded Compact)
    • Pocket PC 2000: 19th April 2000, Rapier
    • Pocket PC 2002: October 2001, Merlin
  • Windows Mobile 2003: 23rd June 2003, Ozone
  • Windows Mobile 2003 SE: 24th March 2004
  • Windows Mobile 5: 12th May, 2005, Magneto
  • Windows Mobile 6 : 12th February 2007 , Crossbow
  • Windows Mobile 6.1: 1st April 2008
  • Windows Mobile 6.5 :  11th May 2009
  • Windows Mobile 6.5.5: Jan 2010
  • Windows 7 : 8th Nov 2010
  • Windows 7.5 : May 2011 ,, Mango
  • Windows Phone 7.8 : Jan 2013
  • Windows 8 : 29th Oct 2012 
  • Windows 8.1 : 2nd April 2014(Latest Updated Version)
  • Windows 9.0 (Upcoming Version)
In this post, I have shared the references which provide the information about Windows Mobile OS evolution and the release details. In the next post, I will be sharing the main features and the problem faced by them in each release version.
Next post will contain brief information about
  • Windows CE: 
  • Pocket PC 2000:  April 19, 2000: Rapier

Saturday 5 July 2014

My Experience through my project journey


I worked for one of the mobile app project. After completing the testing activities, the app gone for release. So, after the release I was eagerly waiting for the users’ feedback. Because I was asked to do a UX. On one way to approach the UX, I stated collecting all the feedback (rating) till date from the app store. Most of the people have given a 5 and 4 star ratings. But some people has shared 1, 2, 3 star ratings. This made me to think what went wrong. Why people has given such low ratings.  I believe that rating might help the team to trace out the problem to some extent. But it won’t help to solve the problems to great extend. Because those poor rating could also be given by the competitors itself. Anyhow, I collected all those poor rating to know what are the common problems among the people are. I grouped 1, 2, 3, poor rating into one; I saw 50 percentages of people have complained about the UI. Some people said, please rollback the older one. But by this, the decision cannot be made. Because there are people around 60 percentages (4 and 5 star), have said that the UI was good. So, UI is a common problem within the poor rating circle but not on the overall product level.
Now I started questioning myself .Okay. How to investigate these problems? These questions paid a way for some more questions. Still I am working for finding the answer for all those questions asked by myself.
One day, while I was learning about the design guidelines, suddenly a question sparked into my mind. Am I responsible for any kind of issues that happens over the product after the release? If people are not happy with the design, Should I need to be answerable for it?
I believe whether it is a product success/failure, an individual should not be claimed/Blamed for that. If it is a team then the entire team takes those responsibilities.  I started discussing this with my colleagues, before I take this to my teacher.  Over all I feel that as a tester it is important to learn about the product.
It made me to realize that tester needs to walk around all the phases of SDLC. Getting struck up at the testing phases will not help to a great extend. I realized what my teacher said about practicing by comparing with the sports people as an example.  Even a legend go for a practice before playing a real game, then as a tester what practices I should do to work for a project which goes to the real world and that might be used by a billions of people.
 But again it is tough for me to know how and when to start practicing. I will be taking this to my teacher and my lead to get clarity on this
In my organization if people ask me what’s your role I can easily give my answers to them. But, when it comes to a project, I am really confused to say my roles and responsibilities and the limitations. I learnt testers job in not about to share pass/Fail status. There are many things beyond that. Communicating with the people doesn't mean that we have walked out through the entire phase of SDLC. Working with individual teams (design, development, BA, etc) before the release and listening to the end users after the release and rework on it if needed is also a part of testers responsibility. So, I call a testers are connecting dots for the product. But it cannot be prolonged. There need a boundary line in case of claims and blames. When product fails people may raise their finger toward tester. When it succeeds in the market people may take the crown to their head. So, I want to know to what extend I can be blamed. When I say product failure it doesn't mean that some quality criteria have failed. It can be a user’s interest too. If people don’t show the interest on product scope, the product fails even it has met all the quality criteria. We can say this as requirement mismatch with people interest.
Now I am learning about the design so that I can have a better understanding about the product design what is needed for a client (product owner/ may not be needed for an end users. So, when working as a tester it is also important to understand the needs at both sides. But it is something tricky one.
There are so many heuristic that could help us to work on it. But what is needed for that context and choosing or identifying by your own matters a lot.  

My journey has just started. Hoping for the better one, not the safe one J