Mobile Application Testing Interview Questions & Answer Android| iOS |Native React Native Flutter

[Music] hello everyone uh scifi are you here yeah i can hear you all right cannot see me right yep yep okay is everyone let me check the chat first uh hello everyone can hear us right are you guys able to see us yes yes yes all right thank you guys so let me share my screen first cool so yeah welcome everyone for the meetups of ministry of testing kuala lumpur community uh so this is our ninth meetup and i am your host today myself nitin i'm working as a qa lead in fave malaysia um so uh let me go through the agenda for today so we will start with uh introduction to ministry of testing community and then i will pass over to saif uh society will be giving a talk on mobile application testing and then we have our normal 99 seconds talk and after that it's about oh uh so what's ministry of testing right so this ministry of testing is the biggest software testing community which hosts events conferences provides learning materials for all the testers across the globe and it is a great community which has many great personalities and if you go to the ministry of testing main website you can see main like there are four main sections one is learnt on the dojo so we which gives which is entirely for the learnings so you can get articles talks podcasts courses etc from there and then there is a connect with the community option so it will give you access to the club which is similar to stack overflow for testers and then there is a slack uh which can be used for communication for the community within the community members and all and then there are feeds uh which feeds like 500 plus testing blocks across the globe and then there are events uh so the most important event is test bash uh so now everything is hosted online uh they just wrapped up uh online test bash for newsland or something so and meetups are organized across the different different communities and then you can actually contribute to the ministry of testing uh you can contribute like you can speak apply for a talk uh you can write some articles for them you can create a dojo course and you can provide reviews and put advertisements as well so that's about ministry of testing and regarding the community principles which we follow uh be human uh be kind be respectful be supportive and then be open-minded so that's the game lines which we are following in this community as well so now i would like to uh hand over this screen to scythe uh so he will be presenting uh mobile application testing made easy so he is currently working as a quality analyst in rea group so saif uh welcome to the screen yeah thank you nathan so you can share your screen i actually will give you access yeah so you guys able to see my screen right uh so everyone can they see my screen hello yes yeah nathan are you able to hear me or maybe you're audible yeah we can see your screen actually yeah okay so i'm out will also write yes yes so you want to start now or maybe you want to wait for another 2-3 minutes uh let's maybe let's wait for one minute and we can stop here oh okay fine fine i guess we can start now safe okay fine so basically in this seminar in this meetup we are going to discuss uh some of the important aspect of mobile application testing and why it is important we won't be going into the technical aspect like how we can design the whole test strategy and all these things because the time is very short but to give an overview to start from somewhere this meetup will help you to go ahead in if you want to go ahead with the mobile application testing and want to explore this domain also so let's start this i am working as a quality analyst in ra group asia and i have been in malaysia since around three years so yeah so first question is like why mobile application development is important we know that we are into mobile application testing but why we need mobile application testing basically uh there are many applications which are like having millions of download and this is taking place because like the app developers who are building the applications they know their value they know the value of the applications on the consumer end so mobile application development is a very important aspect in software development life cycle so as per certain statics if we are developing apps that's a lot of market potential according to gartner as of september 102 billion app downloads equated to roughly 1.26 billion in revenue and in 2013 alone so as you can see like 102 billion app downloads which is equivalent to dollar 26 billion in revenue so you can see the data and you can analyze that how much developers and the companies are investing in mobile application development and if any statics and historic data is to go by we are going to see this potential is going only going to rise up so that's why most of the companies and most of the developers they are now focusing on mobile application development with this the next question comes in like what is mobile application testing so once mobile app developers or maybe the companies are coming up with the development of any mobile applications maybe for android or ies they need to go through thorough testing so that the users are not appending the applications and it is having a good rating and apart from that the usability aspect of the application is also good so going to the theoretical definition of mobile application testing it is like uh testing by which application software developed for mobile phones is tested for its functionality usability and consensus mobile application testing can be an automated or manual type of testing mobile application either comes with pre-installed like dialer or can be installed from mobile software distribution platforms like play store and app stores so there are two kinds of applications one is native applications which are within the you can say mobile devices like dialer or maybe any other which is coming pre-installed in the device and others are like maybe you are installing from the play store or app store like facebook twitter you are directly installing from the app store so these are different these are not pre-installed applications so mobile apps are projected to hit dollar 188.9 billion in revenue by 2020. so as you can see uh the amount of investment and the revenue which mobile application development is bringing in it is going to be a very huge and some statics do show that internet usage is falling for mo falling and mobile internet usage is rising so basically it's happening because of the cheap data internet data that is getting available to the masses and because of these mobile usages internet usage is rising so i have given a brief overview why mobile application testing is important and what is mobile why is mobile development important but let us come to few more statics and this is going to blow your mind so study found that three quarter of mobile users are concerned about app performance before they buy and that half of app developers say they don't have time to properly test app before release so you can see like the performance of the application it's like 77 of the users feel like they haven't tested their application property properly and half of the developers say they don't have time to test the apps before release this is a huge concern because if your app is like having millions of users then definitely they are going to go and use your competitors mobile application so it will be a loss for your business also the softest study conducted through surveys by harry's interactive and news map found that 77 percent of consumers have concerns about mobile app performance those concerns do keep some from purchasing the biggest worry from a consumer standard standpoint so as you can see if you are using any application you are the consumer of any application you maybe you are using a ratio application for booking a flight if it is not working fine then you are not going to use that application i mean if it is crashing now and then and it is causing slowness on the mobile devices it's causing slowness to your device mobile device then you are not going to use that application and you are going to uninstall it so it will be a huge financial loss for the organization and for the company itself so some more statics like 50 percent of the consumer worry about debug 57 worry about crashes and 48 percent worry about performance yo you can relate like it's not like you have just developed the application and you are not going to have usability testing you are not going to do performance testing your app stores and it will bring in revenue it won't happen like that you just need to do thorough testing so that the end user the consumer they are not worrying about these types of performance issues and crashes so i i believe if you guys can guess this number this is a huge number and if this number we are going to convert it you are going to be amazed by this like this is the total number of mobile users for worldwide so you see like seven billion mobile phone users are there so how much potential it has in terms of generating revenues and these kind of things let's go to some more statics and app store consumer spending if you are not aware what is app store consumer spending it is like once you are making any in-app purchases or maybe you are buying anything any extra credits from your application through any app store or maybe you are buying the application itself from the app store that is spending is an app store consumer spending so it is total dollar 157 billion so and on an average dollar 157 billion is being spent that's a lot of money and 7 billion users worldwide so around 79 percent of users abandon the product after only one day of use so you can see that around 20 percent are only not letting the application or not they are not uninstalling the application apart from that 79 percent they are just abandoning the product after one day of use so i believe till what we have seen now there isn't any doubt why mobile app testing is important global mobile app revenue is projected to generate dollar 582 billion us dollars through paid downloads and in-app advertising so you can see the potential any mobile application if it is a very big enterprise or maybe if it is a very good consumer based mobile application how much money it can generate how much leads it can generate let's go and see like some of the approaches of testing mobile application it won't be a very detailed one but i will be touching uh the basic how we can do and how we can test mobile applications so basically there are different types of mobile apps one is native application one is hybrid application and one is mobile web so to give a more idea about native applications these applications basically they are written in the same language in which the os is like say for example android android is supporting uh you can say android studio and for that we need to write the code using android studio so it is written in java and if you go for ios we have a different platform we are using xcode to write the code and that is written in swift so likewise mobile webs they can be like have you heard about m.facebook.com you must have you must be remembering the days when we used to use m.facebook.com so all these websites which are using mdot something it is a mobile web uh though mobile web they are getting replaced by hybrid web applications or hybrid website but to summarize they are still in use and some companies are using it so we came to know like why mobile testing is important why mobile application development is important some statistics about why how revenues are getting generated so there are certain types of testing which we can do in mobile application so one is functional testing so functional testing is the like same type of testing how you are doing for web applications there are certain features that features you are testing across different platforms and then if everything is working fine you are just moving ahead with the release performance testing basically it is done using internal you can say ide like xcode and android studio or maybe you can use any other third party tools like for i mean for performance testing there are certain metrics also which you can take from different uh crash logs providers like fabrics and test flight and apart from that you can do some manual performance testing using inbuilt analyzers in android studio and xcode so memory leakage testing is also like similar to performance testing but in this we only see uh the leakage of the memory if any application it is having too much of memory leakage so what will happen if your application is like having too much of memory leakage it will cause your app to cache and it will also cause your device to slow down so i mean as a user i won't like to use any application which is consuming my memory and it is causing other apps to behave inappropriately so definitely we need to do memory leakage testing this also can be done using analyzers which are built in x code and android studio apart from that there are some third-party tools which can be used to do memory leakage testing so internet testing is something like maybe if you are using the application and you are getting any call messages we need to test our application in such a way that if any interruption like call messages or maybe any notification is coming our application is not getting freeze or it is not getting cash so we need to do some these types of testing network testing is like testing the application across different uh you can say internet strength like 4g 2g 3g maybe wi-fi so that i mean you know like as a consumer it's not like everyone is going to have a wi-fi or everyone is going to have 5g connections so that's why we need to test the application across 3g and 4g also installation testing is like if i want to install the application on different os version and apart from that if i am installing it on different oem so oem means original equipment manufacturer like samsung it is oem xiaomi it is oem iu it is oem so it is their original device which they are manufacturing so we need to test across these different devices and installation should be good it's not like if i'm able to install the application on samsung it shouldn't get installed it shouldn't be like that so whatever application we are installing it should get installed successfully on the devices or oem source upgrade testing okay so this is one of the most important testing because like if you are having millions of users and you want to do force upgrade testing first of all why we do force upgrade testing we do force upgrade testing so that we are not supporting the minimum version of the application which are being used by the user so say for example any user is using 4.0 point x version of the application now we have made multiple releases and our application is into 5.0 uh point x version now i want all the users to use version so in that case it won't be possible to ask all the users to update our application and saying that we don't want to support the lower version it won't be possible so what we can do in that case we can just ask the user uh to have we will be giving them a force upgrade and then they need to install the application in order to continue using the application further so localization and internationalization testing it's basically like uh i mean a very common example is like facebook you want to use facebook in any of your local languages maybe you want to use in polish language maybe you want to use in german language maybe you want to use in malay language how the application is tested if every translated in the application make sense in the localized language we are doing uh this kind of testing and what if i am posting anything in the morning in from usa is it like how it is getting displayed in india so these kind of testing we do in localization and internationalization testing and keeping in view the local aspect it is one of the most important testing that we need to do okay so basically this is like i came up with my own experience and it is a block from it's supposed from my blog which i have written few years back and the observation that i made is like how we can improve mobile application testing this is not a functional testing it's like coming from my experience and it's a non-functional testing so basically if you are testing the app you need to pick the app from the background it's not like just you need to go put the app in background and then you need to launch again maybe after one minute or two minute try relaunching the app the app should be behaving as expected and it shouldn't be causing any lags or maybe any crash so most of the time developers are not giving any heats to these kind of scenarios and once you launch the app after one minute or two minutes they start crashing so we need to look into this so the second thing is screen orientation we need to take care like if we are supporting the portrait or the landscape if we are not supporting portrait or landscape maybe whatsoever is the reason we shouldn't orientate the application in any wrong orientation and even if we are supporting we need to take care that the usability aspect is not lost and the application is still good to use in any orientation if we are supporting that the third one is the gesture i mean if you are using any application you might have noticed that if you try to tap any button or maybe you try to enter any text sometimes you need to do uh tapping multiple times like two three times so in that situation the usability aspect is not good maybe they need to increase the touch pad area where you are tapping i mean the developers need to increase the touch pad area so that it is easier for the end user to use the application and it is not causing any difficulty so performance like i as i discussed previously performance is also one of the most important aspect and we need to do the performance testing based on the you the competitors that say for example i am working for xyz company and their competitor is yz so i need to map my application and see if my launching time my closing app time maybe if any response is coming from the back end if i'm searching anything with response to the competitor it should be at par with the competitor it shouldn't lag behind otherwise it's not a good you can say news for us and network testing this is like what i said before like network testing we need to test the application in different networks 3g 4g wi-fi apart from that you can also try testing it in flight mode so when you are keeping your application in flight mode and you are like doing monkey testing or something like that it is going to cause some crashes i personally believe like if anyone is using 2g or 3g and if we are doing some testing in flight mode it is going to remove most of the bugs in flight mode and it won't be causing any issue in 2g or 3g network so i this is one of the best question which i have came across like many people are asking like there are so many devices and there are so many fragmentation in the os how we can do testing uh on how we can create a device matrix and which device to test so to answer this i haven't like written a very high five long answer but what i have generically used in my experience and from my experience what i can say is once we want to create the device matrix we need to take out the device which is having a higher user base then we need to test on the new os version say for example apple recently came out with ios 12 right so in order to make sure that once the user are migrating to new os version ios 12 i need to test it beforehand in the beta version of the ios 12 so that i need to make sure that the application is not crashing or maybe there isn't any ui issues in the ios 12 so this is called like pre beta testing on the application uh different companies are using different lingos for this new os version testing but it's basically a pre beta testing on the os minimum supported version and resolution so basically if you are supporting let's say for example your company support supporting android 6. so we need to test on one device which is minimum supported if your company is supporting android 7 you need to test on any one device on android 7. similarly it goes for ios if your company is supporting maybe ios 9 you need to test your application on at least one device in ios 9 and based on region where the user is located so this is like something say for example your application is more widely used in europe so definitely you are not going to test it based on the user based in any other continent maybe australia you need to organize your testing strategy so that you are targeting the region where your user is located if 70 of the user are in europe then you are going to test based on the devices which your user are using in your euro okay so simulator versus emulator but i'm not sure how many of you are aware like what is simulator what's his emulator and also there is lot of confusion around this topic but in just two lines i will be explaining it what is simulator and what is emulator okay so simulator very simple concept anything which is related to software it is simulator emulator once we are getting hardware plus software plus os it is an emulator so it's a very simple thing to remember simulator is a software humiliator hardware plus software plus os so when it comes to emulation versus simulation humiliation duplicates while simulation replicates a real device in a virtual environment humiliation imitates behavior closely simulation mimics behavior of a real device but doesn't necessarily match it exactly both are useful in app testing in addition to real devices so you know like buying a real devices it's not feasible for every organization they need to rely on simulators or emulator because if you tend to buy the real devices how much devices you are going to buy it won't be a cost effective approach for your organization so you need to rely on simulators or emulator i believe this is like the overall just like how mobile application testing is working and what are the certain conditions we need to take here in mobile application testing and there can be a different aspect like how you are testing so i haven't shared those things in much detail but this is the starting point from where you can start testing your mobile application so i would like to give my i would like to share share the screen with nathan so you can start and share the experience yeah i hope you like this uh session thank you thank you so much saif it was so informative uh and i like the handy tips which you shared actually the five tips which you shared right so that one was quite good thank you thanks a lot thank you uh we can wait for questions uh so if anyone has questions uh please put over it in a chat section or you can use the questions tab as well oh if you want to share your thoughts or experience with us maybe we can uh give you access to the screen i hope i was it fast no it was on the right page actually hi i'm here yeah hi can you guys hear me yes yeah you thought i liked i like i like all all the slides and your information it really gives a new angle to me in terms of information uh i have one question actually in terms of the device metric you when you have selected set of devices that you want to test let's say you have iphone 12 10 and up to eight right maybe you know you choose android 11 and 10 those kind of things right how do you actually build the infra to test all the possible permutations of handphones that fit this requirement you can try to share in general yeah yeah i got your uh question but the fact here is like there isn't one specific strategy but the best thing that you can do is if you are using any analytics management tool like google analytics or something like that you can get some good idea like which users are using which devices and apart from that which os version is being used and also some data like if any new os version is coming in the market you won't be having data for that but you do have some data from your product itself from maybe you can try asking like from the product team like which devices are widely used for your product and in which market thereby you can just define and narrow down your testing strategy for creating the device matrix and then say for example around 60 percent of the users are using ios 12 and around 10 percent of the users are using ios 11 so i don't feel like if you are having a very small time you need to test across ios 11 the testing across ios 12 should be sufficient if you are not having that much of time likewise you need to create for different os versions and different resolution so the two thing which you need to take care of when creating a device matrix is the os version and the resolution apart from which model oem you are using like you are using samsung or maybe you are using xiaomi these three two three things you need to take care while creating the device metric i hope i was able to answer you i mean maybe if you want uh yeah but but when you have narrowed this down do you actually then test your actual device or you know you go out to and get services that sort of like emulate your ass something like that i mean what's the next step in when you when you get down there so basically that also depends like if your organization is ready to churn out some money for cloud devices or not and if they are not ready and if they are also not ready to go for real devices then you can just use simulators from the i mean you can just use adb studio to create android simulators or maybe any other uh simulators available and xcode to create io simulator because most of the time the free version of the simulator it or maybe real devices on cloud it is not available and even if it is available it is for like 30 minutes or 20 minutes so the best idea is try to uh test it on the simulator itself and if you are having the device you can test on the device also uh yeah this i have is on the first upgrade testing whenever it's a type of testing actually so i'm just wondering what happens to the phone that that that isn't upgraded it's not able to be upgraded are you guys i normally still support that or does the user get certain functionalities based on the upgrade or something yeah actually what happens with that so it's like it depends how you are handling the application if like you are just totally neglecting the application then you will maybe just get a simple message that move on to any new device or any new version depends like if you are not supporting the versions um maybe your application you just need to freeze it or something like that but most of the time what i have seen they are just displaying the messages that this phone is not compatible with uh the app version something like that yeah okay got it so in summary uh it depends on the product owners if they want to support they give limited limited ability if not they just say yeah yeah so most of the time they will totally dismantle it and they are not going to support because even supporting a minimal functionality that is also kind of a bit of troublesome so they are not supporting that also yeah you understand making more courses okay all right that's it from me thanks yeah thank you amir thanks samir uh okay so we got some questions uh from our joiners so uh okay from nasi so he's he want to know like how uh so in web we have inspect element right so you wanna know how to do the same in mobile testing so how you find errors and debug like similar to inspect element in web app yeah so basically like once you are inspecting the element this is like kind of automation that you are trying to achieve i personally believe so for inspecting the element we need to know that what kind of automation you are trying to do like you are doing which tool you are using you are using apm or maybe you are using the talks automation monkey talk or maybe any other uh automation tool which are present so like ios and android also provide their native automation tool so in order to inspect any element you just need to suppose for example you are using apm there is an apm inspector which you can use in order to inspect any element so likewise i believe every automation tool they have their own inspector for inspecting the element yeah i guess his question got one more point uh so uh he was trying to convey like inspect element option right so the inspector option so it will have like network tabs or something i guess he is asking about that so how can we check the error like how we check error from inspect element in web back inspect element in web app actually for web apps it's like similar to how you are using the chrome browser or you maybe you are using any other tool so i believe it can be used in that way so web application maybe you are opening on the application and you can directly use the chrome tool if you want to expect inspect all these things yeah yeah okay so uh all right so the next question violeta has one question so when you have limit of time to test mobile app do you have any plan or order what to do first and in which order you suggest okay so this is a good question most of the time it's like happening we have a very short released testing time so in that time what we can do we can i mean it comes from experience also like which test case you want to execute apart from that what is going to be your testing strategy so if you take my personal opinion what i do i just test on the very recent version of the os on any device say for example i will just pick up android 10 with samsung and apart from that i will just pick up minimum supported version of the mobile application and say for example minimum supported is around android 6 for android and android 9 for ios so i will pick those two device with the application and i will start executing the test cases yeah okay that sounds good hope uh you answered the question and the next one is can we uh can be done mobile performance testing without deep knowledge of test automation actually there are a lot of tools available in the market which can help you generate some metrics for mobile applications but if you are having a good understanding of using the android studio and xcode it will help you to better analyze the performance so i mean coding is not necessary in that situation but you should know how to use android studio and export okay okay make sense and the next one is any examples of interesting bugs you found during testing mobile apps uh which we can take into account okay uh so there are a lot of bugs maybe last time when i was working for one of my clients so we used to have sdks sdks are basically in third party integration tool and software development kit so that are integrated so any payment you can say it's a kind of in a third party tool so there was an issue once i was entering the cvv number it was not a mandatory field but in the sdk there was some bug so once i was entering the sdk uh sorry the cbv number in the payment gateway on um maybe in debit or credit card so it was crashing the application so you see the issue was from the third party and it was causing my application to cash so these kind of issues do come into pictures once you are working with multiple micro services and multiple third party sdks and these kind of things yeah okay okay and one more question when we released an app i found out about some bugs from the customers that it even did not come from come to my mind do you have any tips for test strategy or any risk assessment you have in your work which can help to come up with this idea okay so basically if i believe if you are doing functional testing and you have automated all your manual test cases and your automation test case is also working fine then the issue which will come from the customers side it will be most of the time the compatibility issues maybe something is not working on ios 11 or maybe some button is not working on android and 9 but functionality won't be broken on all the os versions and these kind of things so this is very hard to define like okay if any how you can i mean you cannot go and just test on all the device fragmentation and os so it's kind of impossible but the second thing which i would like to add to your question is like maybe if you are using any crash management tool like crashlytic or firebase or sentry dot io you can just take out the crashes which are coming on most of the devices like say for example any crash is i'm coming on android 9. so all the logs are there in this lock management tool you can just go try replicating the steps and then you can ask the developer to fix the issue okay okay uh hope uh scythe answered your question so all the questions are moved to answered section yeah one more to go how to answer during interview professionally on a question what the what is the difference in testing web and mobile app so it sounds interesting yeah it's an interesting question like most of the time i have also got some questions like what is the difference between testing android app and ios app so in short like i would like to say my personal opinion is like whatever we are testing we are testing to make our consumers happy to make our clients happy and in terms of technical difference i would say that there are different set of tools which are needed for mobile application and maybe there are some different set of tools and strategies for web application but the short goal is to achieve the quality of our product so that our consumers are happy and we are getting more leads and yeah this is what i personally believe okay that's good uh i believe like the we can wait for one more minute for any questions further after that we can move to the next segment which is 99 second talks do you guys have any more questions yeah there is a thanks from violet okay so yeah we can move to the next segment which is 99 seconds talk so if anyone want to chip in and share their thoughts or uh anything you can just raise your hand and we will give you access to the screen we still got time 12 minutes so the stage is yours i guess everyone is shy no one is raising their hands yeah i think it's the time if you guys are having any questions or maybe any confusion you can just ask anything all right okay so i will hand over so one interest is there yeah she will be joining hey hi hello hello hello yeah are we audible uh yeah i just uh would like to tell thank you for this presentation and for the answers and uh in in such a short amount of time thank you for the structure of your talk and for this great point i made a screenshot and and now i understand that i need to deep um to dive deeper to this um topic and thank you for this possibility and for answering my question thank you guys a lot thank you thank you thanks for joining thank you thanks a lot so anyone else want to ship in uh nasir i can see one of your comment uh do you want to chip in and share what you were trying to ask scythe asking you said if you arrange a session of live demo for mobile testing that would be great okay uh maybe we will see in future if ministry of testing is interested for any kind of live demo i will try to do that yeah yeah we are interested yeah we will keep this in mind yeah we will keep that in mind one more question uh yeah any testing techniques that you use specially for mobile testing okay so this is a good question but not many are using but if you want to utilize any mnemonics you can use that so there is one mnemonic like i sliced up fun i don't want to go against each uh what it means but it's like i means interruptions slice for sliced in s it means store so likewise each alphabet means something and it will help you to strategize your mobile application testing i think you should just go on the web and just search for i sliced up fun and it is a very good technique to remember what kind of functional and non-functional testing you can do for mobile applications that's a great tip that's a great yeah i will just write it there yeah sure please okay so yeah uh so is there anyone else wanna chip in or ask any questions otherwise we can wrap it up uh okay so nasir is asking how can we do regression testing for mobile uh so basically the approach will be same like how you are doing on web application but you know you cannot use all the different os and the device and oem so you need to restrict your regression and what i personally do i same again i just pick around one or two major devices from both android and ios os and then i start doing regression so the major functionality i test on any one or two devices and all other minor test cases and minor regression test cases i am just doing on maybe any one application or two sorry one os device or two os device not more than that yeah because at the end of the day you don't have that much time that you can do all your say for example if you are having around 1 000 or 2000 regression test cases you cannot just go and do it on all devices that's not possible yeah correct correct we have to segment it based on our user base and all yeah right uh so the next one do you have you are getting a lot of questions guys [Music] do you have examples of mobile app which can be used as good examples when developing mobile app uh so it's a basically a broad question so events we are developing mobile application we keep in mind our user and the audience engagement that we want to have so the application if it is social it will be having some different uh strategy if it is like in hospitality it will have different uh but if in short you want to pick up any three four five good apps i think facebook instagram and apart from that there is one airbnb for the uh booking of rooms so this kind of application you can just play around and try finding out like if you can find any bug for these kind of things yeah okay and one next one is on can you tell me about accessibility points which can be tested in mobile apps anything special uh not really i mean any application you are testing you just need to see that everything is looking good and you are able to uh find you are not able to find any issues when you are performing and even accessibility also like there are a lot of conditions and criteria that how you want to test how you want to approach your testing so it all depends like who your end audience is and what is your goal okay okay cool uh okay uh for my curiosity i got a question for you so you explained about simulators and emulators right and we do have some uh cloud platforms which offers devices right right right so based on your experience uh which one you suggest like uh out of four like real devices emulator simulators and cloud uh which one you prefer to do your testing okay so most of the time i am doing my testing on real devices like the major application testing that we are doing for our uh users it is on real device so for example i am testing in malaysia market so most of the time the malaysia market is having around 60 to 70 percent of any specific ios version i am just trying to follow that technique that on real device i will test everything but if there are any issues or maybe the device is not available i am trying to go for simulator also so it's a mix and match kind of thing it's not like very hard and fast that i will only test on real device it's nothing like that okay it depends on the situation you would like right yeah yeah got it got it and any resources we can read or listen to broaden our knowledge in mobile testing okay so actually i was going through mobile the ministry of testing website and they have lot of resources so if you want you can just go through them and try searching with the keywords mobile testing mobile automation and they are also having a slack channel ministry of testing is having a slack channel and in that uh slack there is one mobile testing channel you can just go there and there are a lot of questions coming in there so it will help you to increase your knowledge yeah yeah correct uh so i guess there is a dojo course on mobile testing as well so maybe you can check it out and there are several podcasts we uh i hope there are no questions the question stops are cleared up uh do you guys have any any other questions in mind to ask i i guess it's yeah all right thanks a lot yeah cool yes yes yeah i guess the questions are over thanks thanks for your interesting session and we are looking forward for the live demo session which you are planning to do yeah thanks yeah thank you thanks a lot so uh the next meetup is on 12th january 2021 so we will see you after the new year uh if you are interested if any one of you are interested to submit a talk or something just reach out to me or ram or ami so we will help you to get it done awesome yeah thanks nathan for hosting us yeah it was very good meeting with you thank you thank you thanks a lot thanks for your time and like sharing your knowledge with the community thank you thank you thanks everyone have a good day bye bye bye everyone

Channel: Techworld with Saif

Views: 4,799

Keywords: Software Testing, mobile app testing tutorial, app testing, iphone testing, android testing, mobile testing, mobile testing training, mobile testing tutorials, mobile testing for beginners, how to test mobile devices, mobile emulator, mobile simulator, testing android applications, testing iphone applications, testing apple device, overview of mobile testing, emulator vs simulator in mobile testing, types of mobile testing, software testing of mobile apps

Id: Z1luZiDWRsA

Length: 45min 3sec (2703 seconds)

Published: Sat Jan 16 2021