Chapter IX app project test (1)

9.2 APP Testing process

APP The whole R & D cycle of is generally in 2~3 About a month or so , It is determined according to the complexity of the product , The test cycle is generally 1~3 Around the week , The test engineer is required to be familiar with APP The whole testing process and method ,APP The test process is as follows ：

1、 Planning phase

Confirm the product requirements document 、 Prototype design 、 Interface documents and related documentation , Plan the test plan of the project according to these documents , Sorting out test ideas 、 Finally confirm the test equipment （Android and ISO Different versions of the real machine ） And test tools .

2、 design phase

Test cases are usually designed according to business processes and use case design methods , Then hold a use case review meeting in the project team , After passing the review, the test cases shall be archived .

3、 Execution phase

In order to test the accuracy of the data , The test cases are usually executed by the entity machine . If you find that Bug After confirmation, the defect management tool conditions Bug, Waiting for development and repair , Then do the regression test , If the regression test fails , Reactivate Bug; If the regression test passes , take Bug Change the status to closed ; If the developer refuses to modify Bug, Then communicate , You can also meet in the project team to discuss .

4、 Evaluation report stage

Legacy Bug Conduct a risk assessment , And give handling methods and opinions , Finally, prepare the test report and summarize the test after the project goes online .

9.3 APP The test method

To do well APP test , First of all, understand Android And IOS The difference between operating systems , Be familiar with APP How to test , To test more comprehensively , It is recommended to use the real machine for testing .

9.3.1 Android And IOS

Android Current ownership Google, Its kernel is Linux, Its applications are Java Programming language to write , because Android The running mechanism of is virtual machine , The system needs a lot of memory in exchange for execution speed , Coupled with the irregular automatic memory recovery mechanism , Which leads to the phenomenon of jamming .IOS It is a closed mobile operating system launched by apple , It specifies a development language to use Objective-c Language . Its operation mechanism adopts sandbox operation , There is no need for a virtual machine throughout the run , So compared Android The execution efficiency should be higher .

because Android The development strategy is adopted , So many manufacturers have customized it . bring Android Mobile phones are better designed than IOS Become diversified , But at the same time, it also brings security risks , That is to say, we are testing APP Software ,Android than IOS Be safe 、 Compatibility 、 Think more , Market based AIDS are also better than IOS It should be widely used ,Android The version of the system can be increased or decreased , and IOS The version of the system can only be upgraded （ Except for prison break ）

9.3.2  UI test

UI Testing is user interface testing , The specific test methods are as follows ：

1） First, make sure UI The interface design conforms to the National 、 Industry 、 Standards and specifications of enterprises

2） Focus on the window 、 menu 、 The layout of dialog boxes and button controls 、 Whether the style meets the user's requirements

3） Control size in different pages 、 Whether the style is consistent

4） Whether the color matching in the page is reasonable , The overall color should not be too much .

5） Whether the text prompt is friendly, whether there are sensitive words 、 Key words ;

6） Is the operation simple 、 Hommization 、 Is there any help to guide ;

7) Adaptive interface settings zhu meter 、 Whether the content is adaptive to the size of the window

8） Whether the picture involves copyright 、 privacy 、 Patent and other issues .

9.3.3 A functional test

It is to verify whether each function is consistent with the requirements , It can be tested from the following aspects ;

1、 Install the uninstall

1） Verify whether the installation and uninstallation are normal under different operating systems , Such as Android、IOS etc. ;

2） Whether the software can be installed through third-party tools 、 uninstall

3） Whether it can be cancelled during installation and uninstall

4） Whether the exception handling is appropriate during installation and uninstallation 、 If you restart 、 crash 、 power failure 、 Disconnection, etc

5） Whether there is a prompt for insufficient space during installation

6） Whether the installation file is written to the specified directory , Whether all files and folders are deleted after uninstallation .

7） Can I reinstall after uninstallation , Whether the data is synchronized after installation , Whether the function is normal

8） Whether there will be a prompt message for repeated installation

9） Whether there is a prompt message for directly uninstalling the program

2、 Startup and operation

1） After installation, start the software to test whether the function can run normally

2） Whether there is an access prompt when opening the software for the first time , If you allow access to the address book 、 Get geographical location, etc ;

3） Whether the speed meets the requirements during the first start-up operation , Whether the page switching is smooth

3、 Sign up to log in

1） The user name and password length should be considered when registering 、 Whether there are restrictions or rules on the format ;

2） Whether there is a prompt for duplicate name registration ;

3） After successful registration , Whether the user can log in normally

4） Whether the software has a quick login , Such as mobile phone code 、 Get the verification code and log in ;

5） Whether the third-party account login is supported , Such as QQ、 WeChat 、 Accounts such as Weibo ;

6） Is there a limit on the number of incorrect password entries when logging in ;

7） Whether there will be friendly prompt when the network is interrupted during login ;

8）APP Whether the login free function is realized

9） When the user exits voluntarily , Next start APP You should switch to the login interface .

4、 Front and rear station switching

1）APP Switch to the background , Go back to APP when , Whether to stay in the previous operation interface ;

2）APP Switch to the background , Go back to APP when , Whether the function is normal , Whether the data is updated ;

3） After the phone locks the screen , Then unlock and enter APP, Whether the function is normal , Whether the data is updated ;

4） After the prompt message appears , Switch to the background , Go back to APP, Check whether the prompt message exists ;

5） Multiple APP Switch between software , Whether the function is normal , Whether the data is updated ;

6） Use APP when , Interaction test with mobile phone functions , If you call me 、 Receive SMS 、 Alarm clock, etc .

5、 Upgrade update

1） When APP When there is a new version , Whether there is a relationship prompt ;

2) When the version is a non forced upgrade update , Do not update whether it can be used normally ;

3） When you exit without updating , Next start APP, Whether there is still a prompt to update information ;

4） Set up APP When the software is upgraded automatically , In none Wifi Under the circumstances , Update automatically ;

5） When the version is forced update , Do not update whether it can be used normally ;

6） Whether the function can be used normally after upgrading , Whether the data will be synchronized

6、 Abnormal test

1） Electricity test 、 Such as electric quantity 10%、50%、90% when , verification APP Whether the function is normal

2） When the battery is low , verification APP Whether the function is normal ;

3） Charge 、 When the power is switched on 、 verification APP Whether the function is normal ;

4） Weak network test , simulation 2G、3G、4G、5G、WIFI when , verification APP Whether the function is normal ;

5） simulation 2G、3G、4G、5G、WIFI Switch between , verification APP Whether the function is normal ;

6） Offline testing , Check APP Whether offline browsing is supported ;

7）Push test , Check whether the user can accept in the undisturbed mode Push

9.3.4 Performance testing

APP The performance test of is divided into the performance of the mobile terminal and the service terminal

1、 The performance of the mobile terminal

Mainly detect resource problems , Such as CPU. Occupancy within 、 Power consumption 、 Flow situation .

（1）CPU Occupy

In the use of APP Software , If CPU Occupancy is lower than 20% Indicates the best state , If CPU Occupy in 20%~60% Indicates that the resource usage is relatively stable , If CPU The occupancy rate is 60%~80% Indicates that the resource usage is saturated , If CPU The occupancy rate exceeds 80% Performance bottlenecks , Resources must be adjusted and optimized as soon as possible .

（2） Memory usage

The memory of mobile phones is very limited , To reasonably apply for memory use , To avoid memory overflow ; On the other hand, we should release the memory in time , To avoid memory leaks . Improper use of memory , It often causes APP The software is unresponsive 、 crash 、 Run away 、 Flashback and so on .

（3） Power consumption

In the use of APP Software , Must check APP Of electricity use , So as not to cause power consumption and heating of the mobile phone , Bring about adverse effects .

（4） The use of traffic

Conduct APP Software , Repeated requests are often encountered , Slow response, etc . When testing, you should pay attention to different networks , Use of browsing . You can use some Monkey Tools to detect Android Performance problems on the mobile terminal .

2、 Server side performance

Follow Web The performance is similar , It mainly simulates a large number of mobile phone users calling the interface to generate load on the server , You can use tools , Run concurrent tests 、 The load test 、 Stress testing, etc . The tools are described in the following sections .

9.3.5 Security testing

Move APP There is a very important problem is the security problem , That is, the user's privacy is leaked . in the light of APP The following aspects can be referred to for the safety test of .

1、 Install package security

1） First, verify whether the installation package verifies the signature , To prevent the installation from being overwritten by malicious third-party applications .

2） Whether developers confuse the source code , In order to avoid being decompiled software to view the source code ;

3） User privacy , Especially whether to access the address book , Specific permissions need to be checked .

2、 User security

1） Users call 、 texting 、 Whether there is a risk of fee deduction in connection with the network, etc ;

2） Whether the user password is encrypted during transmission , Whether the storage is encrypted in the database ;

3） Whether the expiration time is set for login free ;

4） User's account 、 Whether sensitive data such as passwords are stored on the device ;

5） Whether the interface requiring authentication can be called when the user logs off the account ;

6） Yes Cookie Whether a reasonable expiration time is set for the use of ;

3、 Data security

1） Whether the user's sensitive data is written to the log or configuration file ;

2） Whether the user is prompted with a thank you or a security warning when using sensitive data ;

3） Whether the third-party input method is supported when inputting sensitive data ;

4） Whether the data entered by the user has been verified for validity ;、

5） Whether secure communication is used in the connection containing sensitive data , Such as HTTPS;

4、 Communication security

1） All phone functions should be prioritized , Answer the phone 、 Receiving text messages, etc ;

2） When the network is interrupted or abnormal, you need to give the user the prompt of abnormal network ;

5、 Server side security

Focus on interfaces , Its security is similar to Web The security of the end is similar , The main consideration is SQL Inject 、XSS Cross-site scripting attacks 、CSRF Cross Site Request Forgery and unauthorized access .

9.3.6  Compatibility test

APP Compatibility testing is a time-consuming process 、 Labor consumption 、 And expensive testing work , And APP Compatibility is a necessary testing activity , The test mainly considers the software of the mobile phone 、 Hardware compatibility , On the one hand, we should consider the relationship with the mainstream APP The compatibility of ; On the other hand, it also considers the compatibility of mobile devices , For example, mobile phones of different brands 、 Different operating systems 、 Different mobile phone screen resolutions, etc .

The specific test method can use the simulator to simulate different mobile phone brands 、 System 、 Test the resolution , Third party tools are also available （ Such as Spider Tools ） And the cloud test platform .

9.3.7    The interface test

Whether it's Web End or end APP Interface , The test method is roughly the same （ Reference resources Web The interface test ）

9.3.8  User experience test

Experience can be considered from the following points ;

1）UI Interface design , Evaluate the product from the user's vision ;

2） Use the real machine to test the collection compatibility ;

3） Whether the user's guide design is reasonable

4）APP Whether the page Jump design and depth are reasonable

5） Experience the lock screen 、 Horizontal and vertical screen design and various abnormal operations .