Market today, saves 90% of migration time The most time efficient and cost effective migration process on the.Migration of all QC elements (Requirements, Bugs, Test Cases, AttachmentsĪnd Links between items) to TFS and their interrelationships links.
Test-drive Scrat today: download your free trial version now (which is a fully working
All of the QC elements (Requirements, Bugs, Test Cases, AttachmentsĪnd Links between items) are accurately migrated to the TFS including their You decide how, to what extent and where to migrate Through an easy to manage wizard, the entire
Contrary to the manual migration traditionallyĮmployed by organizations, Scrat fully automates the process. Process that completes in just a few hours.
Scrat converts and migrates all of your HP Quality Center™ projects and items over Map all States fields in TFS against Quality Center StatesĬonvert existing Quality Center (QC) items to Microsoft TFS TM 2010/2017 Map all "Visible" fields in TFS against Quality Center fields.īased on Fields Mapping this allows you to map data from Quality Center to different data on TFS. Takes Quality Center hierarchy and translate it to Area Paths in TFSĬreates Shared Steps in TFS based on QC Call 2 Test feature.Īllow easy mapping between Quality Cetner users to Support for item attachments and for Steps attachments (Test Cases) This allows you to gradually migrate your work to TFS. The Migration process itself and the end results are saved in XML format.
The migration tool works with an XML repository file that contains the entire information. In this post, I’ll share how we used these tools to rapidly define the requirements for the app, and talk about some topics related to converting the iPad app information architecture to a Windows Store app information architecture.The migration tool is based on wizard allowing easy and fast configuration and usage.įull support for: Requirements, Test Cases and defects.īased on TFS linking ability all migrated items will have the compatible links. We also used Visio 2013 for visually defining the overall functional scope and high-level release plan for the app. This gave us the opportunity to leverage new PowerPoint 2013 storyboarding stencils for defining the app’s User Experience (UX), and TFS for efficiently creating and managing our product backlog. That was the bad news… The good news was that we were able to use Microsoft Team Foundation Server (TFS) - in this case the TFS 2010 version - in conjunction with Visual Studio 2012. We had a very short timeline and limited budget to work with. Read More…Īt AIS, we work with clients to help define the overall vision, scope and detailed requirements for the applications they want to build. I recently had the opportunity to work on a project where a client wanted to reach a new set of users through a Windows Store app that was based on an existing iPad app. Executions of other steps obviously follow, but this post is primarily concerned with standing up that environment. In reality the process of removing and creating VMs is treated as just one “step” in our build-out process. We use the same XML-driven framework to build out our machines. In a way, this allows us to test both pieces at the same time.Īt this point I should throw in the disclaimer that this blog post builds on one written by my colleague David Baber: Driving PowerShell With XML.
However, we wanted something that could not only exercise our code base, but also our scripts that we use for building our environment. This may sound like overkill and I’ve seen other approaches that use snapshots and revert each night…and I think that’s great. We don’t use snapshots we actually delete and provision a series of VMs. Today I want to talk about a process we created for building out machines using Virtual Machine Manager (VMM) as part of our daily build process within Team Foundation Server (TFS).Īs part of our nightly build process, we actually recreate the entire environment from scratch.