Test Architect Role

Test Architect Role:

 

 

The Test Architect (TA) role is a senior position in the organization and is treated on par with equivalent Management positions in terms of rewards, recognition, visibility and influence. However, one basic factor that distinguishes a TA from a Manager is the absence of direct-responsibility for managing people. While Management tends to have people management as a core feature of the job, the TA does not directly manage people. However, this in no way lets the TA off the hook, so to speak, from influencing, mentoring, coaching and providing direction to members of the Testing Organization - all very important responsibilities of the TA.

Responsibilities of Test Architect:

 

·        Provides Technical Leadership and Strategic Direction to the Testing Organization (TO)

·        Is responsible for Test Strategy formulation

·        Helps Formulate and Develop effective Test Architecture per organizational needs

·        Is Technically responsible for all the Testing performed by the TO

·   Is the foremost Technical Authority and is responsible for the overall Quality of deliverables across all parameters, both functional and non-functional including performance, security, usability, etc.

·        Is expected to pro-actively analyze current processes and practices and suggest/ drive improvements. Also, defines processes as needed

·        Has wide-reaching scope, impact and influence extending beyond the confines of the TO and spans across the entire product organization

·        Is the counter part to the development architect

·        Is involved in driving organization-wide Quality Process initiatives and their implementation to ensure Quality of deliverables

·        Maintains a "big and complete" picture view of the product, its dependencies, organizational goals, technology arena, etc. and helps guide and direct the functioning of the TO appropriately

·        Collaborates effectively and on an on-going basis with all constituents involved in product development and release

·        Helps with Test plan development

·        Is responsible for design and development of the TO's Test Automation framework / harness and any in-house tools required.

·        Is involved in understanding Business requirements and works with the development architect to translate requirements into solution architecture designs. Reviews requirements and seeks clarity as required, participates in product design reviews and works with the development architect and development team to make any design improvements and refinement as needed. Also helps incorporate Testability requirements into design

·        Analyzes competitive products and technologies and makes appropriate suggestions (may use demos, POCs) to influence product / technology direction

·        Has overall product knowledge and is able to guide both junior and senior team members

·        Involved in hiring activities for the TO and mentoring of TO team members

·        Pro-actively seeks to make continuous improvements to Test coverage, execution and automation

·        Is results oriented and has a high degree of accountability, commitment and responsibility. The expectation is that involving a TA in a project is a guarantee of obtaining positive outcomes

·        Improvement of the organization testing process and growth

·        Must be focused on defining the testing process and setting the test team up for continued success.

·        Acts as subject matter expect for Software testing standards, processes, methodology and tools.

Attributes expected from a Test Architect:

 

·        Comfortable with creating test cases for highly complex systems to ensure full test coverage(for a given definition of full) 

·        In depth knowledge of several/lots of test techniques/methodologies 

·        In depth experience of working across all (ok lots) of development methodologies 

·        Ability to specify and setup test environments 

·        Ability to produce technical strategy for a project/product 

·        Comfortable perform role outside of their comfort zone (so pick up a new technology, on a new project quickly and become the expert) 

·        Ability to improve testing processes and techniques on a project

·        Ability to do test tool evaluation 

      Probably an expert in many test tools 

Keywords:

what is test architect role

test architect responsibilities

test architect job description

test architect roles and responsibilities

test architecture

test architect resume

test architect interview questions

test architect salary

roles responsibilities test architect

test architect job description

test architect interview questions

test architect role

test architect certification

test architect microsoft

test architect certification

What is a test architect?

What is a test architect?

So, what is a test architect. One answer is that it's a fancy title for an experienced tester. At Microsoft, we try to avoid this definition, and instead describe test architect as a senior test role with wide strategic scope. That's the short answer.

Here's the long answer.

There is no "typical" test architect role. Test architects focus on a diverse set of goals and perform a wide variety of tasks. Some spend time developing testing infrastructure, test authoring frameworks, or evaluating features in order to create complex tests. Some are in charge of a particular technology for their group. Others spend time consulting on how to improve test effectiveness. The common thread across all test architect roles and the primary responsibility of a test architect is to provide technical leadership and strategic direction for their testing organization. It is also expected that in addition to accountability to the current product, that senior test architects will consistently look beyond the current release and may have several deliverables not tied to a particular product release.

A test architect has in-depth knowledge of a variety of testing techniques and methodologies used both inside and outside of Microsoft. They often provide technical assistance and/or advice to the test Manager. The question often arises - "Shouldn't the test manager be doing all of this anyway?" Typically, the test Manager is the individual providing leadership and formulating team strategy. However, as organization sizes continue to grow and/or the test manager takes on additional responsibilities, it often makes sense for a test architect to step in and assist with or deliver on these responsibilities. The test architect often takes on some leadership roles typically associated with the test manager. For example, while test managers certainly will implement change to grow their teams, the test architect is frequently the individual who provides technical leadership and strategic direction for their organization.

A test architect is expected to be able to affect change not only across the testing community, but between other engineering disciplines as well. Test architects must drive quality across all disciplines, providing guidance, feedback, and suggestions to improve quality practices across an entire engineering team.

While a few test architects may be focused on a specific problem or improvement, the goal for the test architect investment should be long-term improvement of the organization testing process and growth. Senior test leaders, when faced with an urgent problem or situation in need of quick improvement can typically find a solution. Broad or recurring issues, however, may require a test architect. The test architect should be thinking long-term and laying out a path for solving big issues over a long period and not focused on fighting daily fires. The test architect must be focused on defining the testing process and setting the test team up for continued success.

what is test architect role

test architect responsibilities

test architect job description

test architect roles and responsibilities

test architecture

test architect resume

test architect interview questions

test architect salary

roles responsibilities test architect

test architect job description

test architect interview questions

test architect role

test architect certification

test architect microsoft

test architect certification

How to Get a Software Testing Job as a Fresher?

Many students who want to build a career in IT look forward to being a software tester as a stepping stone. Whether you want to transition into software development later on or continue to become a rock-star software tester, it is a good idea to pursue a career as a software tester as your first job. This post will cover what you should and should not do to get your first job as a testing professional. How to Get a Software Testing Job When You Have No Experience? #1: Be Passionate About Testing Why do you want to do a testing job? This is probably the most common question across all testing interviews. You should have a clear answer as to why you plan to pursue a career in this field. If you are a computer science engineer, why did you not choose software development? If you are from some other streams, why not look for a job in your field of study? People who are passionate about this field and would love to grow as a quality tester often end up getting the best jobs out there. Anyone can be trained. But only the people with real interest in this field can make a name for themselves. #2: Have the Right Skills Required For the Job As a software tester, you'd be spending most of the time trying to "break" the software. You should have excellent aptitude skills coupled with knowledge of testing methodologies and tools. As a fresher, most of the time, you would not have exposure to any test cases. In such cases, you could join a training institute that offers hands on testing training. You could also take up some freelance work to improve your experience. Nowadays most job openings require you to have some certifications. This is made mandatory by most companies so that the candidate can be productive from day 1 and no amount of time or money need to be spent on training the candidates on the basics. If you are serious about testing career, you could go for certifications like ISTQB which will enhance your value in the job market. #3: Choose Your Niche Have you heard the saying "Jack of all trades but master of none"? Well, these days, especially in IT field, you need to specialize and not generalize. A specialist is always preferred over a generalist by most companies (Although it's not a good idea to choose specialists as they have limited scope, most HR's find the easy way out to fill up the position fast). Some of the popular testing niches you can choose are Manual testing: In this method, a tester takes on the role of the end user- one who will be using the software product. It's a tedious process by which the tester has to use all of the software features to find bugs. In most cases, testers perform these tests based on an already laid out plan Automation testing: Using this mode of testing, a tester can evaluate software by writing scripts that automate the tasks. No need of manually doing everything which saves a lot of time. This is often the most cost-effective way of testing a software over the long term Performance testing: In this method of testing, software is tested against a specific workload. Some of the metrics that would be evaluated are responsiveness, maximum load capacity and so on. Similar to software development, software testing is a vast field. So you should focus on one area of testing. This will make you a hot property in the job market. Even though you should specialize in one area, you should also try to be familiar with other areas. You must also be flexible enough to shift to another track if required. #4: Bust All Myths Sadly, the industry and students have a lot of misconceptions about software testing jobs. Some of the myths still prevailing are Software testing is a simple job. So anyone can do it: Although it's not rocket science, testing still requires a lot of work and intellect from the part of the tester. So don't think this is a walk in the park type of job and jump into it. Testing is a second tier job compared to development: We had one student apply for a job who supposedly thought that she was entitled to a testing job since she had already worked as a software developer. Her argument was that since testing is inferior to development, and she cracked development interview and worked on a project or two, she was entitled to a job as a tester without an interview. Well, we have news for you. It isn't the case! Software testing is just as important and valued as software development. So experience in one domain doesn't necessarily entitle you to a free pass to another. Automation testing means clicking a few buttons and the software will do it for you. While it can be true for some existing test cases, most of the time you'd have to create the script for automation testing. So don't think that it will be easy and since you don't know/hate programming, it's the perfect opportunity for you. #5: Write a Perfect Cover Letter and Resume How many times have you applied to a set of jobs at a stretch using the same resume and not even thinking about including a cover letter? If you are like most people applying for a job, you reply should be "most of the time" or "always". We receive several resumes each day from candidates who simply attach their fresher resume and blindly apply to just about any job they can without even reading the titles. Do you really think a recruiter will take the pain to evaluate you after such an attempt? Always customize your resume and make sure that you include a custom cover letter with each application. Instead of trying to apply to 50 different employers at a stretch, apply to just a few relevant ones. You'll drastically improve your chances of hearing back from the employer.

Android Test Cases (Android Testing Criteria)

Android Test Cases (Android Testing Criteria)

Sym­bian Signed Tests Cases v 4.0.14

This ver­sion of the test cri­te­ria is in effect from 5^th Jan­u­ary 2010.

Ref­er­ence: Sym­bian Signed Test Criteria

TEST 1 — Installation
TEST STEPS
Before start­ing the test round, use a file man­ager to note the free user space avail­able on the phone. You will need this infor­ma­tion in test 8.
1	Install the appli­ca­tion being tested. The appli­ca­tion must install with­out error.
2	Dur­ing instal­la­tion note the ver­sion num­ber pre­sented to the user. The ver­sion num­ber must match that spec­i­fied dur­ing submission.
3	Ver­ify that the appli­ca­tion has suc­cess­fully installed on the device by nav­i­gat­ing to the area on the phone where new appli­ca­tions are installed. The appli­ca­tion should present one or more icon(s) on the phone.
Notes
For any sub­mis­sions which do not appear obvi­ously once installed, the sub­mit­ter must include details in the sub­mis­sion state­ment of how suc­cess­ful instal­la­tion can be verified. If the con­tent does not appear obvi­ously on the device once installed, and spe­cific instruc­tions are lack­ing in the sub­mis­sion state­ment, then this test will be failed.

TEST 2 — Appli­ca­tion start/stop behaviour
TEST STEPS
1	Start the appli­ca­tion by select­ing the icon or fol­low­ing the steps out­lined in the sub­mis­sion statement Nav­i­gate to the Task Man­ager and check that the appli­ca­tion appears there.
2	Close the appli­ca­tion from the Task Manager. Exit the Task Man­ager, and re-launch the Task Manager. The appli­ca­tion must no longer appear in the Task Manager.
3	Start the appli­ca­tion as in Step 1. Go to the Task Man­ager to ver­ify that the appli­ca­tion is running. The appli­ca­tion must appear in the task manager.
4	Close the appli­ca­tion from within the appli­ca­tion UI and then return to the Task Manager. The appli­ca­tion must no longer be run­ning and must no longer appear in the task manager.
5	Restart the appli­ca­tion as in Step 1. Nav­i­gate to the Task Manager. The appli­ca­tion must once again appear in the Task Manager.
Notes
An appli­ca­tion which must run in the back­ground does not need to appear in the Task Man­ager or present a UI so long as the devel­oper jus­ti­fies this behav­iour dur­ing submission. All appli­ca­tions must have some way of ver­i­fy­ing that they are run­ning on the device, though, and the devel­oper should pro­vide this information.

TEST 3 — Appli­ca­tion credentials
TEST STEPS
1	With the appli­ca­tion run­ning, check the name of the appli­ca­tion dis­played on the phone. The appli­ca­tion must dis­play the same name on the phone as stated dur­ing submission.
2	Note the func­tion­al­ity of the appli­ca­tion as it runs on the device. The basic func­tion­al­ity of the appli­ca­tion must match that declared dur­ing submission.
Notes
Step 1 does not apply to appli­ca­tions which do not have a UI VoIP appli­ca­tions must present a UI in order to pass this test.

TEST 4 — No dis­rup­tion to voice calls
TEST STEPS
1	With the appli­ca­tion installed and run­ning use a sec­ond phone to call the test device. The incom­ing call must be indi­cated to the user on the test device.
2	Answer the call on the test device. You must be able to con­duct a con­ver­sa­tion with the other party with­out inter­fer­ence from the appli­ca­tion being tested.
3	End the call in the nor­mal way on the test device. The voice call must be ended.
4	From the test device, make a call to a sec­ond phone. Answer the call from the other device. The call must be indi­cated on both devices, and you must be able to con­duct a con­ver­sa­tion with the other party with­out inter­fer­ence from the appli­ca­tion being tested.
5	End the voice call from the sec­ond device. The call must be ended on both devices.
6	Place a test call to the emer­gency 112 num­ber from the device. *Please check in your ter­ri­tory for the approved way to make test calls to the emer­gency ser­vices.
Notes
If the appli­ca­tion being tested has the Mul­ti­me­di­aDD capa­bil­ity, and has audio func­tion­al­ity, then that func­tion­al­ity must be in use whilst this test is per­formed. Par­tic­u­larly, it should be checked that the audio from the appli­ca­tion is faded down to allow the user to hear the tele­phone call. VoIP appli­ca­tions will need this test run­ning using both the hand­set held to the user's ear and using a head­set. The test should be run with a VoIP call in progress, and the incom­ing GSM call should be announced with call wait­ing tones.

TEST 5 — No dis­rup­tion to text messages
TEST STEPS
1	With the appli­ca­tion installed and run­ning, send a text mes­sage to the test device. The incom­ing text mes­sage must be noti­fied to the user as per their alert settings.
2	Read the text mes­sage on the test device and choose to reply. Send the reply. The reply must be received at the sec­ond device.
3	From the standby screen on the test device, nav­i­gate to the "new text mes­sage" option and cre­ate a new mes­sage. Send the mes­sage to the sec­ond device. The mes­sage must be received at the sec­ond device.

TEST 6 — Auto-start behaviour
TEST STEPS
1	With the appli­ca­tion run­ning, find the set­tings for the appli­ca­tion — either within the appli­ca­tion itself or from the set­tings option on the device. There must be an option which allows the user to enable/disable auto-start functionality.
2	Ensure that the set­ting for auto-start behav­iour is dis­abled, and restart the device. The appli­ca­tion must not start on device boot.
3	Now change the set­ting so that auto-start behav­iour is enabled for the appli­ca­tion and restart the phone. The appli­ca­tion must start when the phone boots.
Notes
If the appli­ca­tion does not have auto-start func­tion­al­ity, then this test does not need to be run.

TEST 7– No dis­rup­tion to key device applications
TEST STEPS
1	Ensure that the con­tacts, mes­sag­ing and cal­en­dar appli­ca­tions are pop­u­lated with data and start the appli­ca­tion as in Test 2. After the appli­ca­tion has been installed and used, the data entered into those appli­ca­tions must not be altered in any way with­out the user being aware.
2	With the appli­ca­tion run­ning, nav­i­gate to the mes­sages appli­ca­tion and cre­ate a new message. Save that mes­sage to the drafts folder and then open and edit it. Finally, delete the mes­sage from the drafts folder and delete a mes­sage from the inbox. All of the above actions should be pos­si­ble with­out inter­fer­ence from the installed application.
3	Nav­i­gate to the con­tacts application. Cre­ate a con­tact, then edit that con­tact and then delete it. The appli­ca­tion should not inter­fere with any of the actions above with­out noti­fy­ing the user and giv­ing them option to avoid the change.
4	Nav­i­gate to the cal­en­dar application. Cre­ate an appoint­ment in the cal­en­dar. Edit the appoint­ment and then delete it. The appli­ca­tion should not inter­fere with any of the actions above with­out noti­fy­ing the user and giv­ing them option to avoid the change.
5	Use the web browser on the device to go to a web page which is known to work on the net­work being used. It must be pos­si­ble to cre­ate a data con­nec­tion and to access the web page selected.
Notes
If the appli­ca­tion, as part of stated func­tion­al­ity, makes changes to user data then an excep­tion can be claimed here. The func­tion­al­ity must be described in the doc­u­men­ta­tion with the appli­ca­tion and all data other than that men­tioned in the user guide must remain untouched as described in the test case. The data used in this test case is also needed for Test 8, so leave the data on the device when pro­ceed­ing straight into Test 8.

TEST 8 — Un-install
TEST STEPS
1	Stop the appli­ca­tion as described in Test 2 and unin­stall the appli­ca­tion using the sys­tem installer. The appli­ca­tion must be unin­stalled with­out error.
2	Fol­low­ing the same steps as in Test 1, nav­i­gate to where you would expect to see the appli­ca­tion icon. The appli­ca­tion icon must not longer be present on the device. If you used another method to ver­ify suc­cess­ful instal­la­tion in Test 1 then use this method to ensure that the appli­ca­tion has been uninstalled.
3	Check the con­tacts, mes­sages and cal­en­dar appli­ca­tions to ensure that that the data present in Test 7 is still present in those applications.
4	Using the same file man­ager as at the start of Test 1 check that the amount of user space avail­able on the device is either the same as that found in step 1 or that any dif­fer­ence between the space avail­able before and after ful­fils the fol­low­ing criteria. a) Exclud­ing user-generated and down­loaded con­tent, the appli­ca­tion leaves no more than 100Kb of data on the phone after uninstall b) Any data left on the device after install matches the expla­na­tion given dur­ing the sub­mis­sion process
Notes
You should start this test with the appli­ca­tion data from Test 7 still in place on the device.

TEST 9 — Device adaptation
TEST STEPS
Note: The fol­low­ing test steps should be run on the list of devices cor­re­spond­ing to the UIDs spec­i­fied in the .pkg file. The lead device list can be found at http://tiny.symbian.org/devicetable
1	Install the appli­ca­tion onto the device The appli­ca­tion should install on the device or present an error mes­sage to explain that it can­not install onto that device.
2	Launch the application. The appli­ca­tion should run on the device or present an error mes­sage to explain that it can­not run on that device.
3	Briefly exam­ine the appli­ca­tion whilst running. UI ele­ments should be func­tional and text should be read­able in the main screen of the application.
4	If the device on which the appli­ca­tion is cur­rently being tested sup­ports por­trait and land­scape screen modes, start the appli­ca­tion and then switch between the screen modes. The appli­ca­tion should con­tinue to be func­tional, and usable, in both screen ori­en­ta­tions of the device, whether or not the appli­ca­tion rotates in response to the screen mode change.
5	Close the appli­ca­tion from the appli­ca­tion UI The appli­ca­tion should stop running.
6	Unin­stall the appli­ca­tion from the phone. The un-installation should hap­pen with­out error and the appli­ca­tion must be un-installed.
Notes
Appli­ca­tions which do not present a UI to the user in nor­mal usage do not need to run this test. On the pri­mary device — on which all of the other test cases have been run — only step 4 of this test should be per­formed as all of the other steps of this test case are cov­ered elsewhere.

Addi­tional Tests for VoIP applications

Note that Test 3 and Test 4 both con­tain addi­tional notes which apply to the test­ing of VoIP appli­ca­tions. Please read and apply these notes when run­ning those tests on VoIP applications.

Test 10 — Addi­tional emer­gency call test­ing for VoIP apps
TEST STEPS
Note: These test steps should be per­formed twice — once with a SIM card in the device and once without.
1	With the VoIP appli­ca­tion run­ning in the back­ground, but with no VoIP call in progress, ini­ti­ate an emer­gency call in the usual way. The emer­gency call must be placed over the GSM/CDMA net­work successfully.
2	With the VoIP appli­ca­tion run­ning in the back­ground with a VoIP call in progress, ini­ti­ate an emer­gency call in the usual way. The emer­gency call must be placed over the GSM/CDMA net­work suc­cess­fully and the VoIP call should be ter­mi­nated or placed on hold.
3	With the VoIP appli­ca­tion in the back­ground, and an emer­gency call active make a VoIP call to the device. The incom­ing VoIP must be rejected, and the emer­gency call must not be interrupted.

Posted in Symbian Application Testing, Test Cases. 5 Comments

Testing Checklist for Mobile Applications

October 23, 2009 — anuragkhode

By-Anurag Khode,Copyright 2009-10

No.	Mod­ule	Sub-Module	Test Case Description	Expected Result
1	Instal­la­tion		Ver­ify that appli­ca­tion can be Installed Successfully.	Appli­ca­tion should be able to install successfully.
2	Unin­stal­la­tion		Ver­ify that appli­ca­tion can be unin­stalled successfully.	User should be able to unin­stall the appli­ca­tion successfully.
3	Net­work Test Cases		Ver­ify the behav­ior of appli­ca­tion when there is Net­work prob­lem and user is per­form­ing oper­a­tions for data call.	User should get proper error mes­sage like "Net­work error. Please try after some time"
4			Ver­ify that user is able to estab­lish data call when Net­work is back in action.	User should be able to estab­lish data call when Net­work is back in action.
5	Voice Call Handling	Call Accept	Ver­ify that user can accept Voice call at the time when appli­ca­tion is run­ning and can resume back in appli­ca­tion from the same point.	User should be able to accept Voice call at the time when appli­ca­tion is run­ning and can resume back in appli­ca­tion from the same point.
6		Call Rejec­tion	Ver­ify that user can reject the Voice call at the time when appli­ca­tion is run­ning and can resume back in appli­ca­tion from the same point.	User should be able to reject the Voice call at the time when appli­ca­tion is run­ning and can resume back in appli­ca­tion from the same point.
7		Call Estab­lish	Ver­ify that user can estab­lish a Voice call in case when appli­ca­tion data call is run­ning in background.	User should be able to estab­lish a Voice call in case when appli­ca­tion data call is run­ning in background.
8	SMS Han­dling		Ver­ify that user can get SMSalert when appli­ca­tion is running.	User should be able to getSMS alert when appli­ca­tion is running.
9			Ver­ify that user can resume back from the same point after read­ing the SMS.	User should be able to resume back from the same point after read­ing the SMS.
10	Unmapped keys		Ver­ify that unmapped keys are not work­ing on any screen of application.	Unmapped keys should not work on any screen of application.
11	Appli­ca­tion Logo		Ver­ify that appli­ca­tion logo with Appli­ca­tion Name is present in appli­ca­tion man­ager and user can select it.	Appli­ca­tion logo with Appli­ca­tion name should be present in appli­ca­tion man­ager and user can select it.
12	Splash		Ver­ify that when user selects appli­ca­tion logo in appli­ca­tion man­ager splash is displayed.	When user selects appli­ca­tion logo in appli­ca­tion man­ager splash should be displayed.
13			Note that Splash do not remain for fore than 3 seconds.	Splash should not remain for fore than 3 seconds.
14	Low Mem­ory		Ver­ify that appli­ca­tion dis­plays proper error mes­sage when device mem­ory is low and exits grace­fully from the situation.	Appli­ca­tion should dis­play proper error mes­sage when device mem­ory is low and exits grace­fully from the situation.
15	Clear Key		Ver­ify that clear key should nav­i­gate the user to pre­vi­ous screen.	Clear key should nav­i­gate the user to pre­vi­ous screen.
16	End Key		Ver­ify that End Key should nav­i­gate the user to native OEMscreen.	End Key should nav­i­gate the user to native OEM screen.
17	Visual Feed­back		Ver­ify that there is visual feed­back when response to any action takes more than 3 seconds.	There should be visual feed­back given when response time for any action is more than 3 second.
18	Con­tin­ual Key­pad Entry		Ver­ify that con­tin­ual key pad entry do not cause any problem.	Con­tin­ual key pad entry should not cause any prob­lem in application.
19	Exit Appli­ca­tion		Ver­ify that user is able to exit from appli­ca­tion with every form of exit modes like Flap,Slider,End Key or Exit option in appli­ca­tion and from any point.	User should be able to exit with every form of exit modes like Flap,Slider,End Key or Exit option in appli­ca­tion and from any point.
20	Charger Effect		Ver­ify that when appli­ca­tion is run­ning then insert­ing and remov­ing charger do not cause any prob­lem and proper mes­sage is dis­played when charger is inserted in device.	When appli­ca­tion is run­ning then insert­ing and remov­ing charger should not cause any prob­lem and proper mes­sage should be dis­played when charger is inserted in device.
21	Low Bat­tery		Ver­ify that when appli­ca­tion is run­ning and bat­tery is low then proper mes­sage is dis­played to the user.	When appli­ca­tion is run­ning and bat­tery is low then proper mes­sage is dis­played to the user telling user that bat­tery is low.
22	Removal of Battery		Ver­ify that removal of bat­tery at the time of appli­ca­tion data call is going on do not cause inter­rup­tion and data call is com­pleted after bat­tery is inserted back in the device.	Removal of bat­tery at the time of appli­ca­tion data call is going on should not cause inter­rup­tion and data call should be com­pleted after bat­tery is inserted back in the device.
23	Bat­tery Consumption		Ver­ify that appli­ca­tion does not con­sume bat­tery excessively.	The appli­ca­tion should not con­sume bat­tery excessively.
24	Appli­ca­tion Start/ Restart		1. Find the appli­ca­tion icon and select it 2. "Press a but­ton" on the device to launch the app. 3.Observe the appli­ca­tion launch In the time­line defined	Appli­ca­tion must not take more than 25s to start.
25	Appli­ca­tion Side Effects		Make sure that your appli­ca­tion is not caus­ing other appli­ca­tions of device to hamper.	Installed appli­ca­tion should not cause other appli­ca­tions of device to hamper.
26	Exter­nal incom­ing com­mu­ni­ca­tion – infrared		Appli­ca­tion should grace­fully han­dle the con­di­tion when incom­ing com­mu­ni­ca­tion is made via Infra Red [Send a file using Infrared (if applic­a­ble) to the device appli­ca­tion presents the user]	When the incom­ing com­mu­ni­ca­tion enters the device the appli­ca­tion must at least respect one of the fol­low­ing: a) Go into pause state, after the user exits the com­mu­ni­ca­tion, the appli­ca­tion presents the user with a con­tinue option or is con­tin­ued auto­mat­i­cally from the point it was sus­pended at b) Give a visual or audi­ble noti­fi­ca­tion The appli­ca­tion must not crash or hung.

kEYWORDS:

mobile application test cases

java mobile application testing tutorial

java mobile application testing example

mobile application development tutorial

mobile testing pdf

mobile testing techniques

mobile application testing techniques and tools

software testing techniques

mobile testing methodologies

mobile testing tutorial

mobile testing tools

mobile testing interview questions

mobile testing interview questions and answers pdf

mobile testing tools

mobile testing tutorial

mobile testing interview questions with answers

mobile apps testing interview questions

mobile application testing interview questions

mobile application testing interview questions and answers

mobile app testing interview questions

test cases mobile application testing

iphone testing interview questions

mobile application testing tutorial

interview questions handset testing

mobile application testing tools

mobile application testing ppt

mobile application test cases sample

windows mobile test cases

automation tool test cases

android test cases

mobile application testing

test cases for mobile

test cases for mobile phone

Interview Question on Mobile Application Testing

Inter­view Ques­tions on Mobile Appli­ca­tion Test­ing!!!…well I know very well, many of you must have been in search of thisthing since so long.Starting from a begin­ner in this domain to an expert, every­one  is very keen to know what are the dif­fer­ent ques­tion they may come across  in there interview.Here in my post I have shared some inter­view ques­tions which me or my friends have come across in there inter­views for the post of Mobile Soft­ware Testers.I hope this will help you:-

1. What is the dif­fer­ence between Mobile Test­ing and Mobile Appli­ca­tion Testing ?
2. What is your approach while Test­ing Mobile Applications?
3. Have you ever writ­ten a Test Plan?What are the things spe­cific to Mobile Appli­ca­tion would you empha­sis on while writ­ing test plan for Mobile Applications?
4. Do you know Facebook?Tell me what are the High level test cases for Face­book Web Appli­ca­tion and for Face­book Mobile Application?
5. Can you please let me know,the devices you have worked upon?
6. Test­ing of Mobile Appli­ca­tion on Emulators.Can you let me know your view?
7. Have you ever worked on any automa­tion tool for Test­ing Mobile Application?
8. Please tell me about your project.What kind of Mobile Appli­ca­tions have you worked upon?
9. Do you have Idea about Mobile Oper­at­ing Systems?
10. Black­berry Devices have which Oper­at­ing system?
11. What is cur­rent iOS (iphone OS) version?
12. You have two cases. 1st you can not dis­con­nect your call and 2nd you can not send SMS from your devices.Tell me Sever­ity and Pri­or­ity in both the cases?
13. What are dif­fer­ent Mobile Platforms/OS?
14. What are the dif­fer­ent way you can install a Mobile Application?
15. Have you ever worked on Device Anywhere?Do you have expe­ri­ence of work­ing on it?
16. Do you have Idea about appli­ca­tion cer­ti­fi­ca­tion pro­gram like True Brew Testing(TBT),Symbian Signed Test Criteria,Java Ver­i­fied Program?
17. See this application(Interviewer is given a Hand­set with a Mobile Appli­ca­tion installed).Tell me what are the bugs in this Mobile application/Game.?
18. Have you ever worked on LBS Application ?
19. How will you test a Loca­tion Based Mobile Application?
20. How will you per­form Per­for­mance Test­ing for a Mobile Application?

Some mobile handset,messaging related, GPS related questions:-

1. Can you name some per­for­mance test­ing tool.
2. Can you explain some file for­mat for mul­ti­me­dia test­ing (audio and video)
3. How to write blue­tooth the test case for stress, give me 20 example.
4. Explain the WAP pro­to­col stack.
5. Explain the type of test­ing you have done in mobile appli­ca­tion testing.
6. How basic phone is dif­fer­ent from smart phone in test­ing perspective
7. Which android ver­sion you tested ?
8. Write few sce­nar­ios for any fea­ture in a mobile phone other than browser.
9. Do you know about android?
10. Explain the Archi­tec­ture of android
11. Load Test­ing on Mobile and Web application.
12. Test con­di­tions for touch screen mobiles(landscape and portrait).
13. Explain about the mobile appli­ca­tion project that you worked in pre­vi­ous company?
14. How you did per­for­mance test­ing for mobile appli­ca­tion in your pre­vi­ous organization.
15. Can you name some per­for­mance test­ing tool. 12 What do you under­stand by Mul­ti­me­dia test­ing in mobile devices.
16. What is mobile mem­ory leak­age, have you tested that?, which tools have you used.
17. On which mobile u have tested the browser?
18. Types of devices tested dur­ing mobile appli­ca­tion testing?
19. writ­ing high level scenario's for any mobile features(I selected Calling)
20. Dif­fer­ent types of DRM
21. What is com­bined delivery?
22. Is it pos­si­ble to trans­fer seper­ate deliv­ery con­tents to mem­ory card then to other phone?
23. can we open seper­ate deliv­ery files, if we have rights and con­tents copied from mem­ory card?
24. what dif­fer­ent types of browser con­tents tested?25.Any idea of SDK?
25. Any idea of VPN?
26. Explain the type of test­ing you have done in mobile appli­ca­tion testing.
27. How GPRS works?
28. How GPS works internally.
29. What is GPS how did you tested
30. About GPS and A-GPS.
31. Write test cases on Cam­era feature.
32. That are the mobile plat­forms you worked on?
33. What is Android and what are the extra fea­tures in Android?
34. A mobile num­ber con­tains 10 dig­its, which kind of method you fol­low to test a mobile num­ber on a tele­phone keypad?
35. What is Blue­tooth and how you test them?
36. what is the exten­sion of android application?
37. Explain abt tools used in Mobile Hand­set Testing.
38. How to test SMS, MMS and what is Class1, class2 message.
39. Test cases for Alarm , Set­tings , Media player , Browser , Bluetooth ?
40. On which mobile u have tested the browser?
41. What all the GSM mobile you have tested?
42. Bug Track­ing Tool – JIRA
43. What are the BT pro­files, give some examples.
44. What BT pro­files sup­ported in Froyo and not sup­ported in Eclairs.
45. What is the MMS size and is it net­work dependent ?
46. Lat­est ver­sion of OMA DRM
47. when mes­sage with 500 char­ac­ter sent what happens
48. Write any five test cases for Mes­sag­ing Subsystem?
49. What kind of mobile appli­ca­tion i have tested?
50. What do you under­stand by Mul­ti­me­dia test­ing in mobile devices.

Keywords:

mobile testing

mobile testing tutorial

mobile testing tools

mobile testing interview questions

mobile testing jobs

mobile testing ppt

mobile testing wiki

mobile app testing

mobile software testing

mobile automation testing tools

mobile testing tutorial

mobile phone testing tools

mobile application testing

mobile testing interview questions

mobile testing tools tutorial

mobile app testing tools

mobile testing tools free download

mobile testing tutorial pdf

mobile testing interview questions

mobile testing tools

java mobile application testing tutorial

java mobile application testing example

mobile application development tutorial

mobile testing pdf

mobile testing techniques

mobile application testing techniques and tools

software testing techniques

mobile testing methodologies

mobile testing tutorial

mobile testing tools

mobile testing interview questions

mobile testing interview questions and answers pdf

mobile testing tools

mobile testing tutorial

mobile testing interview questions with answers

mobile apps testing interview questions

mobile application testing interview questions

mobile application testing interview questions and answers

mobile app testing interview questions

test cases mobile application testing

iphone testing interview questions

mobile application testing tutorial

interview questions handset testing

mobile application testing tools

mobile application testing ppt

Mobile Testing: An Overview

Introduction

Most general software testing principals apply equally well to mobile solutions, although the number of tools available for mobile testing is much smaller, and there are a lot of extra potential problems your users can encounter that you have to test for.Many mobile solutions involve a significant hardware element in addition to the PDA, such as scanners, mobile telephony, GPS and position based devices, telemetry, etc. These extra hardware elements place additional demands on the tester, particularly in terms of isolating a bug to hardware or software.Mobile applications are often intended to be used by people with no technical or IT background, such as meter readers, milkmen, insurance sales people, on devices that have small screens, and either no keyboards or awkward keyboards. Good usability testing, carried out in conjunction with key users, in their own environment, is essential. I have seen a number of hand held projects fail for the reason that the end-user could not come to terms with the technology, even though the application was robust and met the functional spec. Many hand-held operating systems come in even more flavors than their desk top counterparts. I can think of seven flavors of Windows CE alone. Add to this that many enterprise PDA manufactures OEM the operating system, and update it regularly, you start to see the problems testing. Remember also that we don't have our faithful automation tools for regression testing here.

Let's start with some Mobile Testing Basics.

Mobile Testing Basics

Mobile Device Testing is the process to assure the quality of mobile devices, like mobile phone, PDA etc. The testing will be conducted on both hardware and software.

And from the view of different procedures, the testing comprises R&D Testing, Factory Testing and Certificate Testing.

R&D Testing

R&D test is the main test phase for mobile device, and it happens during the developing phase of the mobile devices. It contains hardware testing, software testing, and mechanical testing.

Factory Testing

Factory Testing is a kind of sanity check on mobile devices. It's conducted automatically to verify that there are no defects brought by the manufacturing or assembling.

Certificate Testing

Certificate Testing is the check before a mobile device goes to market. Many institutes or governments require mobile devices to conform it's specifications and protocols to make sure the mobile device will not harm users' health and have the compatibility with devices from other manufactures. Once the mobile device passes the checking, a certificate will be issued to it.

Unique Challenges in Testing

Unlike the PC based environment, the mobile environment is constituted by a plethora of devices with diverse hardware and software configurations and communication intricacies.

This diversity in mobile computing environments presents unique challenges in application development, quality assurance and deployment, requiring unique testing strategies.

Mobile Buisness Applications can be classified into stand-alone applications and enterprise applications. On the other hand, Enterprise applications are built to perform resource intensive transactions that are typical of corporate computing environments. Enterprise applications also interface with external systems through Wireless Application Protocol (WAP) or Hyper Text Transfer Protocol (HTTP). The unique challenges in testing mobile applications arising from diversity of the device environment, hardware and networking considerations and Rapid Application Development (RAD) methodologies are explained below:

Diversity of the Device Environment

The realm of mobile computing is composed of various types of mobile devices and underlying software (hundreds of device types, over 40 mobile browsers). Some of the unique challenges involved in mobile testing as a result of this condition are:

Rendering of images and positioning of positioning of elements on screen may be unsuitable in some devices due to the difference in display sizes across mobile devices and models.

Exhaustive testing of user interfaces is necessary to ensure compatibility of the application.

Mobile devices have different application runtimes- For example, Binary Runtime Environment for Wireless (BREW), Java, embedded visual basic runtime are some of the runtimes commonly available in mobile devices. Applications should be tested exhaustively for the variations specific to runtime.

Hardware Configuration & Network related challenges

Mobile environment offers lesser memory and processing power for computing when compared with the traditional PC environment. Unlike the network landscape of PC environment, the network landscape of a mobile device may have gateways (access points between wireless internet and the cable internet). Some of the drawbacks of diverse hardware configurations and network landscape of mobile devices are:

Limitations in processing speed and memory size of mobile devices lead to variations in performance of applications across different types of devices.

Testing programs should ensure that the applications deliver optimum performance for all desired configurations of hardware.

Some devices communicate through WAP while some others use HTTP to communicate. Applications should be tested for their compatibility with WAP enabled as well as HTTP enabled devices.

The network latency (time taken for data transfer) will be unpredictable when applications communicate over network boundaries, leading to inconsistent data transfer speeds. Testing should measure the performance of applications for various network bandwidths.

Gateways in a wireless network may act as data optimzers that deliver content more suitable for specific devices. This data optimization process of gateways may result in decreased performance for heavy traffic. Testing should determine the network traffic at which the gateway capabilities will impact performance of the mobile application.

Rapid Application Development (RAD)

In order to deliver the benefits of faster time to market, RAD environments are used for mobile application development. Since the time taken for development is reduced by the introduction of RAD tools, builds will be available for testing much earlier. Therefore, RAD methodology imposes an indirect pressure on testing teams to reduce the testing cycle time without compromising on the quality and coverage.

Critical Success Factors

The critical factors that determine the the success of mobile testing program are:

Use of Test Automation

Use of emulators and actual devices

Testing for mobile environment and application complexity

Use of test automation

Testing of mobile applications is traditionally done by manual execution of test cases and visual verification of results. But it is an

effort intensive and time consuming process. Automating the appropriate areas of a testing program can yield quantifiable benefits.

Use of emulators and actual devices

Emulators can be beneficial for testing features of the application that are device independent. However, actual devices should be usedfor validating the results.

Testing for mobile environment and application complexity

Due to diversity in mobile hardware and platforms, testing programs need to incorporate GUI and compatibility tests in addition to the standard functionality tests. Enterprise applications are more complex in both functionality and architecture. Such applications require performance testing, security testing and synchronization testing in addition to the standard functionality testing.

Guidelines for Testing Mobile Applications

• Understand the network landscape and device landscape before venturing into testing and identifying bottlenecks.
• Conduct testing in uncontrolled real world test conditions (field based testing) is necessary, especially for a multitier mobile application.
• Select the right automation test tools for the success of testing program.

Rules of thumb for ideal test tool are:

1. One tool should support all desired platforms.
2. Tools should support for various screen types,resolutions and input mechanism such as touchpad and keypad.
3. The tools should be connected to the external system to carry out end to end testing.

• Check the end to end functional flow in all possible platforms atleast once.
• Conduct Performace testing,GUI testing and Compatibility testing using actual devices.Even though these testing can be done using emulators, testing with actual devices is recommended.
• Measure performance in realistic conditions of wireless traffice and user load.
  
  
  
  
  
  
  Keywords:
  
  
  mobile testing

  mobile testing tutorial

  mobile testing tools

  mobile testing interview questions

  mobile testing jobs

  mobile testing ppt

  mobile testing wiki

  mobile app testing

  mobile software testing

  mobile automation testing tools

  mobile testing tutorial

  mobile phone testing tools

  mobile application testing

  mobile testing interview questions

  mobile testing tools tutorial

  mobile app testing tools

  mobile testing tools free download

  mobile testing tutorial pdf

  mobile testing interview questions

  mobile testing tools

  java mobile application testing tutorial

  java mobile application testing example

  mobile application development tutorial

  mobile testing pdf

  mobile testing techniques

  mobile application testing techniques and tools

  software testing techniques

  mobile testing methodologies

  mobile testing tutorial

  mobile testing tools

  mobile testing interview questions

  mobile testing interview questions and answers pdf

  mobile testing tools

  mobile testing tutorial

  mobile testing interview questions with answers

  mobile apps testing interview questions