On the afternoon of June 23, July 12, I attended classes as usual. When I named the class, I found a strange face behind me. I thought this was a student from the recruitment department who asked the consultant to attend the class, the admissions department forgot to inform me in advance.
I paid special attention to this "student". He was very careful when he listened to the course and remembered the diligence and happiness when taking notes. He should be a studious student.
In the first class, I learned it only after asking. He was a journalist who specialized in class experience. During the second class, he also took some photos.
Today I saw a Southern Metropolis Daily article "Software defects were discovered one by one" and found that the content in the article is my class content ^_^
Electronic link of the original article: http://epaper.nddaily.com/E/html/2008-07/15/content_515146.htm
The full text is as follows:
○ Time: Afternoon, January 1, July 12
○ Location: Xinyi vocational training school software testing campus
○ Subject: Software defects
As the name suggests, software testing courses are naturally intended to teach students to test software defects. However, after listening to a software test lesson, the reporter found that software testing has many specifications and specifications, not only are there a lot of precautions when testing Software defects, but there are even a lot of taboos when reporting software defects. The words in the text must be carefully considered. If you are not careful, you may offend people!
Software testing rejects fuzzy terms
At the beginning of the software defect course, the teacher began to ask questions to review the content of the previous lesson. "What is software defect ?" The person who was clicked seemed confident: "Software defects, such as program errors, cannot meet user requirements ." The reporter also felt that the answer was well-rounded, but the teacher shook his head: "in software testing, we must avoid the use of fuzzy terms such as 'Wait, developers cannot find out the specific causes of defects from 'etc. In summary, all faults that do not meet user needs are defects ."
"What are the causes of defects ?" The second classmate was a little nervous: "There are many reasons for poor communication between people, incomplete documents, or even no documents, and the participants are overly confident ......" The reporter was surprised to hear the answers from the students. Why is there even a reason for "the participants are over-confident? The teacher was clearly satisfied with the student's answer: "There are many causes of Software defects, some of which are subjective mistakes, such as the inconfidence of the participants. Some developers often say "no problem, I know, I have done it before" without a clear explanation of the customer's requirements. The software produced in the result is inconsistent with the customer's requirements. This reminds us that software work must listen to the opinions of others and listen more or less ."
The defect is that the expression is inaccurate.
After the study, the teacher turned on the magic light and a line of big words appeared on the screen: "The necessity of reproduction and optimization defects ." The reporter was suddenly stunned. Review and report defects both need to be reproduced and can be understood. Do defects still need to be optimized? The instructor explained: "The optimization defect is just a simplified term. The full name should be the optimization defect report. How can we make the defect report clearer ."
"What would you say if you find a defect ?" The instructor demonstrated a case. Create a text document, input the word "Unicom", save it, and close it. When you open the document again, it turns out to be garbled. "This is obviously a defect. Which one can express it ?" A girl stood up confidently: "Create a text document on the desktop, enter 'connection', save it, close it, and then ......" The teacher smiled and said, "'create a text document on the desktop 'is incorrect. The correct expression should be 'create a text document on the blank area on the desktop'. This is a small mistake. Although developers will understand what you mean, but try to be accurate. The second mistake is to use a lot of things, which will make people look messy." The girl immediately understood: "Yes, sequence should be used, such as step 1 and Step 2 ."
The abuse of punctuation in writing defect reports can lead to offending people.
"Pay attention to some important points when reporting defects, especially when using declarative statements with objective tone. Do not add emotional words and symbols, such as exclamation marks and question marks ." There was a defect report sample on the magic lamp, one of which said, "Do you developers use your heels to consider the problem? Actually. TXT is written. Txk !" Let reporters and students laugh. However, the teacher apparently did not smile: "Don't laugh, many people may unconsciously vent their emotions under work pressure. Similar cases have not happened in actual testing. But do not make such a mistake. Your opposition will impede communication, affect the project process, and affect your career development ."
Views of trainees
"I feel that the teacher is very practical ." Chen junxian, a trainee, told reporters that the course talked about many details and precautions in practical application. "This course is very instructive for future work. These problems will certainly be encountered at work ."