Improving Untestable Code
0 likes•716 views
The document outlines challenges faced in improving an untestable codebase, including code diversity, dependency issues, and team size. The proposed solutions involve implementing test automation, build automation, and code reviews, alongside migrating from SVN to Git. Future steps include integrating REST APIs and enhancing testing frameworks with Selenium for better long-term quality assurance.
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