1 / 26

Automated Builds and Testing: Streamlining Software Development with Best Practices

Discover the best practices for automated builds and testing in software development. Learn how effective automation enhances team collaboration, increases code quality, and simplifies processes across projects. This presentation covers key topics such as the benefits of automated testing, handling multi-developer environments, and resolving common issues like merging changes and writing unit tests. Explore tools including MSBuild, NAnt, and automated testing frameworks like Selenium. Gain insights to improve your software development lifecycle, ensuring cleaner and more efficient code management.

fola
Download Presentation

Automated Builds and Testing: Streamlining Software Development with Best Practices

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Automated Builds and Testing Wm. Barrett Simms FrontRunnerMD wbsimms@gmail.com 781.405.4686 Twitter : @wbsimms

  2. Systems Administrator • Linux – Solaris • Perl • Java • .NET/C# • Agile Project Manager • I love what I do for work. Whoami – Past to Present

  3. How I build software How this helps teams Techniques Tools Show a fairly complete approach What you’ll learn

  4. WHY?

  5. Automated Build/Test Benefits

  6. Problems?

  7. Multiple Developers

  8. Dependent Projects Code Smell: Shotgun Surgery!!

  9. Database Changes

  10. Branching and Merging Main Line ??? Branch 2 Branch 1

  11. Mainline merge process

  12. Buildservers Test results are published to team and viewable by all.

  13. Unit tests = Quality Software Automated testing

  14. Typical bug velocity

  15. Negative bug velocity

  16. I can’t write unit tests because… • I have a UI • WaitN, QTP, Selenium • Fixing someone else’s poorly written code • Refactoring, training • I use a database • The tricky part. Common resistance

  17. Common Questions • How do I write unit tests when I require a database • How do I merge changes? • How do I add default/test data? • How do I update… • Buildserver • Production site(s) Databases – The tricky part

  18. Use SQL scripts! • Table • View • Procedures • Key and Constraints • Default Data • Test Data A decent answer

  19. Automated Build Server • TFS • Auto Generate Database • DumpDatabase/CreateDatabase • Automated Testing • MSTest My one slide solution

  20. DumpDatabaseToSql.exe • Microsoft.SqlServer.Management.Smo Generating the scripts

  21. Generating the scripts (2)

  22. All schema files in revision control. Database Files

  23. Creating the database

  24. EdmGen2 • http://archive.msdn.microsoft.com/EdmGen2 Another trick: Entity Framework

  25. Boy Scout Rule • Leave the campground cleaner than you found it. • At least… leave it as you found it. Unit testing with the database

  26. Wrap it all up in a build script. • MSBuild, NAnt…. • I’m using MSBuild… • But prefer NAnt. Finally… sort of…

More Related