Importance of performing app performance and security testing-software testing

How to make a user feel that the app is running faster, which requires performance testing of the app. The factors that limit the performance of the app are divided into app itself and the backend services that app needs to use.
Test the speed at which the app connects to the network
Typically tested in mock mock environments, the test method uses more time to add timestamps to the app's log, such as using Apple's iphone Configuration Devices console in utility to view the app log.
Test how the app operates at different network speeds
Tests can be validated using the timestamp method in the app's log, or you can verify the user's experience with app performance by using the intuitive experience of the app.
Test the performance of the app for front page rendering
Tests can be validated using the timestamp method in the app's log, or you can verify the user's experience with app performance by using the intuitive experience of the app. Specifically, when using WebView in the app, testers can quickly refresh the current page or switch between pages using WebView to verify whether the app has a performance problem or even crashes.
Test the performance of the app operations database
The iOS operating system uses CoreData or SQLite databases when it stores app data locally; The Android operating system uses the SQLite database when the device stores app data locally. If the operation of the volume of data is very large, it is possible to have the performance of the app, the app test is very important, the database operation of the function of a large amount of data testing. Testers can also work with developers to improve database performance in accordance with some of the principles of web-side database optimization, such as database-enabled transactions, indexing, and bulk manipulation of data.
Test whether the app has expired settings for session sessions
For a test of the expiration of app session sessions, switch to another app or desktop for a period of time in the app run, and then go back to the app to see if the app needs to enter authentication information such as a password. It is worth noting that the reasonable session expiration time of different app is not the same, the tester needs to work out a reasonable test case with product manager and developer.
Test whether the app request contains plaintext user information
Information that contains plaintext, as in the app, which indicates that the user should use a transcoding such as a UUID or GUID, rather than a direct user phone number or account information, and certainly not the explicit transmission of the information. Testers can use Apple's iphone Configuration utility,android SDK's Ddms,charles and fiddler tools to monitor requests sent by the app.
Test whether the app's request is encrypted
General app requests can use HTTP, but the request that relates to user sensitive information needs to use encrypted transmission such as HTTPS.
To test the storage security of the SQLite database
Testers can connect to Root's Android snakes via ADB and use SQLite to view specific database-saved information. Obviously, it is not safe to store the user's actual login information in the database file, it is best not to store it, if it must be stored, it is best to encrypt the information and then store it.
Test the security of the app using WebView
Because the WebView request is the same as the request data on the Web side, any attack method and vulnerability that applies to the web side is common to webview.
More articles go to how to get users to feel the app running faster, which requires performance testing of the app. The factors that limit the performance of the app are divided into app itself and the backend services that app needs to use.
Test the speed at which the app connects to the network
Typically tested in mock mock environments, the test method uses more time to add timestamps to the app's log, such as using Apple's iphone Configuration Devices console in utility to view the app log.
Test how the app operates at different network speeds
Tests can be validated using the timestamp method in the app's log, or you can verify the user's experience with app performance by using the intuitive experience of the app.
Test the performance of the app for front page rendering
Tests can be validated using the timestamp method in the app's log, or you can verify the user's experience with app performance by using the intuitive experience of the app. Specifically, when using WebView in the app, testers can quickly refresh the current page or switch between pages using WebView to verify whether the app has a performance problem or even crashes.
Test the performance of the app operations database
The iOS operating system uses CoreData or SQLite databases when it stores app data locally; The Android operating system uses the SQLite database when the device stores app data locally. If the operation of the volume of data is very large, it is possible to have the performance of the app, the app test is very important, the database operation of the function of a large amount of data testing. Testers can also work with developers to improve database performance in accordance with some of the principles of web-side database optimization, such as database-enabled transactions, indexing, and bulk manipulation of data.
Test whether the app has expired settings for session sessions
For a test of the expiration of app session sessions, switch to another app or desktop for a period of time in the app run, and then go back to the app to see if the app needs to enter authentication information such as a password. It is worth noting that the reasonable session expiration time of different app is not the same, the tester needs to work out a reasonable test case with product manager and developer.
Test whether the app request contains plaintext user information
Information that contains plaintext, as in the app, which indicates that the user should use a transcoding such as a UUID or GUID, rather than a direct user phone number or account information, and certainly not the explicit transmission of the information. Testers can use Apple's iphone Configuration utility,android SDK's Ddms,charles and fiddler tools to monitor requests sent by the app.
Test whether the app's request is encrypted
General app requests can use HTTP, but the request that relates to user sensitive information needs to use encrypted transmission such as HTTPS.
To test the storage security of the SQLite database
Testers can connect to Root's Android snakes via ADB and use SQLite to view specific database-saved information. Obviously, it is not safe to store the user's actual login information in the database file, it is best not to store it, if it must be stored, it is best to encrypt the information and then store it.
Test the security of the app using WebView
Because the WebView request is the same as the request data on the Web side, any attack method and vulnerability that applies to the web side is common to webview.
　　The article goes to 51Testing Software Test Network (http://www.51testing.com), more test articles please go to the 51Testing Software test network.