The Seapine View

When you’re ready to share your Surround SCM evaluation with your team, it’s relatively straightforward to enable access for those users. The following steps will walk you through the process.

Note that by default the administrator user (no password) is the only account that can access Surround SCM. The following steps will let you add additional users to your Surround SCM installation. Also, be sure to open port 4900 (default for the Surround SCM server) on the machine running the server so the rest of your team can connect from their desktops.
Continue reading…

As a consultant, I have been exposed to many different development methodologies and processes. In most cases, assignments are performed by a person that is aware of staff resources and distributes tasks according to the availability of these resources.
Continue reading…

If you are a loyal reader of this blog, chances are that you read Gerhard Kruger’s post about our Visual Studio Integration.  In this article, Gerhard talks about accessing TestTrack Pro items and Surround SCM actions from within Visual Studio. I’d like to present a different angle to this integration, specifically, the TestTrack Pro integration.
Continue reading…

Filtering is a great way to slice data on a daily basis. Filters form the basis for working efficiently with your development and QA artifacts. It’s typical for a customer to have 10,000+ issues/bugs/feature requests in a TestTrack project – filters allow users to narrow that list of data to what is relevant to them at any given moment. In this post, I’m going to highlight the filter run time feature that makes creating and maintaining a usable list of filters much easier.

Continue reading…

I’m pumped up to announce the Seapine User Days 2010 events in London and Munich in late April! We’ll be holding one-day events in both cities, and we’re cramming a ton of stuff in.

Continue reading…

Being able to easily and quickly segregate data by various criteria is a requirement of any product that claims to be “easy to use.” For example, product management is interested in commonly reported issues and feature requests during product planning, but nearing the end of a release cycle they’re focused on critical issues that could delay the release. QA wants to see test runs yet to be executed or those that need to be re-run and development wants to see approved requirements that are ready for implementation. All of these scenarios create the need for distinct and re-usable “views” of the artifacts in TestTrack. This is where TestTrack’s tabbed views can make life much simpler for you as a user.

Continue reading…

The quickest and easiest way to pass a variable value between scripts is to create a repository variable. A repository variable is a sort of “global variable”, accessible by all scripts that interact with an application. Repository variables are by default defined as text values, but can be converted to any type needed using the appropriate function or simply assigned a non-text value.
Continue reading…

Server plug-ins query external reporting services, communicate information about reporting services to client plug-ins, and run requested reports.

The Surround SCM and TestTrack Servers scan for plug-ins in the serverreports directory in the product application directory every 10 minutes. If a new plug-in is found, it is added to the list of available server plug-ins, which is sent to Surround SCM or TestTrack when users request to add external reports.

All server plug-ins must define the following ReportStatus enumeration, which provides return values for several functions in the server plug-in API.
Continue reading…

Client plug-ins are only required if you want to provide the following functionality from Surround SCM or TestTrack:

• Run an external report editor to create or modify reports.
• Run external reports that require parameters, such as filters.

Note: You cannot run external report editors or work with reports with parameters from TestTrack Web.
Continue reading…