How to Test Android Applications – part 2

In the previous article, we learned 4 cases for how to test Android Applications.

In this article, we will learn more cases for how to test Android Applications.

5. Compatibility testing test cases

Compatibility testing is performed to protect against mobile application failures as devices have different operating systems, sizes, resolutions, and so on. Determines that an app works consistently across various platforms and environments.

Six compatibility test case scenarios questions:

1. Have you tested on the best test devices and operating systems for mobile apps?
2. How does the app work with different parameters such as bandwidth, operating speed, capacity, etc.?
3. Will the app work properly with different mobile browsers such as Chrome, Safari, Firefox, Microsoft Edge, etc.
4. Does the app’s user interface remain consistent, visible and accessible across different screen sizes?
5. Is the text readable for all users?
6. Does the app work seamlessly in different configurations?

6. Security testing test cases

Security testing ensures that the application data and network security requirements are met per the guidelines. It focuses on identifying possible risks and security vulnerabilities so that the application is not exploited and the data is protected.

Twenty-four security testing scenarios for mobile applications:

1. Can the mobile app resist any brute force attack to guess a person’s username, password, or credit card number?
2. Does the app allow an attacker to access sensitive content or functionality without proper authentication?
3. This includes making sure communications with the backend are properly secured. Is there an effective password protection system within the mobile app?
4. Verify dynamic dependencies.
5. Measures taken to prevent attackers from accessing these vulnerabilities.
6. What steps have been taken to prevent SQL injection-related attacks?
7. Identify and repair any unmanaged code scenarios
8. Make sure certificates are validated and whether the app implements certificate pinning
9. Protect your application and network from denial of service attacks
10. Analyze data storage and validation requirements
11. Create session management to prevent unauthorized users from accessing unsolicited information
12. Check if the encryption code is damaged and repair what was found.
13. Are the business logic implementations secure and not vulnerable to any external attack?
14. Analyze file system interactions, determine any vulnerabilities and correct these problems.
15. What protocols are in place should hackers attempt to reconfigure the default landing page?
16. Protect from client-side harmful injections.
17. Protect yourself from but vicious runtime injections.
18. Investigate and prevent any malicious possibilities from file caching.
19. Protect from insecure data storage in app keyboard cache.
20. Investigate and prevent malicious actions by cookies.
21. To provide regular checks for the data protection analysis
22. Investigate and prevent malicious actions from custom-made files
23. Preventing memory corruption cases
24. Analyze and prevent vulnerabilities from different data streams

7. Localization testing test cases

Localization testing ensures that the mobile app provides a flawless user experience in a specific locale based on the target language and country. It aims to ensure that the functionality and content of the application is fully tailored to meet the needs of users in a particular location. Since fully localized apps and websites outperform their competition, this is a test case that shouldn’t be overlooked. Partnering with a respected third party with global reach alleviates some stresses and unknown variables when using localization. For example, Testis covers over 100 countries and over 140 languages.

Eleven localization testing scenarios for mobile applications:

1. The translated content must be checked for accuracy. This should also include all verification or error messages that may appear.
2. The language should be formatted correctly.(e.g. Arabic format from right to left, Japanese writing style of Last Name, First Name, etc.)
3. The terminology is consistent across the user interface.
4. The time and date are correctly formatted.
5. The currency is the local equivalent.
6. The colors are appropriate and convey the right message.
7. Ensure the license and rules that comply with the laws and regulations of the destination region.
8. The layout of the text content is error free.
9. Hyperlinks and hotkey functions work as expected.
10. Entry fields support special characters and are validated as necessary (ie. postal codes)
11. Ensure that the localized UI has the same type of elements and numbers as the source product.

8. Recoverability testing test cases

The recovery test is a non-functional testing technique that determines how quickly a mobile application can recover after a system crash or hardware failure.

Five recoverability testing scenarios questions:

1. Will the app continue on the last operation in the event of a hard restart or system crash?
2. What, if any, causes crash recovery and transaction interruptions?
3. How effective is it at restoring the application after an unexpected interruption or crash?
4. How does the application handle a transaction during a power outage?
5. What is the expected process when the app needs to recover data directly affected by a failed connection?

9. Regression testing test cases

QA and mobile app testing doesn’t end once an app is launched. When an application is updated, even small changes can create unexpected problems. This is why regression testing is key. The purpose of regression testing is to ensure that new code changes in the software do not cause errors or interruptions.

Four regression testing scenarios for mobile applications:

1. Check the changes to existing features
2. Check the new changes implemented
3. Check the new features added
4. Check for potential side effects after changes start

That’s it. If you want a good application, take these tips and follow cases for Android Application test. It will help to make quality & standardize your Applications.