It’s not easy to enforce a minimum level of quality in your organization’s code before check-in to version control, but it’s important to try. While application developers have been able to do this for a long time, it hasn’t been a mainstream function of database development environments.
With Toad for Oracle Xpert Edition you can combine the Team Coding feature with the Code Analysis feature I described in my last post and your version control system to ensure good coding policies at check-in and consistency across teams. Team Coding is a collaborative utility that accesses the version control system through the Toad editor. If somebody tries to check in code that does not conform to team or project standards, you can configure Team Coding to deny check-in until the code has been improved.
- Edit code and check it in to your version control system through the Toad for Oracle editor.
- If any of the code violates the standards you’ve set, you’ll receive a validation error that helps you find and repair the offending code.
Click on this 3-minute video of our John Pocknell demonstrating how to use Team Coding in Toad Xpert Edition:
The Team Coding/Code Analysis feature can prevent code quality regression from stretching out your development cycles.
This is part 3 of my 5-part video series designed to help you decide whether Toad for Oracle Xpert Edition is right for you. If you’ve been following along, you’ve seen scenarios in which it can help you optimize code and improve collaboration.
For more details on Code Tuning, have a look at Reason #3 in “Five Ways Toad Xpert Edition Can Help You Write Better Code,” our updated technical brief.
Want to see for yourself how Toad can help you keep sub-standard code out of your version control system? Download a 30-day trial and take Toad Xpert Edition for a test drive.