Wiki

[[third_party_codeline_patlet]] JayFlowers Trace: » third_party_codeline_patlet Context You want to focus on building the components for which you can add the most value, not on basic functionality that you can easily buy. Your codeline is associated with a set of external components that you will ship with your product. You may customize some of these to fit your needs. You need to associate versions of these components with your product. When you create your Private Workspace (6) or when you build a release for distribution, you need to associate these components with the version you are checking out. You also want your Repository (7) to contain the complete set of components that make up your system. This pattern shows how to track the third-party components in the same way you track your own code. ...

[[unit_test_patlet]] JayFlowers Trace: » unit_test_patlet This needs a rewrite Context Sometimes a Smoke Test is not enough to test a change in detail when you are working on a module, especially when you are working on new code. This pattern shows you how to test detailed changes so that you can ensure the quality of your codeline. Problem How do you test whether a module still works as it should after you make a change? ...

[[active_development_line_patlet]] JayFlowers Trace: » active_development_line_patlet Context You have an evolving codeline that has code intended to work with a future product release. You are doing most of your work on a Mainline. When you are working in a dynamic development environment, many people are changing the code. Team members are working toward making the system better, but any change can break the system, and changes can conflict. This pattern helps you balance stability and progress in an active development effort. ...

[[development_workspace]] JayFlowers Trace: » development_workspace Context All developers and the Integration Build work in their own Private Workspaces yet there needs to be constancy between them. This pattern is a means to define the structure of the Private Workspace. Problem With many Private Workspaces how do you mitigate the chance that differences between them will cause bugs? Solution Define a structured workspace and location for it in private environments. Allow for variation in the content and not the structure. ...

[[traceability_and_continuous_integration]] JayFlowers Trace: » traceability_and_continuous_integration Introduction I am a proponent of CI (Continuous Integration). I have read a great deal of material on Agile. Yet I have never seen anyone folding a ticket tracking system into a CI process. I have seen them spoken to separately. The industry standard CI servers and tools for scripting builds do not integrate with ticket tracking system either. I have found the synergy created when a ticket tracking system is integrated into CI to be invaluable. Normally you hear people expousing the virtues of CI they talk about rapid feedback, quick identification of bugs, reliability…, these are not things this article will discuss. Here I will discuss the value of the record results of the build. The value of traceability it adds to a project. It shows a historic list of changes to the project. Adding the context of why those changes were made to the history dramatically increases its value. ...

[[articles]] JayFlowers Articles :: Software Projects :: Works in Progress Unit Testing in .NET Projects :: Code Examples Now is a pretty exciting time for unit testing in .NET. Tremendous progress is being made on several fronts: IDE integration, process integration, and new test fixtures. Jay Flowers and Andrew Stopford explain how to use Visual Studio’s new integrated unit testing, as well as the NUnit and MbUnit testing frameworks. articles.txt · Last modified: 2005/10/10 14:21 by jflowers