Test process summary

1. Send a developed installation package with a version number to the development manager by email for testing, and the product should have corresponding product documentation
   ios: you can use itools, drag the ipa package into it and it will be installed automatically, if not You can check it on Baidu (how to install the ipa package with itools)
   Android: The packaged package is called apk package, and there are many installation methods (you can search for apk installation package method on Baidu), the following are two of them
      1. Windows system can use mobile phone The assistant double-clicks the apk file to install
                   2. It can also be sent to the mobile phone through QQ and other tools, and then download and install

2. Check the current test environment and the corresponding product documentation:
    Check the installation package to be tested and the documentation to be tested: product functional requirements document; product prototype Figure (just an approximate demo); Product renderings (generally IOS and Android have renderings provided by products)
    ios environment check: ios operating system version, device type, network status
    Android environment check: Android operating system version , device type, network status
    web environment check: the version of the browser used (if it is the mainstream browser of the website, it should be tested, if it is a management system, the product should determine which browser our system will use in the future and what the version is above)

3. Start the test: (ios, Android, web, some parts of the test requirements are the same)
        ios: After completing the tests of the basic functions and requirements described in the business requirements, you can perform the following tests when you have time
   1. Answer the call while the app is in use. You can test the length of different call times. After the call is over,
                    The response of the originally opened app, such as whether to stay in the original interface, the response speed when continuing to operate, etc.
                2. During the use of the app, if there is a push message, whether it will affect the use of other functions of the app, and secondly, whether the push message is clicked to view the message
                3. When the device is charging, how is the response of the app and the smoothness of the operation
    4. How does the app respond when the network environment changes: Are there appropriate prompts? How is the app's feedback when going from a networked environment to a non-networked environment? When returning from an environment without a network
                   to an environment with a network, can the data be automatically loaded, and how long does it take to start loading the data
                5. The response when switching between multi-touch and other apps
                6. The process is closed and then reopened,
                7. The smooth usage of the app when the IOS system locale changes (that is, the IOS Apple operating system is upgraded to another version)
                8. The test of each physical button, such as the volume button, the lock screen button, and the home button. The latter two can also be designed with many use cases. For example, when the app is open, after
      pressing the home button/lock screen button, after 1 minute, 5 minutes, 10 minutes, and 30 minutes, reopen the app/unlock to see if it is still open. The app sub-interface,
      or return to the main interface of the app. When the horizontal screen and vertical screen are displayed and switched several times quickly, this also applies to
      different versions of Andriod IOS (especially between IOS 5 and 7, the UI update is relatively large)
                9. Can the app be actively pushed when there is an update
               10. When you first get the ipa file, look at the file size. 50M is the breaking point. Because when using the mobile phone network, if it is larger than 50M, there will be a warning
     (maybe it cannot be downloaded, only WiFi can be used, I don't remember it clearly, you can check it.)
               12. When there is UIWebView in the program interface, try Try switching the interface quickly, do it a few times, and see if it crashes. Because there is more than one thread in UIWebView,
                   there may be crashes. 3. There is the process of simulating itunes app update. (How to simulate, I dare not say nonsense. Maybe you can do some research.) For example
                   , you buy something in the app, then update the app, see if the purchased item is still there, etc. . . 4. For the UI you mentioned, please add, to see if the
                   normal screen and double-precision screen are displayed well.
       Android: Same as above
       web: After the main business logic functions are tested, you can test other (non-normal use) Some test operations to see if the software product is robust enough)
     
      Summary:
            1. Functional module testing: First of all, the functional items of the functional module should be analyzed to test whether each functional item can realize the corresponding function. Generally, the basic function test can be completed according to the test case (Test Case) or the process of the software itself (relatively simple, and the fault is easier to find and solve).
2. Cross-event testing: Also known as event or conflict testing, it refers to a test in which a function is being executed while another event or operation interferes with the process.
3. Stress test: also known as boundary value fault tolerance test or limit load test. That is, during the testing process, the maximum capacity, boundary value or maximum bearing limit of a certain software function has been reached, and related operations are still performed.
4. Capacity test (ios and Android): that is, the test when the storage space is full, including the test in which the available memory of the mobile phone user and all the space of the SIM card are fully used. At this point, the editable module is tested for any operation related to storage space.
5. Compatibility test (ios and Android): that is, tests of different brands and models of mobile phones, different networks, and different brands. The web also has compatibility tests between different versions of
     different browsers
The ability to attract users is a concentrated expression of the adaptability, functionality and effectiveness of an interaction.
     
4. Record bugs (for example, record bugs in the mantis system):
1. Defect summary (Summary) Simple and clear, easy to understand Generally no more than 30 words in
length
Explain as much as possible: what is the situation and what caused the problem so that 
others can locate the bug
2. Descrīption a
) Reproduce steps (Actions) Describe in detail the key steps to reproduce the problem
                 omit irrelevant operations, and strive to achieve: all reproduction steps are sufficient and necessary The
        easy-to-understand routine steps can be taken in one sentence, such as logging in as an administrator, entering the background user management page
     and environment-related issues, and giving specific conditions, such as a certain operating system, a certain browser
            b) Actual results (Actual Result)
              describe the actual error results. You
  can use screenshots to express
     bugs that are not always reproducible, and give the frequency or regularity of occurrence
  
. Confirm this function), the reasons are as follows:
    a. Redundant code, garbage code, unnecessary code can cause system functionality, efficiency (performance), and security risk
    b. Interface problems cause abnormal operation between modules, Causes efficiency (performance) and functional risks
    c. Compatibility and reliability risks that exist on different platforms (that is, when hardware, network, and supporting software are not available)
    d. Misunderstanding errors cause deviations in functional design, resulting in The whole development fails