Improving Untestable Code

  • 441 views
Uploaded 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 …

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.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
441
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
1
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Improving Untestable Code
  • 2. BackgroundChallenges 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 ForwardShort term:● Add REST API● Jenkins IntegrationLong term:● Add Selenium Tests● Server-side Code Reviews● Code Refactoring
  • 6. Recap
  • 7. Questions?twitter.com/gforgegrouptwitter.com/tonybibbslinkedin.com/company/gforge-group-inc-https://gforgegroup.comhttp://blog.gforgegroup.com