Last week we discussed the topic you are most rewarding bug:
Topic: Recall what makes you the most rewarding bug that? How did you find this bug?
Topic Description: as a software test engineer, you are sure to find numerous makes you feel excited and proud bug. Think back to let you have a bug most rewarding, and how did you find this bug it? Maybe you can just find the idea of the problem to help other people.
Share of results of discussion
Not many people actually participate in the discussion of the three main under the impression I am here to share my own encounter particularly deep bug, the first two are scouring occurs when the hand work, the last one is at work in the emergence of Yutong.
bug caused by the improper use zipFile
Hand wash Android bottom frame is Atlas (already open source, can be found on github), was a colleague of the security services want us to fight patch packages for security verification, but often can not properly install the patch package loaded (under normal circumstances, hand wash restart to take effect).
So open a long road to find the problem, because the Atlas is the equivalent of a sdk, so mainly by debug the code, step by step follow-up to see where the problem is. Especially impressed investigation for a week, the real cause of the problem are not found, but guess decompression patch package, there is a problem, but look at the use of the code ZipFile can not tell what specific the problem is.
Eventually a colleague suddenly said, to write a single example of a zipFile compressed file to verify that the api itself has a problem. The results are amazing examples can be run properly, then the code inside and Atlas do than found when using zipFile decompress files, read and write using a zipFile same. Eventually leading patch package is always an error when local decompression, and thus can not be a normal hand wash load patch package.
So when you encounter can not solve problems, can change in thinking, maybe there will be a windfall.
Pit red double eleven activities, services on the line
In the two-eleven by 2015, there is a red envelope hand Amoy activity called fission red envelope , I was in charge of testing. In order to verify that the environment was a red envelope logic online, the server classmates set up a red envelope amount is 0.01 yuan, but the show is 100 times, which is $ 1.
Verify that no problem, normal development activities waiting for entrance release version until the first two hours on a few days during the warm-up events before the two-eleven line, suddenly a lot of user feedback, suggesting that red envelope is 100 yuan, but only credited into the dollar (the normal amount is $ 1, $ 5, $ 10, so users have received a $ 100, 500, 1000).
A scare, but it will result in capital loss, is it not logical to measure the test?
Hand wash is very honest, all received 100 yuan, 500 yuan, 1000 yuan red envelopes of users, are carried out in accordance with the issuance of a red envelope denominations, thus causing a great deal of capital loss. Later, when doing inventory we found that when development and deployment services, there is not a machine deployment is successful, it is also used before the test logic (red envelope denominations expanded 100-fold).
This gives us a warning: Fear the production environment, must not be the test of logic in order to release the test line, otherwise, it may cause a huge disaster .
After ios app upgrade, appeared crash
Our team was responsible for docking all the company's app, I remember very clearly, we set a sister, 20:00 and more tests still working overtime, Apple's application store shelves last, but wait until after review by, users have direct return, complete update of the crash, no way to use.
First off the shelf quickly to our application, followed by appease customers, fortunately not many people updated. The final step is to find the problem, find the database structure made changes, but not the best compatibility, resulting in after it bounced off the updated app.
Next is to solve the problem, back on the shelves application market, the re-set after the meeting, we reached two consensus:
- After developing all the changes, you must mail notification to the test and product.
- Tests need to improve their return to library use cases, but be sure to use ios after testflight be verified to the line (before been lazy, did not carry out).
Through this bug, let me remain vigilant: Fear the production of bags, head always filled with the sense of quality .
Written in the last
Recent weekly topic, the participation of students is relatively small, we may return to work recently, we are more busy. I hope to be able to create a very good atmosphere for discussion and exchange, so that everyone can be harvested and progress in the discussion.
What topics interest you most? What topics you would participate in the discussion? What topics you more concerned about? Welcome to give me a message, or micro-channel contact me, I will be targeted selection of the corresponding topics.