ios test should pay attention 1

1. To test the basic functions of the app, such as a calculator, you must first test the basic functions of the calculator, such as addition, subtraction, multiplication, and division. 2. App resolution compatibility test, for different versions and screen sizes of iOS system calculators on iPad And whether the iPhone5 is displayed normally, and whether the iPhone upgrade iOS8 calculator can work normally. 3. Security test, app read and write phone book, permissions, access network calculator whether to access the network, 4. app UI test, border, drag to, multi-touch screen, UI element size, color, font calculator button, font , whether the color meets the user's needs and meets the best user experience 7. App performance test, such as the calculation time of the calculator, the length of the response time, how much memory is used on the mobile phone, and whether there is a memory leak. Whether the power consumption is normal 8. Installation and uninstallation test the compatibility of installation packages such as upgrades 9. Internationalization of different system languages ​​is displayed normally 10. Ease of use test Whether the calculator function is clear at a glance, simple and convenient, and there will be no hidden menus that are difficult to understand. The phenomenon of ease of use is purely mobile phone calls, and I think so much for the time being. Interested in doing app automation testing.




Testing can be divided into white box testing and black box testing according to the major types. White box testing is generally performed by developers using coding. The tester needs to touch the internal code of the program; while black box testing can be performed without knowing the internal structure and code of the program. Our service only requires customers to submit the APP installation program, without submitting any source code and test cases, so it is a black box test. The following is the main test process: Carry out the smoke test. There are many sources of smoke testing, one of which is from the hardware industry. After the circuit board is completed, it must be powered on both sides first. If the circuit board emits smoke, it means that the board has a very serious quality defect and cannot be listed. In software testing, smoke testing refers to quickly verifying the main functions of the APP (for example: WeChat login, logout, message sending, etc.)
. If no problem is found, carry out more in-depth testing work; if any problem is found, it means that the APP has major defects and needs to be called back to the developer for urgent repair. The smoke test we conducted is based on the main functions of the APP. For example, if the APP sharing photos, try taking pictures and sharing functions. Do a full functional test (go through all functions of all interfaces)
. Functional testing is also called behavioral testing. It is necessary to verify whether the expected functions of the application are implemented according to test cases. In the mobile development team, this link is generally in charge of the product manager to check whether the requirements raised by him have been implemented. Larger teams will have regular testers to do this work. Since our service does not require customers to submit test cases, our testers will traverse all functions according to their own understanding of the APP to see if they are normal. We will take screenshots of all interfaces and add a test case for each operation. The record will indicate which interface, what operation was performed, and what kind of result was obtained. If the result is as expected, the case is a success; if the result is obviously wrong, the case is a failure; if the result state is ambiguous or there is room for optimization, the case is a potential problem. Conduct free exploratory testing (try boundary conditions, enter special symbols, abnormal network environments, abruptly interrupt programs, etc.)
. The purpose of functional testing is to verify whether normal functions are realistic, and the purpose of free exploration testing is to test whether the application will have problems under extreme operations. General applications can ensure that the main functions have been implemented before going online, and there will be no problems under normal operation. However, in some special scenarios, due to the inexperience of the developer or the lack of thoughtful consideration, the application will behave abnormally. In some cases, the expected function cannot be provided, and in the worst case, the APP crashes directly. Exploratory testing is all about finding actions that can make your application fail. There is no fixed routine for testing in this area, and it mainly relies on the basic experience of test engineers. Our test engineers are all experienced and are good at finding potential problems in APP. It is difficult for ordinary product managers and junior test engineers to find such vulnerabilities, and it is too late to find out when users use the app. Run regression testing (retest the case for an application that was previously tested with our service). The premise of regression testing is that our service has been used before, and we will retest the last case when testing again. Regression testing is necessary because developers may create new problems while fixing bugs. It is also a stage that the general software must go through before it goes online. The problems found in the regression test fall into the following categories: Repair, that is, the developer corrected the bug in the last test; Reappearance, the last bug still exists this time; Rollback, the previous normal function appeared in this test problem. Generally, after the regression test, we will also try to find new bugs, so that the APP can be retested more completely.