QA Wizard Pro reports always contain a starting and ending time, which is useful for understanding how long the script took to run. However, if you want to time specific sections in a script you can use the Stopwatch functions to return time in milliseconds or in HH:MM:SS format.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponArchive for November, 2011
Andrew Horner, one of our Sales Engineers, was recently on-site with a customer that purchased Surround SCM, and had a large amount of source code which they wanted to import into Surround SCM from another tool. The customer had also been using a source code plug-in that allowed them to perform source code control (SCC) actions from within Visual Studio. Surround SCM has a similar plug-in that allows you to perform all of the standard SCC actions as well as other actions specific to Surround SCM, such as attaching source code changes to an item in TestTrack Pro.
In this post, Andrew explains how to bind to Surround SCM as the source code provider for an existing project. This example uses one of our sample Visual Studio solutions, Bug Reporter, that is currently bound with Visual SourceSafe, and shows you how to change the binding from Visual SourceSafe to Surround SCM Integration Provider. If you’re converting from another source code management tool, the steps will be similar.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponSeapine will be exhibiting at the EuroSTAR Test Tools and Services Exhibition, which runs alongside the EuroSTAR Software Testing Conference 2011. This year, EuroSTAR 2011 takes place from November 21-24 in Manchester, UK. The exhibition segment of the conference opens on Tuesday and closes after the last coffee break on Thursday evening. You can find Seapine at Stand 90.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
The TestTrack Agile Task Board is a fully configurable web interface, enabling teams to work with TestTrack in a streamlined interface configured to match the way they work.
Let’s look at how a team can set up the Agile Task Board to deliver the information they need for their project. Logging onto the Task Board presents a view of tasks to do, in progress, blocked, and completed. Configuration options can be accessed across the top of the page.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
Thanks to everyone who joined us for our Scaling Agile for Project Teams webinar. The recording is now available on YouTube if you missed the webinar or want to watch it again. Q&A from the session follows.
Continue reading… Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
Agile methodologies are all about speed and simplicity. In the early days of Agile, simplicity was represented in the form of 3 X 5 notecards, which were used to record user stories, tasks, and feature backlogs, among other things. Even today, most teams exploring Agile will start off with a whiteboard and stack of index cards. After the novelty wears off, and the team gets into the thick of a release, they start looking for software tools that can maintain the collaborative nature of the whiteboard while adding the ability to automate some work and also add collaboration with remote team members.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponWhen do you ship an application? The answer seems simple—you ship when it’s ready. However, there are many possible definitions of “ready.”
According to Seapine Software’s Peter Varhol, customers, users, and development teams must all agree on what “ready” means—before work begins on the project. Peter discusses this issue in his presentation, When to Ship: Using Automation to Determine Application Deployment Readiness, on Wednesday, November 9, at the Better Software Conference East.
If there is no common consensus on what “ready” means, you may be tempted to release an application before its product goals are met. Peter presents different approaches to determining when an application has the required quality to be ready to ship.
Learn the factors to base your ready-to-ship decision on, so the project team and the business will know whether to continue working or declare, “Ready.”
TestTrack’s sample project includes a sample workflow for managing requirements and requirement documents. In most cases, customers base their workflow on the sample, but want to tweak it to meet their needs. This article explains how to make three quick tweaks to the sample workflow: configuring when requirements and requirement documents are locked, enabling test cases to be generated from requirements, and configuring the workflow states and events.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponThere were many updates to the blog in October. Here is our monthly recap:
Working with HTML-formatted Text in the TestTrack SDK – Explains how the TestTrack SOAP SDK supports HTML-formatted text.
Internal Displacement – Explains how QA Wizard Pro’s .Net invocation technology can come in handy when dealing with third-party controls and technologies.
Webinar Recording – Requirements and Agile: Keeping up with Change – Explains how to bridge gaps between user stories and requirements and reduce documentation needs while maintaining a minimal level of formal requirements for validation and traceability.
Video: Surround SCM and Microsoft Office Integration – This video shows you how the integration works and how to do a few basic things, including viewing file history, viewing differences between document versions, and merging different versions of a document.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
