APP Test (i)

Before you talk about app testing, let's talk about the current app's operating system and app-related basics.

I. App Basics

1. Operating System #

Now the mobile operating system mainstream is divided into two types of :(1) Android (2) iOS system.

2. Android System #

Linux system-based kernel for the development of open-source operating systems, Android applications are generally written in the Java language, the package suffix name is. apk, the highest permissions require root.

3.IOS System #

The package suffix named. IPA, development language involves C,object-c,swift,c++, etc.

Web servers on the 4.app are now most commonly used by Nginx, the database is the most used MySQL.

5. Most of the current app tests are agile development tests, and the time to update iterations is mostly three weeks.

Two. App Test points #

The summary draws a mind map, as shown in

I. Functional Test points

1. Running

2. Registration

3. Login

4. Start

5. Front and rear switch of the application

6. Free Login

7. Data Update

8. Offline browsing

9. Positioning, camera service, etc.

10. Time Test (whichever is the server time)

11.Push test, is to push the app information to the phone

and other points, etc...

Two. Safety Test points

1. Whether sensitive information is encrypted and analyzed with the grab kit tool

2. Password is too simple to check

3. Important data, such as the payment password will not be saved to the device, will not be decrypted

4. The same account login at different terminals, whether there is a hint

5. Do you have any prompt for remote login?

6. Whether the system allows multiple illegal logins, is there any hint

7. Restricting or permitting the use of certain functions of the mobile phone

8. Whether the registered verification code can be reused and whether there is a timeout limit

9. decompile, convert the compiled data into source code, and then tamper with the program

10. Protocol fetching, that is, after the code is decompile, the implant illegal program crawls the user and the server communication information, thus obtains the user data

And so on other security test points, here to add a free Android scanning platform, Baidu Love encryption can.

Three. User Experience Testing

To perceive the comfort, usefulness, ease of use and friendliness of a product or service in the perspective of a subjective, ordinary consumer.

Four. Cross-event testing

A conflict test is a test in which a feature is executing while another event or operation interferes with the process.

Five. Compatibility test

1. Compatibility with local and mainstream apps

2. Compatibility of different operating systems, whether they are compatible with

3. Screen resolution compatibility for different mobile phones

Wait, there's some.

Six. Performance testing

The performance test of the server and the performance test of the mobile terminal

(Attention: CPU, memory, upload traffic, download traffic, battery usage, etc.)

Seven. Install, uninstall, upgrade test

Eight. UI testing

Prototyping and contrast testing

Having said so much, let's talk about a simple process of measuring my app.

Before testing, familiarize yourself with the app's prototyping and business needs and identify the test points.

After the app has been developed, do a smoke test to see if the basic functionality of the software is available, and if so, do functional testing, UI testing, compatibility testing, cross-event testing, installation and uninstallation upgrade testing, and so on.

By the way, here are a few questions that friends often ask about before.

App FAQs Summary

The difference between 1.APP testing and web testing

The app has to switch between front and back, no landing, cross-event testing, traffic and battery testing, interrupt testing, and so on, and these Web tests are not.

How to simulate the weak network environment of 2.APP

Using the Grab Bag tool fiddler simulation of the Weak network environment, how to simulate, in the future will be described in the Fiddler topic.

3.APP test How to determine the front-end or the background problem

Fiddler grab bag with grab kit 1. See if there is a problem with the requested parameter, the problem is the front end problem 2. See if there is a problem with the response parameter returned, the problem is the background problem

APP Test (i)