Thoughts on "The way of software testing by Microsoft" (i)

In this e-Book of the sky, I still like to read paper books, like to read the taste of the book, like tasting a delicious meal. Recently got a "Microsoft's software Testing the road", gnawing for a while, every time to pick up to see the contents of the forgotten, remember before a leader always taught us: "To continue to summarize, to accumulate, so that will progress!" "Every time before listening to this is annoying, and then work long to know how important the summary, now in order to remember the contents of this book, I decided to write a review, think where to write where."

　　The first part:

The first chapter of Microsoft software Engineering

Chapter II "Microsoft's software Testing engineer"

Chapter III "Engineering life cycle"

After reading, I want to say: Oh, the original Big company is this appearance. Next or talk about our own, work in a small company, feel the team like a guerrilla, may use anti-Japanese war in the volunteers to describe more appropriate, more complex, organized, have their own fighting mode, but the discipline is slightly poor, although "organizational" sent a lot of people to "reform", but the implementation of the difficulties, At last, they died halfway. The company each year according to the project situation of the team reorganization, promote staff reuse, also because I participated in a number of product testing work, from the product bid to release acceptance of all the process, which makes people sound a bit complicated, a test engineer need to go through so much, I started the time also very rejection of this mode, Later slowly figured out, it is because experienced so much to let oneself have the opportunity to learn more, work should not be confined to a region, to continue to expand their knowledge, experience the more you will find yourself missing more, and in this process will have harvest surprise, not much explanation, we all know.

　　Testing career development, we always see two choices: one is the technical direction, the other is the management direction. In fact, for the new people do not have to be too obsessed with this problem, because when you work to a certain degree of time, nature has made a choice, the individual feel that the work does not need to be against their own, the person only according to their favorite direction to take full advantage of their own. The book refers to the various development of the test grade, for the confused person is a good hint, the level is mainly based on the depth of technology, the breadth of technology and influence range to differentiate, the scope of influence from a narrow definition of product functions to a series of functions, a complete product, Influence can be extended based on the various aspects of testing, or it can be based on a single aspect of the technical field. My impression is that learning, testing is the same, the more you learn, the higher the level of technology, you will have the ability to maintain their status, the higher the status, your influence will be greater.

Engineering life cycle, the author takes cooking as an example to describe a process approach: through the coordination of various resources, according to the circumstances of flexible adjustment. is the orderly or flexible, all have advantages, not a software development model for all products, different products need different ways to achieve, although there will be many changes in the actual operation, but many process methods in practice has been widely used, but also in the practice of the process of significant experimentation and innovation. The traditional software engineering model has waterfall mode, spiral mode and agile development. In addition to the second, I have experienced the other two and have been developing agile all the time. Quality improvement is the definition of work objectives, the designation and execution of plans to achieve the objectives, the inspection and determination of the expected results, and the modification of the work procedures to complete the plan if the expected results are not achieved. The Deming cycle (or PDCA cycle) is a method of describing the process, which ensures that the product quality meets expectations. Prior to reading "Software testing and continuous quality improvement", "continuous integration, improve software quality and reduce risk," and other quality-related books, the company's leadership has advocated process improvement, the project team has made a variety of attempts, and the Deming cycle practice, and achieved some results. My summary is the sentence:A good process is a process, that results in good software.

Thoughts on "The way of software testing by Microsoft" (i)