Remember Me Binghuangmaluan week (0808-0812)--user feedback and modification point verification

Late at night, but I still do not want to sleep, always feel that the last week that five days Binghuangmaluan work life to make a summary memo, the heart has a bottom, to sleep soundly.
There were 3 things that were done last week.

The first thing: test case execution

In this matter, there is no big problem, basically belong to regression test and smoke test, because it is a very mature product, return to the general problem is less, smoke test, the newly developed software bug many, find it is relatively easy.
But as one of the next week's regular jobs, there are a few things to keep in mind:
1. Improve the speed of use case execution, each time use cases, execution will have some do not understand or know how to execute, perhaps with others to communicate with the beginning is how familiar with the use case .
According to today's share of content, there is a point to be aware of, is to grasp the strength of regression testing, use case although important, but in a full understanding of the function based on, and do not have to follow the use cases of the implementation of the complete.
　　Use cases are services to test work, but work is not an execution case ~
2. Learn to report bugs, like XC elder sister said, the reported bug directly reflects our workload, so the first report, then you can take the time to confirm the problem slowly, summarize the least steps to reproduce the problem.
In addition, it should be much more efficient to locate the problem with development communication than to confirm it yourself.
Therefore, feel that there is something wrong, the right way is to record immediately, in order to ensure that the problem is not omitted, this aspect should be more bold, not too cautious , anyway, the most is deducted wages ~/laugh/
3. Consolidation of training content
Last week, a total of two training, the first is to learn the cloud control use case execution method, but I do not know what the host or the actual operation, and now although not very necessary, but still should learn it.
The second is the writing of automation use cases, I was the first time in Friday to start writing use cases, but also just to verify the bug, write use cases may be slow to do this thing?
But I think today Hz on the skin function design without use cases to write a use case, I do not know whether it can be written directly or assigned to the task, this remains to be seen .

OK, then the second thing next: User feedback

User feedback is one of the highest priority daily tasks, and it is this work that makes me burn and touch a bag.
Then record the specific case where the problem occurred:
Feedback A: Local authentication is not reproduced, I wait until after work only slowly after the verification, probably the reason seems to be at that time the work is very urgent, although did not delay the work, but did not pay attention to this matter priority, now want to actually is a hidden danger.
Feedback B: Local authentication did not reproduce, the morning test of the same, left a small tail, eat to go, at noon back after the test and then back to the mail, the result was WW said.
Because it is the day of the workday user feedback, operations, users are online, so immediately after verification can continue to communicate with users, but I returned to the mail late, although only a less important problem, but indeed because I delayed the progress of the matter. On the one hand, I did not realize it, and on the other hand there was a very difficult feedback, that is, the immediate appearance of the feedback C.
Two things at the same time in front of me, B easy to verify but the importance of low, c difficult to verify and high importance, in this case I seem to be a bit ignorant, almost the east test of the west, the lack of organized directly lead to inefficient, delay time. In fact, this time to quickly verify the B and reply, then carefully verify that C seems to be the best solution, but the reality is that C is verifying the process, to verify that B needs to switch environment, c a lot of things will be lost, so I rush, forgotten how.
Feedback C: With the feedback B at the same time the important feedback, has been dealt with two user feedback, are the same problem, the local verification has been unable to reproduce the user's problem, then or XC elder sister looked for the same system environment, help me reproduce the problem, and teach me how to say in the Mail (OS: I love xc elder sister, The help is really the feeling of being rescued, but this feedback is equivalent to the full XC sister, so that my work is still not good.
Feedback d:p0 level of important feedback, my spirit completely high tension, but the Local has been unable to replicate, in order to verify a variety of environments and live environment, resulting in a very slow response. Because of this feedback I see not only the operation of the head, but also the boss personally asked the progress, but also the first time to the computer room with a virtual machine, but also no one .../wry smile/. In short, with the feedback that almost all of this confusion was done, I was responsible for the end of the week of user feedback, and I felt a deep sense of frustration.
anyway, summarize it.：
1. In the working hours must try to avoid the cost of time to take the environment, the need for the environment of their own, the priority to ask others whether there is such an environment, have to use others first. Need to take the environment with the computer what's waiting for work (do not forget to do things in the small book, to prevent Forgetting).
2. User feedback does not indicate the specific environment with WIN10 64 or Win7 64-bit verification, no recurrence of the first reply to the mail, tell the operation to continue to communicate with the user, if the environment, the priority use of the same environment authentication, no longer return to the message description. In addition, the message is best to write only objective phenomena and conclusions, do not tell the operation how to work (to avoid mistakes)!!!
3. Believe in your own judgment, there is a lot of feedback on the problem is that may not reproduce, up to restart the computer or re-install software re-test again.
4. The brain will be partitioned, it seems a little more recently, to be able to separate one thing from another, rational point, do not mix a group!
5. Operation gave me a suggestion, let me get a solid-state drive, the virtual machine in the inside, you can quickly switch various environments, but also a variety of environments to verify,you can discuss it with your sister JL tomorrow .。

Third thing: Modify point validation

Modify point verification basically is the JL elder sister taught me, remember the process:
1. Look at the description of the change point, first to reproduce the previous situation
2. It is best to find the development of the requirements before the test package, but these are the several times I have to take me to the right, I do not know what the development said what the meaning of the need for a few things: the revision is based on which version, what changed the content, whether or not to affect other modules; , how to verify the modification points, which modules should be returned, and all related bugs involved.
3. After the package comes out, take a look at the diff file in the bag and see where the development has changed.
4. Start verifying the modification point function, and return all related modules to the bug involved.
5. After the verification, spend half an hour to conduct a random test.
6. Test progress should be synchronized on the task platform every day.
7. Verification through, start to supplement the new version of the use case, involving module use cases and regression use cases, no operation, need to find the JL sister confirmed.
8. Finally, the use case is finished, the bug is turned off, you can modify the task platform status, the modification point verification is complete.

Remember Me Binghuangmaluan week (0808-0812)--user feedback and modification point verification