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.

1. Improving Untestable Code

2. Background
Challenges we faced with existing Codebase:
● Code diversity
● Dependency issues
● Codebase size
● Team size
● Subversion
● Thirst for Innovation

3. The End Game
● Test automation (phpUnit, Selenium)
● Build automation (Jenkins)
● Code Reviews
● Live code rolls to gforge.com

4. Taking the First Steps
● Migrating SVN to Git
● Focused, Functional Testing
● Code Reviews
● Code rolls to gforge.com

5. Moving Forward
Short term:
● Add REST API
● Jenkins Integration
Long term:
● Add Selenium Tests
● Server-side Code Reviews
● Code Refactoring

6. Recap

7. Questions?
twitter.com/gforgegroup
twitter.com/tonybibbs
linkedin.com/company/gforge-group-inc-
https://gforgegroup.com
http://blog.gforgegroup.com