Pre-tested Commit

With TeamCity's Pre-tested Commit feature (available in IntelliJ IDEA, Eclipse, and Microsoft Visual Studio), the developer's changes to be committed to the Version Control System (VCS) are first tested on the server bypassing the VCS:

• If the committed changes fail the tests, the code is not integrated and the developer is notified so he can safely work on a fix. The bad code doesn't affect the team and work is not interrupted
• If the build is successful, the changes are committed to the VCS automatically

Typically, your team submits code to Version Control before verifying that it works, and risks breaking the build every single time — causing more problems than necessary. That's why TeamCity is different.

Unlike the standard scenario (edit, commit, verify), TeamCity's Pre-tested Commit feature allows you to remotely verify your changes before committing them to the VCS.

If your changes pass, TeamCity (in cooperation with your IDE) automatically commits them to Version Control. If they fail, your code won't be submitted to the VCS and you'll receive a notification (by email, IM, your Windows System Tray, or in your IDE), allowing you to fix the failed code immediately. And unlike the standard scenario, you'll always know who broke the code. Most importantly, your team never stops working and there is never broken code in your Version Control.