Personally I always get a bit concerned about "what should I test" questions around security testing, because if you need to ask, you really shouldn't be doing security testing.
That said you need to start with a threat model do determine the potential attack vectors and then proceed from there. Your application really needs to follow some form of Security ...
Firstly you need to become a member of Apple's developer program, and understand how in app purchase works. As a starting point you should look to Apple's documentation here: https://developer.apple.com/in-app-purchase/.
Apple provides sandbox environments to facilitate testing, and it is all covered in the documents and past WWDC sessions.
Once you ...
Create an appleID:
and use free provisioning:
Which states that Free provisioning allows developers to deploy their Xamarin.iOS application to their iOS device without being part of any Apple Developer Program
See details here.
You can try this tools:
Disclaimer: I'm author of the second one :-)
I am working as a functional engineer in qa outsourcing company, where we provide qa services to the offshore companies. We work on both automation & manual testing and clients (Development Team) always ask us for the Crash logs, so that they can easily debug the issue.
Following are the steps, that we follow to get the crash logs:
Install iTools (...
There will be differences between emulators/simulators and actual devices. Android emulators just emulate the screen size and pixel ratio and run a stock version of Android. Many of the major devices run their own custom version of Android. For instance, any Samsung Galaxy runs it's own version of Android which contains Samsung software to promote people ...
Test cases that are based on its specs:
Video should be available to all iOS users; this spec is not very clear.
Does your application have some kind of account sharing feature?
Or it simply means as long as a user has got an iOS device, this video feature is available to them?
Test case, since it is not really practical to test on every iOS device, I ...
You can figure out the possible test area by asking a few questions to your team. Such as how many products should be offered, what their prices are, and if their purchase is restrained in some way (time window, inventory limit, account status, etc). From this you can start making tests that canvas the in-app purchase functionality.
Currently I also test a app with notifications and after upgrading the app, the badge count is still present. The app control the badge.
An application is responsible for managing the badge number. If the application does not clear the badge, the push message(s) will remain in the notification center. After an application receives a push notification, it ...
First of all you would need a sandbox user for testing In App purchase. Once its available you can start testing. I would like to mention some of the test cases I followed for In App Purchase:
Check if user is able to buy the app on entering correct credentials
Check user is NOT able to buy the app on entering incorrect credentials
Check the status of the ...
Testing with old versions makes little sense. Only do it to familiarize QA team with new features (if changes are not radical), and develop testing protocols and tools.
To deal with changes in system to be released, we use "soft freeze" and "hard freeze".
During "soft freeze" changes in released software need to be approved by QA (and are evaluated for ...
As per the developer documentation on Apple's website:
The following scenarios are common causes of leaks, you can confirm whether your observations are actually memory leak??
Retain has been called on an object without a corresponding release call when the object is no longer referenced.
An object has been allocated and initialized with APIs that don’t ...
I don't specifically know any security testing tools for mobile, but I wouldn't rely on them because you won't learn security testing by only using tools. Try to manually test for security vulnerabilities. This won't be easy. First, try to understand the mobile architecture, not only the application. Then learn to use the debugging tools. For example, ADB on ...
Many passive scanners exist to give holistic views of both a device and services running on it. So, while running a scan against a device with the application running and its ports open will give you a little bit of info, likely it will lead to many rabbit holes that will eat additional time.
What I would do to start (as if that counts for something), is ...
Maybe you can make it working with Xamarin or the new Visual Studio for Mac (which is in Beta).
Here is a blog about Selenium with C# on a Mac with Xamarin: http://testerstories.com/2015/11/c-and-selenium-on-xamarin/
Microsoft is supporting C# in Mac with its new .Net Core: https://docs.microsoft.com/en-us/aspnet/core/tutorials/your-first-mac-aspnet
What you have here is a classic case of whether the ROI makes the effort worthwhile. You can find recent release notes on Wikipedia, as well as the Apple developer library.
Considering how many releases of iOS there have been since iOS 8 first appeared, one critical issue is not a bad track record.
Unless your apps deal with financial or other critical,...
Yes, iOS manual testing is supported by Bitbar Testing (Testdroid). iOS Manual testing was introduced during the end of the year 2016 and currently, it's supported by dedicated devices and Private/Enterprise installations.
For more information use URL 1 or URL 2
Yes, you have pointed out clearly that the chat application meant for both web and mobile devices.
An application which is responsive has different UI views based on the environment in which it is opened up.You can write test cases for web portal first and
then clone the test cases for mobile devices for execution.
Straight forward Answer: As Appium is a cross-language tool for mobile automation & it's independent of product language developed. you can use any language listed below.
I am not able to decide which language should I use with Appium to
automate this app.
But the answer to this question is not straight forward: ...
You can save 90% of the time if you just use testRigor instead of Appium. It runs in the cloud and all you need to do to kickoff new tests is just to upload (via UI or API) a new version of your app.
Disclaimer: I'm a co-founder of testRigor.
First option you have is to ask your developers to create a version of the application without ads.
Advantages - No ads.
Disadvantages - You will not be testing the exact same code as you plan to release.
You can disable only fullscreen ad.
I think there is no best way to do this. Stable automate checks or checking the exact same code as you plan to ...
Check your battery status for iOS: Go to Settings → General → Usage Usage. Under the section at the top labeled Battery, tap Battery Usage. Check usage and stand by status in that you can view last charger time and remaining percentage.
iPhone 5s battery life 10h 57m 24s.
Check your battery status for Android:
The apps home screen gives an adequate quick-...
It is important to note the difference between system under test versus test system failures.
It is also important to assess this risk as early as possible during test planning.
General rule is to test in the known functional test environment that is as up-to-date as possible. If the risk materializes that new relevant 3rd party software releases during ...
Run the App in an iOS simulator that comes with Xcode, then test with selenium.
What you also could consider is using Appium, which is quite similar to selenium.
Included blogpost has a very detailed explanation.
Well it depends, and to get the best answer you will have to decide where and how do you want to look at packets.
The best place to look for packet loss is the application itself since packets can get lost inside the application or on their war from the OS network stack to the application. Skype for example shows some of this information in the "Call ...