App Test contingency bug is not accidental

I believe that when you test the application software, often happens that their own bugs can not be reproduced or accidental occurrence, so the developer's solution to the bug is to refuse processing, resulting in this bug is useless bug, can not improve the quality of the software.

In fact, these bugs are only in a special scene will appear, need our testers to locate, below I listed the Smart Community app test project encountered some occasional bug.

Function One: The app when the invitation to the family, the flash back, some users will be able to unbind the normal, some users when the untied, there is a flash back.

Bug targeting: found that there is a flash, the invitation list only one user, here can guess is the value after the data is unbound, resulting in a flash back.

Function Two: Backstage publish the same serial number of the advertisement, the app appears flash back, contingency

Bug targeting: The app only displays 6 images, such as an ad with the same serial number, which causes the flash back

Function Three: After the user invites the family member, the family carries on the application authentication, cannot carry on the property payment, prompts the room ID number to be empty, uses other mobile phone login to be able to pay normally.

Bug Positioning: Family certification, in the absence of re-landing, did not get the room number caused.

App Flash back, usually appear empty value, overflow, variable no assignment result, above just enumerate three function scene, hope can initiate, bring more testers to share own test experience, let ice ice small white grow together

App Test contingency bug is not accidental