Archive for January, 2008
Works with TestTrack 2008 and later
Will not work with TestTrack 7.6 and earlier
Here you’ll find a sample T-SQL query and Excel report that you can use to report on your TestTrack Studio automation rules.
This was written for TestTrack Studio 2008, and won’t work with earlier versions. With 2008, we completely re-did the automation rules table structure so it’s not even close to what you’ll see if you’re using an earlier version. You should upgrade, the 2008 release is really cool! Continue reading…
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
Tags: dashboards, Excel, Reporting, sql server
Jeff Amfahr talks about
Surround SCM on January 23, 2008
It’s possible to use AppleScript and Microsoft Office for the Mac to provide improved integration between Surround SCM and Microsoft Word on the Macintosh. Below are some sample AppleScript snipets that show you how to do this. None of these have full error handling, but should server as an example of how you might leverage these two tools. For all of these samples, open up the AppleScript Script Editor application, paste the script in and save the file as an application.
Continue reading…
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponTags: Applescript, Mac, Microsoft Office, scripts, Surround SCM integrations
Fernando Cremer talks about
Surround SCM on January 03, 2008
Works with Surround SCM 5 and later
Some time ago I wrote an article on how to e-mail a file from Surround SCM after it is checked in. The file that is e-mailed is the latest version from the Surround SCM server.
While the ability to e-mail a file automatically from Surround SCM can be very useful, a better suited solution for your process may be to e-mail the file that exists in a user’s working directory before it is checked in. This gives someone other than the user doing the changes the opportunity to review it. Some testing could also take place. Once the file has gone through a review/approve process, then it can be checked in.
This process can increase the chances that you will only have quality check ins in your source code management system.
Continue reading…
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponTags: triggers, workflow
