Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Improving Untestable Code

676 views

Published on

All developers run into this. You inherit code, a lot of it and some of it decades old. When the system is a revenue stream you can't simply rewrite it so what is a geek to do? Follow through how The GForge Group is working to take the rough edges out of their code and their process.

Published in: Technology
  • D0WNL0AD FULL ▶ ▶ ▶ ▶ http://1lite.top/hN0Ha ◀ ◀ ◀ ◀
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

Improving Untestable Code

  1. 1. Improving Untestable Code
  2. 2. BackgroundChallenges we faced with existing Codebase:● Code diversity● Dependency issues● Codebase size● Team size● Subversion● Thirst for Innovation
  3. 3. The End Game● Test automation (phpUnit, Selenium)● Build automation (Jenkins)● Code Reviews● Live code rolls to gforge.com
  4. 4. Taking the First Steps● Migrating SVN to Git● Focused, Functional Testing● Code Reviews● Code rolls to gforge.com
  5. 5. Moving ForwardShort term:● Add REST API● Jenkins IntegrationLong term:● Add Selenium Tests● Server-side Code Reviews● Code Refactoring
  6. 6. Recap
  7. 7. Questions?twitter.com/gforgegrouptwitter.com/tonybibbslinkedin.com/company/gforge-group-inc-https://gforgegroup.comhttp://blog.gforgegroup.com

×