TestTrack security groups allow the administrator to configure the level of access a user has. From having access to only specific workflow events to only seeing fields that apply to the user, security groups allow the administrator to ensure that the user is not flooded with options and fields. As your implementation of TestTrack grows, your number of security groups may as well. To easily compare these groups and analyze why one gives users a level of access that another does not, TestTrack 2011 introduces a new report that allows you to compare security groups in a more efficient manner. This video shows you how.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponArchive for October, 2010
TestTrack list windows display defects, test cases, requirements and more. Knowing what features are available will help you work more efficiently with TestTrack. In this video, I share some tips for working with TestTrack list windows.
In a recent video I posted, I highlighted the rich feature set provided by the Surround SCM integration package with Visual Studio. In this video, I’ll show you how to easily get started using this integration.
Note that this video assumes your solution does not have any prior bindings. If yours does, you may want to review tips on how to remove source control bindings.
Being able to get your work done from within your IDE can greatly increase your productivity. Having a tightly integrated source code management tool with your IDE is an integral part of this. Surround SCM provides a rich feature set as part of its integration package with Visual Studio, as highlighted in this video.
Thanks to everyone who joined us for the Zen Mastery of the TestTrack SDK webinar. The recording is now available if you missed the webinar or want to watch it again. Q&A from the session follows.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponEvery once in a while we get feature requests for new columns in the Surround SCM Source View window. Some of the most popular column requests are for the comments that were part of the last check in of a file, the last user who performed a check in, and the last defect number the file was attached to. (By the way, make sure you are submitting your feature requests. That’s the only way we’ll know about them.)
While all feature requests are reviewed, and may be implemented in a future release, we haven’t yet added new columns to the Source View. So, I’m going to show you how to use Surround SCM’s customer fields and triggers to create your own Source View columns.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
In the Look Back in Agile: The Sprint Retrospective eBook I talked about the purpose and elements of a good retrospective. I strongly emphasized the need for action items to make sure the team is not only inspecting but also adapting their practices as they progress through the project. If you’ve already conducted a productive retrospective then you probably have quite a few actions.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
I’ve been a member of the Surround SCM team for nearly a year and half (including my co-op) and there are still little features of Surround SCM I’ve never used or wasn’t aware of. Just this morning I was looking into a defect about the “Image Comparison” tool and it hit me – up until that point I had no idea Surround even had an image diff feature. So I started playing around with it and, as it turns out, it’s a nice little tool. I imagine it would be quite handy if you were a graphic designer or someone who spent a decent amount of time working with images.
Continue reading…
One of the more popular feature requests from QA Wizard Pro customers is exception handling. We added two well-known exception handling techniques to QA Wizard Pro 2011: Try…Catch statements and On Error statements.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponDuplicating changes across branches is critical to streamlining your development efforts because it eliminates the need to manually make the same change in multiple locations. Surround SCM’s Duplicate Change functionality allows you to take a change associated with a TestTrack defect, changelist, label, or a set of files and copy it to any branch in the tree. This video provides an overview of this feature.
