Q & A ticket to specific questions

Preface:

Today, when testing the NK certification base disk, we found a problem with an abnormal phone number.

At the same time, the cause of the problem is described in zookeeper, but when the problem is described,

Some problems are exposed, which require future attention and improvement.

========================================================== ==========================================

I remember when I first wrote the QA ticket, someone told me that I should try to put what I want to say on the page.

Let the viewer see all your things without moving the mouse scroll bar.

This incident has had a deep impact on me. Until today, I wrote Q & A and other issue tickets,

Try to compress the content to one page.

I have always said this, and I feel good about myself.

However, I did the same for describing a complicated problem today.

After being pointed out by leader, I have some thoughts, that is, some problems should be analyzed in detail.

========================================================== ==========================================

First of all, I did not take it into consideration, that is, the first impression of the other party while watching this ticket.

(The first impression is that the description is too complex)

Cause: So all of them are together. Although there is a sense of excitement, it seems like it is too tight at first glance !!!

Deep reason: I always want to clarify the problem in one step. In fact, this problem can be explained in several steps.

========================================================== ============================================

Conclusion 1,

You don't have to concentrate the image on one page, but every time you make the image so tight !!
Specific Problem Analysis !!!

Conclusion 2,

After writing a ticket, I want to think about it. If I was the person who checked the ticket, would I feel it at first glance?

The description of the problem is complex, so you have no confidence to continue looking at it.

Conclusion 3,

For complicated problems, you can explain them step by step in QA. Don't always think about all the problems at once.

For example

1. symptom: Error. Data is different. There are two error pictures.

2. Cause: different data may cause different exceptions.

3. Cause: one exception can be captured, and the other cannot.

※This is explained step by step. The main purpose is to make people who are looking at the page feel obvious, rather than packing the pictures in a pile.

Conclusion 4,

For QA, we should first talk about the problem and let him see that there is a problem in this place,

This problem can arouse his interest and attention.

(For example, this time, due to an error in the encrypted data, two levels of error can be displayed based on different data)

(Describe this phenomenon with him first !!)

Then, let him know the cause of the problem.