App Test induction

Test an app that mainly includes the following points:

I. Test resources: 1. Product Functional Requirements Document 2.  Product prototype Figure 3. Product 4. Behavioral statistical analysis Definition document 5. Test equipment (ios3.1.3,android4.0 ...) Other

Two. Daily newspaper and product launch report:

1. Testers are required to send test daily to test project daily

2. Daily content includes:

----Rating the current beta version quality

----An example of a more serious problem, prompting developers to first modify

----evaluate the overall situation of the version

3. Before the product goes live, the tester sends the product on-line report

4. The Product Launch report includes:

---quality grading for the current version

---attached test report (Functional test report, Compatibility test report, performance test report and app available performance standard results)

Three. Functional testing:

Testers need to perform pre-manual tests (Black-box testing) and post-test automation to implement and evaluate the functional testing process in the following ways:

1. Use the time, place, object, behavior and background five elements or business analysis methods to analyze and refine the user usage scenarios of the app, compare instructions or requirements, complete

Develop internal or external and pulmonary functions directly related to the needs, build test points, and clear test criteria, if not explicitly followed, reference to international standards

2. According to the characteristics of the tested function points to list the appropriate type of test cases to cover them, for example: the place involved in the input needs to consider equivalence, boundary, negative,

Exceptions, illegal, scenario rollback, test types such as associated tests are overwritten

3. Track test implementation and requirement input coverage at all stages of the test implementation, and remediate business or demand understanding errors in a timely manner

Available automated test tools include: IPhone WebAPP, Andriod

Four. Performance test:

Evaluate the app time space characteristics, the main parameters are: CPU, memory, power consumption, traffic, FPS (transmission frames per second), app installation time-consuming and startup time-consuming;

Performance testing includes client performance testing and server-side testing

1. Client Performance Testing

1). Load test: Verify that the app responds correctly at various boundary pressures such as battery, storage, speed, etc.

Install the app---memory is full

---CPU, when the memory is too high, whether the app will run properly, will be prompted

---Disconnect the network while running the app

2) Responsiveness test: Test the application in various operations to meet user response time requirements

---The response time for installation and uninstallation when memory is full

---the time impact of various functional operations of the app

3) Stability test: Under repeated/long-term operation, the system resources are not occupied by the exception

---app to load and unload repeatedly

Repeat Operations---other functions

---app runs more than dozens of hours in a row

After these operations, check the resources when the exception

4) Performance evaluation: Evaluate the usage of system resources in typical user scenarios.

5) Benchmark Test (baseline test): Benchmarking with competitive products, product evolution comparison test, etc.

Server-Side testing:

1) Single-machine capacity test: can detect the single-machine server in 90% of the response time and success rate are the premise of compliance, can carry how many users

2) 24-hour stability test: 24 hours with a specific model, no restart of the server, no memory leaks, and success rate of each transaction

Five. Compatibility test

Main test for internal and external compatibility

1) compatibility with local and mainstream apps

2) based on the different development environment and production environment, the test under each system, the behavior is consistent (considering different operating systems, different phone resolutions and different mobile phone brands)

Six. Safety testing

The app requires detailed security testing before it goes live. Security testing is mainly to detect whether the application is easy to be cracked, whether there is a risk of malicious code injection, on-line

After the high risk of external plug-in specific include

1. Software permissions

1) Charge risk: Send SMS, call, connect network

2) Disclosure of privacy risks: access to Mobile information, access to contact information

3) Restrict/allow use of mobile phone to read/write user data

4) Detection of user authorization levels, data leaks, unauthorized access to the app, etc.

......

2. Install and Uninstall security

1) The application should be properly installed on the device driver

2) Ability to locate the appropriate icon for the application on the installation device driver

3) whether to include digital signature information
4) all managed properties and their values contained in JAD files and jar packages must be correct
5) The data content displayed by the Jad file should be consistent with the content displayed by the application
6) The installation path should be able to specify
7) without the user's permission, the application cannot be pre-programmed to start automatically
8) Whether the uninstall is safe, and whether the files installed in it are all uninstalled
9) Whether the files generated during user use are prompted
10) Whether the modified configuration information is restored
11) Whether the uninstall affects the functionality of other software
12) Uninstall should remove all files

3, data security

4. Communication Security

5 Man-Machine interface security

6. Network security

Seven. UI Testing

Test the layout of the user interface (such as menus, dialogs, windows, and other customizable controls), whether the style meets the customer's needs, whether the text is correct, the font, whether the page is beautiful, and whether the operation is friendly

Includes: User-friendly, humanized and easy to operate test, specific as follows

1 Navigation test

1) Buttons, dialog boxes, lists and windows, etc., or navigating between different connection pages
2) is easy to navigate, navigation is intuitive
3) Whether a search engine is required
4) navigation help is accurate and intuitive
5) The style of navigation and page structure, menu, Connection page is consistent

2 Graphics Testing

1) Horizontal comparison. All controls operate in a uniform manner
2) Adaptive interface design, the content according to the window size adaptive
3) page label style is unified
4) Whether the page is beautiful
5) The picture of the page should have its actual meaning and require the overall orderly appearance
6) Picture quality is high and the picture size should be as small as possible when the design meets the requirements
7) The overall use of the interface color should not be too much

3 Content Testing

1) Input box description text content and system function is consistent
2) Whether the length of the text is limited
3) Whether the text content is unclear
4) Whether there is a typo
5) Whether the information is displayed in Chinese
6) Whether there are sensitive words, keywords
7) Whether there are sensitive images, such as: copyright, patents, privacy and other pictures

Eight. Server Disaster tolerance test

The main point is whether a server process crashes and has the ability to recover itself. For example, if the logic process disappears, will it automatically pull up when the game app is gone?

If the memchached crashes, does it restart and does it affect the player?

Nine. Non-functional testing

Before the mobile app is launched or further developed, testers have a role to follow. The first test to be performed in the early stages of development

is a usability test, with an alpha user or person

10. After-line public sentiment tracking

After the new app is online, the user reviews the app, what bugs are undetected during the test, and what the App Store's top posts for the app are on the forum ...

App Test induction