App black box test-some things you can try

<span id="Label3"></p> 　　 <strong>i. <strong>multiple quick clicks on a function entry:</strong></strong>The<span style="text-decoration: underline;"><span style="text-decoration: underline;"><strong>Test</strong></span></span>The method can be opened in some applications two times the target interface, to give some specific examples: 1. For example, many apps need to log in, if you open the two login page, it is easy to log on after the successful application of the Jump interface is the login interface, the second login caused by unknown consequences, The simplest consequence is that, Users will feel that the application needs to log in two times, not suitable for 2. Enter the user name password two times click the login button, some apps will open two login success interface, this time if you need to set the gesture password, then will do two settings operation, the consequences are unknown, due to different program logic leads to different consequences 3. Opening an interface a multiple times and then opening the interface B of an element in that interface several times, causing<span style="text-decoration: underline;"><span style="text-decoration: underline;"><strong>Android</strong></span></span>Triggers a similar garbage collection mechanism, resulting in a interface where the other controls are destroyed and invalidated after returning from B<strong><strong>two. The network app quickly exits the function and operates again after accessing a feature operation:</strong></strong>This test method will result in a quick multiple access to an interface, for Example: 1. The application will get some flags in the interface to do certain operations, if the development in the application of NULL values do not protect, well, multiple calls will make the pass parameter is empty probability increases, this operation can do more, no harm<strong><strong>Three. Click on all the places where there are pictures:</strong></strong>This involves the development of the habit, they will be in a certain logo to add a debug portal should not exist, This logo is often in the requirements of the specification is an ornament, but in the product of the test may be a debug entrance, as a tester, we should find that all<strong><strong>Four. do everything before logging in, change the interface elements, colors, etc.</strong></strong>This is done to ensure that the Post-login brush layout does not conflict with changes before login<strong><strong>Five. Lock Screen</strong></strong>We will know that the network, power off, strong retreat, such as a series of abnormal operation, but the most likely to ignore the seemingly in my view is the lock screen, bold in each interface lock screen bar, There is the best gesture password can wait until the gesture password Appears. There will be unexpected gains.<strong><strong>six. gesture Password unlock error</strong></strong>See if the interface stays in the login screen after the exception exits<strong><strong>Seven. Erase data, android-specific Skills</strong></strong>Is the app alive after clearing the user data?<p><p>App black box test-some things you can try</p></p></span>