Mobile App Development test Tool Bugtags Integration and use tutorial "reprint"

A few days ago, a lot of apps suddenly became popular, but eventually they were all cherry blossoms. As a startup team, a sudden burst of red is a very rare opportunity. However, the egg, due to the lack of adequate testing, coupled with the proliferation of users, app Flash, server data anomalies and other issues are exposed, the user's loss is inevitable.

A successful app, testing is an essential part. If there is not enough testing to go online, will inevitably lose a part of the users can become a big fan, and, very detrimental to the promotion of the app.

Problems encountered on the test

What does the test do? Simply put, it is the fault! The bugs found in the test are submitted to a task management system, and after we have solved the bug, we close the bug in the task management system (always the bug that is not complete). Some companies may not use the task management system, directly using Excel tables.

In this mode of operation, there are always some problems:

• Excel is not good for bug management (a task management system can be a lot easier)

• After the test found the bug, need, and then sent to the computer, and then uploaded to the task management system, this process is more troublesome

• Device information, app status, problem itself is difficult to describe

• Some bugs are hard to reproduce

• Crash logs are difficult to collect

I think a lot of children's shoes have come across these problems. Test Submit a bug, we always can not reproduce, cannot be reproduced can not locate the problem where (can only continue with the test rack: you want to reproduce the bug Ah! ）。 In order to solve these problems, I recommend a test sdk-bugtags to you today.

Bugtags supports iOS and Android platforms, and I'm just introducing the iOS platform here.

To facilitate testing, I have integrated the bugtags in Iosstrongdemo:https://github.com/worldligang/iosstrongdemo. Bugtags is really handy for testing, so let's give you a quick introduction to Bugtags and Bugtags tutorial.

Bugtags Introduction

According to the official website: Bugtags is a new generation of defect detection and management tools designed for mobile testing. Committed to improving the testing process of mobile apps, connecting the user experience between discovering defects and submitting defects, and improving the efficiency of testing and resolving defects. Improve your app anytime, anywhere.

Bugtags uses the original application to see that is the resulting problem escalation method, effectively improve the efficiency of the escalation of the problem and the accuracy of the problem description, and the platform provides automatic collection and analysis of crash information and problem lifecycle management functions.

Bugtags Official website:

https://bugtags.com/

Through a simple understanding, I feel that bugtags should be a very good test tool. If it's really as good as the official website, it's really a big benefit for developers. I decided to try out the bugtags out of curiosity about new things and technologies.

Bugtags Integration and Usage Tutorials Bugtags Integration Tutorials

I am using cocoapods integrated Bugtags SDK, the integration method is relatively simple. The steps are as follows:

1. Add the following code to your project's Podfile

pod ‘Bugtags‘

2. Perform pod installation commands

pod install

3. Import the header file in APPDELEGATE.M

#import <Bugtags/Bugtags.h>

4. Then add a row to the Application:didfinishlaunchingwithoptions: method

[Bugtags startWithAppKey:@"App Key" invocationEvent:BTGInvocationEventBubble];

The app key here is the app key that you get when you create the app after logging in to bugtags.com.

For detailed usage of cocoapods, please visit: https://cocoapods.org/.

Bugtags can also be manually integrated (it is recommended to use Cocoapods to manage the third party libraries), the tutorial on manual integration can be clicked: http://help.bugtags.com/hc/

Once the connection is successful, a small ball is suspended in the app. (can also be shaken by shaking out the ball)

Bugtags Using Tutorials

Next, I'll show you how to use Bugtags by submitting a bug and a flashback log. First, let's take a look at the Bugtags console.

Bug Submission

Let's say we tested the app and found a title that was incorrectly written. Then, submit the bug by Bugtags. To submit a method, look at the GIF graph:

After submission, refresh the Bugtags console. At this point, we have a new bug in our console:

Click to see the bug details and see if the bug was just submitted:

Sure enough, we just submitted the bug. We have previously made the mark "Title error", and here is a clear record of our device information. It feels very convenient!

You can also view the steps for user actions. Before we mentioned the bug in the test paper, it was difficult to reproduce. Now we can quickly reproduce the bug with Bugtags user-action steps:

More than these features, there are user data, console logs, and Bugtags logs. More functions we have access to the SDK to learn more about it.

App Flash back

I bind a method on the left side of the navigation bar:

- (void)actionClick:(UIButton *)button{    NSArray *array = [NSArray arrayWithObjects:@"1", nil];    NSString *string = [array objectAtIndex:2];    NSLog(@"%@",string);}

This is an array out of bounds problem, the array out of bounds can cause the app to flash back. Let's see if bugtags will record this flash-back bug.

After the commit, refresh the Bugtags console again, and there is a new bug:

In order to test the accuracy of the bugtags data, I tested it with the simulator and the real machine, with a total of five points. Let's take a look at the information Bugtags Records:

Suddenly, I felt bugtags really strong. Have children shoes may worry, if this time I do not have the Internet how to do it. Will the flashback information be submitted? Don't worry about it, I've already tested it, and Bugtags will submit the previous flashback message when you're on the next Internet connection.

Summarize

Here is my summary of the BUGTAGS trial process, the following points:

1. I am connected to the Bugtags latest iOS repository for iOS SDK1.0.4 integration process simple and convenient.

2. Bugtags easy to test upload, can also be labeled.

3. Bugtags Records device information, user data, user steps, console logs, and Bugtags logs.

4. Bugtags will automatically submit a flashback message.

5. Bugtags can set priority and bug management for bugs.

Acknowledgement

The birth of this tutorial is not easy, in the use of bugtags in the process, inevitably encountered some problems. I was directly with bugtags technical staff He Dong shoes Communication, thank you very much! Hopefully this tutorial will help you quickly access the Bugtags test tool and provide the efficiency of your app testing.

何童鞋QQ：39442811技术交流群：479166560

If you think the tutorial is good, remember to share Oh!

Mobile App Development test Tool Bugtags Integration and use tutorial "reprint"