Editor's note: This is a bugtags user contribution, mainly introduces the changes brought about by using Bugtags before and after testing and solving bugs. Thanks to student Gao Zhengyan from Shanxi Agricultural University for their trust and support to Bugtags. The editor here sincerely invites all enthusiastic users to contribute to us and tell your story of using Bugtags.
0x01 Preface
Written on the occasion of the trend of Bugtags listing Crash, and the eve of English level 4. Just feel, nothing else.
0x02 Origin
In September, when the school started, with Codekk's WeChat account pushing a message called "Quick Feedback Tool for Mobile Application Bugs", if you want to do a good job, you must first sharpen your tool.
After reading the introduction, I can't help but feel that my eyes are bright, and it is a little different from the Crash collection tools I have contacted before, and I have also heard of some functions of shaking for feedback.
This is mainly a project similar to outsourcing. The application content is in the form of app social and community in the university. The overall app needs a good architecture
and complete testing (however, there is no testing), so it has to be tested while developing.
Initially, we used git version control in application development, mainly two people developed, and did not test sister paper. (At first I found a "designer" classmate), when the manager puts forward project requirements and improvements, he
often tells another person through the manager, and then another person evaluates and makes modifications directly in the code, and there is no record. The process is not transparent.
Later, the manager would find a piece of paper to record some problems and tick the solution, but this was still not easy to manage, and the uncertainty of the model and the difficulty of reproducing the bug reduced some efficiency.
There should be a picture here:
In the public account information, the process of submitting bugs was shown, and then I tried to integrate the SDK. The overall integration process was not troublesome. I quickly felt the effect and recommended it to another developer.
After access, I am familiar with the way of submitting bugs, and I feel that I have seen each other late. It is very suitable for managers to ask if there are any problems and which needs to be improved.
0x03 Growth
After accessing the application, I felt some convenience in terms of efficiency, but I found some problems. For example, I would always receive reminders by email and raise a work order.
I also consulted in the QQ group, and received this problem. It is being resolved and will be online next week.
And Bugtags When submitting bugs, the overall process is not troublesome.
It is gratifying that the iteration of the Bugtags team has made the Bugtags continuous improvement. With the use, the following features have been gradually launched:
Added several label states and types.
Distinguish between developers and those who submit bugs
Can edit status and delete labels in bulk
Crash can capture screenshots
Export function supported
Add anonymous submissions
Added functions such as batch invitation of members
……
In the process of the team's continuous iterative development of the application, I received a lot of tags from managers, often a dozen or so a day. If you make a list as usual, and then solve them one by one, it will waste a lot of time and efficiency.
The application is also in the internal testing of fir.im, and it is constantly improving and improving its development skills. The number of models affected by the crash has gradually increased from a small number of mobile phones at the beginning.
There should be a picture here:
0x04 accompanying
In the process of using, more and more questions are submitted, and more and more tags are received. After all, it is an App application, the process from 0.1 to 0.9 (0.1 means that a simple prototype has been developed when accessing).
A current statistic, there are already a lot of labels, and there should be pictures here:
Question interface:
With the continuous use, I found that the efficiency has improved a lot. During the nearly three months of getting along, I felt the unremitting efforts of the Bugtags team and the attention to development and testing.
And now it also provides some visual data to express the effect of the test and the degree of perfection of the application.
After the launch, we also focused on some Crash, and Crash is more reproducible than before, and we have improved it, optimized the performance of the application, and improved some user experience.
Because of the different models and systems, as an Android developer, you will inevitably encounter a lot of crashes. When users encounter them, they are helpless as a developer. After all, it is difficult to reproduce.
With Bugtags, you can make statistics in time. Models, system versions, and steps performed by users, and
now the trend of Crash occurrence has recently been launched, allowing developers to focus on recent crashes with high frequency for improvement.
There should be a picture here:
In this year's five-province computer application contest in North China, I also briefly introduced the bug management platform to the judges, which improved some development efficiency.
0x05 Postscript
Your test girl, domineering product, and boss must have needed it for a long time. If you love him or hate him, transfer it to him.
Before Bugtags, I didn't know there was a related bug management platform. As a developer, Bugtags is worth recommending.
Finally, a few comments (some of which are not sure whether they are pertinent or not):
Develop an Android studio plug-in, so that you can receive emergency label reminders.
Develop an Android client to implement mobile management of the label state.
Open some APIs to implement custom configuration
Hope to provide some mobile app testing, such as Monkey or something like practice.
If it is a non-Wi-Fi environment, provide some traffic statistics.