[Software Engineering] Does XP Require a full set of automated tests?

Today, I saw Mr. Zhang put forward his views on XP application automated testing:

"

-- As mentioned above, "Using XP framework" accounts for 43%, and only 30% of automated testing tools are used. So what is the 13% in the middle? Will it use XP, but will not use automated testing tools (such as xunit )? Obviously, the samples in this survey are problematic, and the organization and problem settings of the survey also seem to have defects. Regarding my comments, qingrun responded:

I don't think this is an inevitable connection with whether XP will be used with automated testing tools. If XP's key practices are used, this is a choice for a company/team, any company/team can choose to adopt a certain process or development method at a certain stage based on their own characteristics or project characteristics, in another stage, select another process or development method. There is a difference between "use" and "use all". Therefore, I don't think there is a serious fault of 13% of the difference between the two data.

Does the XP team need automated testing tools? Are you talking nonsense, fever 40 degrees Celsius? In the development cycle of XP, every time you have finished code refactoring, You can discard many automated testing tools such as xunit and testng for manual testing? Manual testing is also feasible for system/acceptance testing. How can you perform manual testing for a large number of unit tests? What exactly makes it difficult for you to keep yourself close to the distance and simplify your work? To defend your brother's "43% of enterprises use XP", is it true? Too tired. I think you are leaving for reasons. The conclusion is that XP teams must use automated testing tools, whether unit testing, integration testing, or system testing, and should be used in large quantities.

"Any company/team can choose to adopt a certain process or development method at a certain stage based on their own characteristics or project characteristics, in another stage, we plan to choose another process or development method. "This is correct, but this is only the case in principle.

For XP, specific analysis is required. We can divide all XP practices into two categories: core practices and alternative practices ). If you discard the core practice of XP, your process cannot be called XP. Using automated testing tools is such a core practice, which can be derived from other XP core practices based on logical analysis. Qingrun said, "whether it will be used or not, which of the key practices in XP can be selected by a company/team, some cannot. We distinguish XP from other processes to see if a process is XP. The key is to see if people have achieved these "Key Practices" and whether they comply with the XP principles and spirit. Xp x means extreme, which means that many places should have strict requirements (high-disciplined) to do its best. If key core practices are available, it is not XP, is MP (mild programming ). It is hard to imagine how XP can proceed without using automated testing tools and how it can ensure agility.

"

The text above is directly referenced without any modification.

In this article, I felt an exception, that is, whether the things that Mr. Zhang learned have been too accurate. According to the words of Mr. Mao, the founding chairman, they are: Local capitalism!

I personally don't know much about XP and dare not call it an expert in this field. I do not know much about testing. However, I have read some things in these two aspects and will not know anything about them.

However, for the sake of authority and accuracy, I would like to ask the old man He Xiaojie from the testing age to explain this question. I will contact him over the past two days to check his time.

In addition, you need to declare:

Mr. Zhang said that I am maintaining my elder brother!

Mr. Zhang must be referring to the bear festival. I know a little about the resentment between Zhang and the bear festival. However, here, I think this is a very strange name, I have never thought that the bear festival is my brother, and the bear festival is younger than me. How can I become my brother? Does Mr. Zhang give me a hat like this? Is it a bit of a sense of private revenge?

-- How many other behaviors and texts can be guessed without any evidence in Mr Zhang's article? This seems to be a question worth pondering!

In addition, I think that, whether it is the RUP/up or XP, if they all need to be used as a whole to count as their own concept, then, is it empty to crop up or update the RUP?

My experience is as follows:

As long as it is applicable to the methods used to solve the actual problems in my project, whether they belong to RUP/up or XP, I will use it out, instead of using the framework of RUP/up, however, some methods and suggestions in XP are rejected. This is the essence of software engineering, not an abstract void theory!

Any part of the RUP/up and XP can be split and used as needed, as long as any part is used, neither of us can deny that we have adopted or borrowed from RUP/up or XP. Many people may think that they have used up or XP, instead, we will not seriously investigate whether all of them use the RUP/up or XP.

In Mr. Zhang's text, the stubbornness and viewpoint of the original doctrine are very strong and obvious.

It is hard for me to believe that, with such stubborn views and thinking, Mr. Zhang is able to provide services to his own customers and help them solve practical problems. Such stubborn thinking may expand the problems that users can solve quickly (just like the Cultural Revolution) and bring a lot of unnecessary losses and waste to customers.

Mr Zhang's thinking and practices are obviously not the normal thinking of programmers starting from the bottom layer, maybe Mr. Zhang has no such experience as the underlying Programmer (I have never seen any related content in his resume, he cannot understand the ideas and considerations of our programmers starting from the lowest layer.

Software Engineering aims to be practical, to solve practical problems, rather than to speak out, not to publicize the profession and depth of itself, but to attack others and to publicize its position and influence, exaggerate your practices to belittle others. Solving the problem is the foundation of software engineering, rather than taking it out of context!

I hope Mr. Zhang will reflect on this sentence.