WEB, App testing focus

Web Testing Highlights:

1. Functional testing: whether the implementation of the function to meet customer needs.

2. Performance test:

2.1 Link Speed test: Test the speed of page links

2.2 Load test: How many users can the Web application system allow online at the same time? What happens if you exceed this amount?

2.3 Stress Testing: Test your Web application for a certain amount of stress without crashing and where the performance bottleneck is.

3. User interface test: Whether the interface is harmonious, the style is consistent, the page can be scaled proportionally

4. Compatibility test: Operating System (Windows xp,windows 7, Apple, Linux), browser (different versions of different vendors), resolution

5. Safety test:

5.1 Number of landing times are limited, whether there is a timeout limit (after the user log on for a certain period of time does not do the operation will automatically exit)

5.2 Log files and cookies (do both explicitly display user password accounts?) ）

App Testing Highlights:

1. Install and Uninstall

1.1 IOS different system versions or Span style= "Font-family:arial;color:rgb (51,51,51); letter-spacing:0px;font-size:13px;" >android Installed on different system versions (some system versions are too low for apps to fit)

1.2 whether the software will function properly after installation

1.3 Whether you can cancel during installation

1.4 If the installation space is not sufficient when the appropriate prompt

1.5 network Installation when there is a corresponding prompt

1.6 Can uninstall the software normally

1.7 When uninstalling the crash, power failure, restart and other accidents, if the environment after the reply can be properly uninstalled

1.8 Whether the uninstall process can be canceled, click Cancel Uninstall after the normal use

1.9 Write directly in the program whether there is a prompt message

1.9 Remove all installation folders after uninstallation

2. Login

2.1 Account and password errors when the interface is prompted

2.2 After the user actively log out, the next time you restart should enter the login screen

2.3 The correct automatic login when remembering the password

2.4 Password changes, the next time the login is synchronized (with the original password login prompt password error)

2.5 No sign-in status action some pages are controlled (please login when not logged in to add items to cart tips)

2.6 User information is updated when switching accounts (QQ switch related account, user information changes in time)

2.7 More than one end of the operation, ensure that the data is accurate and each end of time to see the updated data (QQ: computer, mobile phone)

2.8 iOS and Android devices log in to the same account to make changes to the data to ensure that the data is correct and that the updated data is visible in time

3. Running

3.1 can open and use normally after installation

3.2 Whether there is a load prompt at run time

3.3 Running speed and switching speed between modules is smooth

4. Offline

4.1 Log in after the network can browse local data

4.2 Are there any friendly hints when getting data

4.3 The network can be re-connected to the normal use

5. Message Push switch

5.1 Whether the message push switch is turned on by default (open by default)

5.2 Push switch can open and close freely

5.3 Open Push switch can receive message push normally

5.4 App backstage, the phone message bar can receive message reminders, click to view, click and then disappear from the message Bar

5.5 App runtime message prompt does not enter the message Bar

5.6 Push switch off cannot receive message push

6. Software Updates

6.1 Indication of updates when a client has a new version

6.2 Ensure both iOS and Android are up-to-date and ready to install and function

6.3 When the version is a non-mandatory upgrade, the user can cancel the update, the old version can be used normally. Users will still be prompted for updates the next time they start the app

6.4 When the version is a forced upgrade, when the user does not make an update after the mandatory update is given, the client exits. The next time you start the app, a mandatory upgrade prompt still appears.

6.5 If the client has a new version, the direct update check will update properly if the client is not deleted locally.

6.6 When the client has a new version, if the client is not removed locally, check whether the updated client features are new versions.

6.7 When the client has a new version, if the client is not deleted locally, check whether the file with the same name can be updated to the latest version properly. If the above can not be updated successfully, also belong to the defect

7. Anomaly Testing

7.1 The app is running out of memory correctly prompt

7.2 App run suddenly power off, break the network, constantly point, constantly refresh, switch background whether Flash back, crash (abnormal test)

What are some tips for making or receiving calls, sending messages, receiving messages, starting a camera, and so on when the 7.3 app is running?

7.4 2G, 3G, 4G, WiFi internet app response speed

7.5 When the network is not good, the submission data is always processed in the submission, there is a delay, the submission failed to have a reminder

7.6 There is a network to no network and then to have a network, submit data, do the operation is normal load

8. Front and rear switch of the application

8.1 App switches to the background and back to the app, checking to see if it stays on the last user interface

8.2 App switch to the background, then back to the app, check the function and application status is normal, IOS4 and IOS5 version of the processing mechanism are different.

8.3 app switch to the background, and then back to the foreground, pay attention to whether the program crashes, functional status is normal, especially for switching back from the background to the foreground data has automatic updates.

8.4 Mobile phone lock screen after unlocking into the app notice whether it crashes, functional status is normal, especially for switching back from the background to the foreground data has automatic updates.

8.5 When the app is in use, when the phone comes in and then switches to the app, is the function status normal?

8.6 When the app process is killed, the App,app can start normally.

8.7 After you have to handle the prompt box, switch to the background, and then switch back, check whether the prompt box is still there, and sometimes the app will automatically skip the hint box defects.

8.8 for the data exchange of the page, each page must be a front and back switch, lock screen test, this page is most prone to crashes .

This article from "The History of the strongest SB" blog, declined to reprint!

WEB, App testing focus