Functional testing category of "reprint" mobile End

To summarize are all very simple, but very important functional tests .

Defining functional Tests: Functional testing is a quality assurance (QA) process and a type of black-box testing that bases it test cases on The specifications of the software component under test. Functions is tested by feeding them input and examining the output, and internal program structure is rarely considered ( Not like Inwhite-box testing). Functional testing usually describes what the system does.

In short, it is a test of what the system can do when it comes to functional testing. For the mobile side, this is what kind of app, what it can do. But compared to the PC-side system, because of the diversity of the use of the environment, the use of user differentiation, the use of different habits to make an app testing a rather laborious, first understand the next functional test to test those aspects.

First, to verify that the app is properly installed, run, uninstalled, upgraded, and before and after the operation and operation of the system file impact, mainly including:

1) Check whether the software can be installed, run, uninstall correctly;
2) Install, uninstall, update error report;
3) Other ancillary information:
-The location and folder of the installation files is reasonable;
-whether the component is properly registered or deleted;
-System cache files, especially pictures, voice save location, whether it will affect the system level of files
Question 3 of the first question, mainly refers to Android, the truth of this check is relatively few, require to understand the Android APK application installation process and the default installation path, self-Baidu; the latter two problems are often omitted, this is a giant pit, said more are tears!
4) Upgrade!! In fact, in the process of testing generally will not be aware of the coverage test, but you have tried in-app download test, which is often forgotten Ah, and test cases inside the first version will have, and then will not be written, as we have not said the test cases, but will forget!! It is recommended that you write a check list for the line, including this one.
5) The APK name downloaded from the server, especially downloaded through the browser, will not understand the name of the application to create the illusion

Second, permission test, permission test this is a very simple thing, also did not find what to do for the mobile end of the rights testing, the simple column in the work encountered some problems.

1) Software permissions
-Charge risk: including sending text messages, making calls, connecting networks, etc.
-Privacy breach risk: including access to mobile phone information, access to contact information, etc.
-Add risk items, get permissions that are not needed within the app, especially the Andorid version, which can be viewed in settings to get those permissions, and the installation page will typically prompt the app for permissions
2) The Developer official permission list information comparison analysis (especially iOS audit, must check), and in the application process, iOS will prompt the user to get system permissions, this in the process of testing need attention.

Third, the requirements of the document or product specifications to check the--app function of the main function, which is generally measured by the test case to express, so the test case writing is very important.

Definition of test cases: a test case was a document, which has a set of test data, preconditions, expected results and postconditions, devel OpEd for a particular test scenario on order to verify compliance against a specific requirement.

This said test case is a guide document that describes an input, which produces a result by the operation of the system. In the actual process, the actual such an operation will have a lot of preconditions, it will lead to a different page will have such a test case, resulting in the repetition of the test case. Here, of course, I define the test case as an operation. In different test objects, the test case, whether a functional function or an operation, or a scene, the problem here is not much elaboration. Test cases are just tools, how the tools are used to see the individual, as long as the goal is achieved.

Test case writing this part, this would like to sum up this time, one hours, or not a specific direction, or feel that the test case is not easy to write, and then look at the test cases written before, feel write, but really start to write again, or feel almost anything, so next time to write a version of the more satisfactory test cases, Then make a summary, fill in this part of the bar!

Functional testing category of "reprint" mobile End