This workshop tests whether you understand all the concepts you learned in this hour. It is very helpful to know and understand the answers before starting the next hour's lesson.
What is the main problem with integration?
The number of components makes it difficult.
There are no real tools to ease the pain.
The task is mostly manual, which slows development down.
Conflicts occur between components developed by team members.
What XP practices support integration?
Pair Programming, refactoring, collective ownership, testing, and coding standards.
Pair Programming, on-site customer, collective ownership, testing, and coding standards.
Pair Programming, collective ownership, and testing.
All other practices support it
How do we define a good build?
Passes the customer's acceptance tests.
Compiles and links without error.
The build passes a verification or smoke test.
Source code is checked in and passes unit tests.
Why is a build important?
It's the heartbeat of development and is the best measure of the state of the system.
Enables the customer to know work is being done
Helps to keep the team focused on shipping the product.
Assures the system quality by passing tests.
Write a build script that extracts the latest source from your repository and builds on a clean machine.
Download CruiseControl, install it, and begin to experiment with automating your build from Activity 1.