A Microsoft day 1. Let us see how the day of each role in the project is spent • Development • Test • Project Manager
Note: There is a focus on each stage of the milestone, and we take the "completion function" stage as an example.
What is the day of Microsoft? Answer: Midnight
why? Because Daily Build is the core of all work and is automatically started in the middle of the night.
Daily Construction Daily Build • Do you know your own version of Windows? • DAILY BUILD Significance: O module can be integrated o as required programmers to put the latest code into the code base • Implement with scripting language and compile / link tool • BVT Build Verification Test O Validate Build • Blocking bug O makes build The problem found in OBVT
2. What is the most worried about programmers before working every day? Answer: Because of his code CHECK-IN, it causes Blocking bug.
why? Because daily build is the foundation of all people work on the same day: programmers need Build to verify interface testing of other modules requires Build discovery new bugs, and verifying the new buil's bugs
What should I do with Blocking Bug? Solve the problem and play patch on today's Build.
The developer's work experience After the BUILD, the first thing is to win, what answers do: Open the defect tracking tool, view the BUG specified to you, solve the high-priority bug. Because of the quality of new features.
Next, the developer will ... From the version control tool CHECK OUT code modification code (solve the BUG or implementation new features) to obtain the latest changes in the version tool, in this machine build and unit test, develop group colleagues for Code ReviewCheck IN code
3. What is the first thing to test? Answer: Open RAID / BMS to view the bug that specifies to you, verify the resolved bug.
Next, the tester will ... • Test today's Build • Record new discovered bugs in RAID / BMS in RAID / BMS
4. Expert consultation • Participants: project manager and development team leader, test team leader • Each unresolved bug O decision BUG priority o can wait until the next milestone or version is solved by RAID / BMS. O Who will solve • Predictive project actual progress and release time
Defect chart
5. Review Microsoft's day • Construction: Daily Build • Development: Solve Blocking Bugs, implementation, Check-Out, Code REVIEW, CHECK-IN • Test: BVT, use test cases for test • Project manager / group length: expert consultation
6. Microsoft's practice solves those common problems? Quality Problem • The previously solved issues have occurred again, need to rework • Improving the release time is premature release, bringing quality and maintenance issues • The problem of test discovery is forgotten or not. • Unable to measure testers and development The work of the staff • The problem in the program is often discovered after the release.
Document Management Questions • Documentation and Programs, Documents become a description of the program results • The project group looks into a burden
Team coordination issues • Developers to fight, when they are integrated, the serious problems in the module are discovered. The changes need to be changed. • Do not keep your company's previous version and code, unable to meet the user's change requirements for older versions • Developers left The project brings a big impact, no one knows where the code is, or cannot read
