[Live broadcast preview] 99 yuan cloud virtual machine × 9 yuan cloud native architecture √

1. Background

As more and more "newcomers" take on major responsibilities in daily work and preparations for major promotions, we find that only understanding our own system business can no longer meet our daily system development, operation and maintenance needs. To this end, the big data platform department organized a Bug Bash event to not only improve its understanding and use of brother products, but also to improve the functions of its own products. Today I will share with you some practical operation processes and experience summaries~

2. What is Bug Bash?

Bug Bash, as the name suggests, is bug cleaning . Usually initiated by QA, all team members put down their work and find a conference room to focus on finding defects together.

figure 1

3. Benefits of Bug Bash

1. An effective supplement to conventional testing. More user testing will uncover more problems or needs.

It is possible to discover different types and levels of omissions in business processes, hidden flaws in the overall design, and even hidden new needs in product planning. It is easier for different people to discover issues such as compatibility and permission differences. Testers can also improve their testing strategies based on the problems discovered.

2. Improve team cohesion and promote team communication.

In the bug cleaning process, some competition elements have been added, such as reporting who has found the most bugs from time to time, paired with relaxing and pleasant music, so that everyone can catch up with each other to find bugs. This will promote healthy competition among personnel, thereby boosting the morale of team members and increasing team cohesion.

3. In-depth product learning to bring more added value.

In daily work, production, research and testing spend more time working independently, focusing only on the parts they are responsible for, rarely having collective communication on product issues, and rarely using the entire product in depth. Bugbash allows other roles in the team to experience the product as users and gain an in-depth understanding of the business. Focusing on these issues and explaining in detail how and why they are handled can lead to more product thinking.

4. Bug Bash organization practice

figure 2

1. Activity preparation

1.1. Department publicity and implementation

Notify the plan and arrangement of this bugbash event in the department work group , and determine the event organization time, event conference room, and group divisions. At present, the products in the department mainly include three major products: JDQ, JRC, and integrated platform. In order to "sweep" each other more effectively, we have divided them into rounds and groups. As shown in the following table:

Rounds	group	Q&A staff	time	point	Remark
Round 1	JRC vs JDQ	JRC: Duan Dongni JDQ: Yin Wei	2023.11.15 18:00	Honghe Conference Room	Free explorers choose their own products to sweep
Round 2	Integrated platform vs JRC+JDQ	Integration platform: Guo Weiwei JRC: Duan Dongni JDQ: Yin Wei	2023.11.22 18:00	Honghe Conference Room	Free explorers choose their own products to sweep

Table 1

Tip: This bugbash is aimed at cleaning up the production environment . When it comes to the process approval process, you need to notify the other party for approval in advance to avoid blocking the subsequent process due to lack of approval.

1.2. Use case preparation & review

Before bugbash officially starts, testers should prepare test cases for their respective products in advance, and invite product managers and product lead developers to conduct use case reviews and delineate the scope of activities. You can refer to the following aspects:

The main process business scenario of the product. For example, create binlog collection tasks, consume topic data normally, etc.

Scenarios frequently used in daily operation and maintenance work. For example, consumers suspend consumption operations, etc.

Cross-platform joint query scenario. For example, query the associated JRC flink task through JDQ consumer username.

Hidden sexual function scenes. For example, function A will not be displayed under normal circumstances, and a certain switch needs to be turned on to display normally.

image 3

1.3. Test data preparation

Prepare test data based on use case scenarios and number of event participants. It mainly includes the platform to which it belongs, test data type, test jed data table, test ck data table, test data description, and user, as shown in the figure below:

Figure 4

Tip: Add permissions to event participants in advance. For example, use a designated project space.

2. Activity carried out

Event time schedule: 10 minutes to introduce the round of this event, 50 minutes to perform tasks, and 10 minutes to communicate and speak.

2.1. Task allocation

Tasks are divided according to the activity rounds and group divisions. Taking JRC vs JDQ as an example, JRC's R&D and other related personnel perform JDQ's tasks, and conversely, JDQ's R&D related personnel perform JRC's tasks.

2.2. Test data distribution

In order to avoid conflicts in task creation caused by using the same test data, personnel from both parties need to mark and claim the test data. As shown in Figure 4 above, the users are listed.

2.3. Problem record

When personnel from both parties find problems during the cleaning process, they will be recorded in joyspace in a timely manner. There is no need to discuss product details on site, and the test verifier, test time, result filling, and test verification results will be indicated. In the future, different rewards can be given based on the value and importance of the problem. As shown in Figure 3 above

2.4. On-site Q&A

The main product tester is the event answerer. Personnel from both parties may need on-site support in the following scenarios:

The task was created successfully and requires XXX approval, and the Q&A staff will follow up on the approval operation.

I don’t understand the product functions and use case scenario descriptions, so I need guidance.

3. The event ends

3.1. Problem collection

Merge, deduplicate, classify and summarize all problems found. Including the problem number, the product to which the problem belongs, the task number performed, problem defect description, screenshot or error log, recorder (task executor), and problem classification.

Problem handling. Work with the product lead R&D and product manager to review the priority of the problem, whether to improve it, the improvement plan, the person in charge of the improvement, the estimated completion time of the improvement, the improvement status, etc.

Figure 5

3.2. Problem review

A total of 40 problems were found in this bugbash activity, including 2 functional bugs, and 30 were determined to need improvement, mainly front-end optimization.

Testers improve product use cases based on the problems discovered to further improve product quality.

4. Summary of activities

4.1. Participate in user voices

① Provides opportunities to learn other products

Understand what other products do and how to use them, and cross-experience is more in line with the user's identity and discover more problems. It’s not easy to spare such a long time when everyone is so busy.

② Provide test scenarios to avoid blind testing

The test scenarios selected in the activity were mainly encountered in daily work. The testers described the operation steps clearly to facilitate the execution of the cleaning personnel.

4.2. Areas for improvement

①Critical node approval is blocked

Because the approver of the process link is not present due to various reasons (temporary meetings, temporary leave, etc.), the process approval is blocked and the task cannot be executed downwards. Backup personnel can be added during the approval process in the future.

② Time is tight and some tasks cannot be completed

Since the entire activity lasts only one hour, it will take some time for non-business related people to understand the business knowledge. In the future, the activity time can be appropriately extended and the task scenarios can be streamlined. For example, activities can be carried out in special topics, such as product interface ease of use, security, internationalization, etc.

③The incentive mechanism needs to be improved

This event lacks some material (such as small gifts: yogurt, chocolate, etc.) or spiritual (badges, T-shirts) rewards, and everyone’s enthusiasm for participation needs to be improved. It is recommended to introduce a game competition mechanism, which can increase interest, mobilize enthusiasm, and truly integrate work into entertainment.

5. Thinking

① Bug Bash platformization

This bugbash cleaning activity is mainly in the form of offline organization + shared documents. If we can build a platform to organize bugbash anytime and anywhere, freely choose product business scenarios, flexible and changeable task distribution will be more efficient.

② Bug Bash scope expanded

Instead of only allowing members of the internal production, research and testing team to participate in Bug Bash, users can also be invited to participate. The more people who participate, the easier it is to find problems.

Author: JD Retail Yin Wei

Source: JD Cloud Developer Community Please indicate the source when reprinting

Best Practices for Big Data Platform Bug Bash Cleaning