Chapter One: Introduction
Problem: Engineers do not see how their source code is specifically executed on the user's machine, and can hardly reproduce the problem of the program completely, then how to properly modify a software or program?
Chapter II: Personal Skills and processes
Question one: How can I tell if a unit test is successful? Is the code coverage of 100%?
Question two: How do unit tests overwrite all code paths? How do you integrate unit tests into the framework of automated tests?
Question three: If a module is found to be "backward", then it is necessary to do each module regression testing, or only the "backward" module to do regression testing?
Question four: Can VSTS test code written in Java or in other programming languages?
Chapter III: The growth of software engineers
Question one: As for the growth of software engineers, do you need to have a unique understanding of software design ideas and engineering ideas in this growing process? Or is it right to suck other people's thoughts?
Question two: The company will choose the technical skills very good but the professional skills are poor or will choose technical skills general but professional skills are good?
The fourth chapter: two people cooperation
Question: What is a class with a county-style constructor and destructor?
Fifth: Teams and processes
Question: Do you have to have a team working model if you work outside?
Doubts about chapter 1-5 of the Law of construction