I need help in importing test cases from excel to TFS [Version 14.102.25423.0]. As we have to write thousands of old test cases in TFS which seems to be very time consuming task.
I've already tried using- Test Case Migrator Plus. But its not working bcz of-TCMP has stopped working error. I'm unable to find solution for this error. Also there is no alternative I could find for same on Google.
I have also tried using Team Addin for excel but this gives option of importing Data from TFS to Excel but not vise versa.
So Plz let me know if anybody knows any solution or any otheralternative for getting this done.Thanks in Advance!
Note: I've Visual Studio 2015 installed on my VM with Windows 7.
The simplest way to import your test case back to TFS is: Import your test cases from web portal by copy and save. Note you must switch to the grid view first.
For more details take a look at below two links:
Importing Test cases from Excel to TFS
Add feature in TFS to export and import test case to and from TFS with steps,actions and expected result details
If you have multiple/thousands of test cases which need to upload. While TFS does not offer an out-of-the-box feature as a perfect solution. The 3rd-party tool Test Case Migrator Plus you are using seems only until 2013 version and there isn’t the version which supports TFS 2015.
You could still use the grid view, if you use three columns in Excel, you can even import many test cases into TFS at once. Besides depending on what you have as input, you can also do it with a bit of code, e.g. in C#. Just append some text, split columns by \t and rows by \r\n. Use Clipboard.SetText() and then paste in TFS.
There also has been a related user voice, you could vote up to get more attention, TFS PM will kindly review your suggestion:
Exporting Test Cases with Steps to Word/Excel
https://visualstudio.uservoice.com/forums/330519-visual-studio-team-services/suggestions/19582678-exporting-test-cases-with-steps-to-word-excel
Related
We are using floating licenses for an older version of the IBM DOORs requirements management tool. It works great for requirements management, however it is not the right solution for our test procedures and automated test cases. We have recently selected testlink as a cost effective test managament tool to replace test planning in a spreadsheet and word documents. We aim to import our test procedures and to link to JIRA and Jenkins and PyWinAPI test automation. The dream is that Manual Tests can create JIRA tickets easily linked to the test step... and ultimately produce a dashboard of test reports that provide greater visibility on test coverage using live data for both manual and automated testing.
As for requirements, yes we can import the Requirements manualy from csv files. However we will have to do this manual import regularily making updates at each aproved requirement change in DOORS. I would prefer a longterm solution to connect DOORS to TestLink in one direction. And once a week an automation can run and feed new requirements or modified requirements into TestLink automatically to keep the two in synch.
We are building TestLink on top of mysql, and DOORS is also a database. Can we write some SQL and scripting that can pull the desired data from DOORS (new and updated) and push it to testlink. I am wondering if anyone has ever done this before or something similar? Thanks very much.
For only one particular SSIS package (v. 2005) I am getting the following error when trying to open the script task...
TITLE: Microsoft Visual Studio
Cannot show the editor for this task.
ADDITIONAL INFORMATION:
The operation could not be completed. (Microsoft.VisualBasic.Vsa.DT)
BUTTONS:
OK
I need to get into this to be able to edit it, also I am in the process of upgrading it to 2014. Once upgraded I can get in, but there is no code, so assume the upgrade is not working as it=self cannot see the code within.
I have tried other machines - same problem.
I have tried other packages - they work fine - even in the same solution.
I have tried a few resets found on the net/re-installs - same problem.
Clearly its something to do with this specific package only, but I am stumped.
I would expect to be able to open the Script task like any other, and be able to edit it. I would also expect the upgrade to work and contain the code.
If you want to read the Script Task code, open the package file (.dtsx) using a text editor (Notepad++), and search for the Script Task code, copy the Script Task code and recreate the script and paste the code within the Script editor.
If you have a problem with Script Tasks in visual studio 2005, then copy the code to an external file, upgrade the package to 2014 then paste the code inside the Script Task (since it will be empty after upgrade)
In my current project we are using Microsoft Test Manager 2013. We have prepared test cases in excel. How can we upload prepared test cases from excel to MTM 2013.
Additionally to the answer by #MrHinsh:
Check Create Manual Tests using Team Web Access and look for the question Can I copy test cases and test steps from an existing Excel worksheet? in the Q&A part.
I do this using the free tool tcmimport: http://tcmimport.codeplex.com/
You can do this by copying and pasting into the test grid in the web access for TFS 2013. In the web access to to the test tab and for the test suit you want to add items to switch to grid mode. Then past in in the required format.
I recommend preparing test cases directly in Web Access or MTM. Your current workflow is a dysfunction resulting from Quality Centre use 😊.
I am looking for information regarding Visual Studio 2013 and working with SQL Server projects using VS 2013. We are currently working on a project where were're using a database that already exists and is used by an ERP application. We're creating SQL Scripts that would alter and create fields on a table on the target database.
Now, we're not looking to "publish" those scripts, but create postdeploy scripts instead, which contains all the necessary SQL scripts in the order they need to be run. Everything is working fine. When we build the project, we get a fresh copy of the PostDeploy.sql script file that we run across a target database.
At the moment, the script looks at a table, if the column that needs to be added exists, it DROPS it and then recreates it. This is fine for the testing phase, but once we go live, there will be several stages of the databases that the code needs to be tested on. The column may already exist from before and in that case, we wouldn't want to DROP that column, instead, we want to do schema and data level compare and just get over the objects that are DIFFERENT, so that the column doesn't need to be dropped, instead just "updated". I hope I am not being vague when I ask this question.
I found this video: https://www.youtube.com/watch?v=AuVpmu9CKRY and I am not sure if that is what I need to do? I would love any suggestions from you guys..
Have a wonderful day!
Well, this isn't really the best use for SSDT/DB Projects. Ideally, you'd want to pull the schema into a project and tweak that project to look the way you want. Rename columns, change types, etc. Because it sounds like this is a 3rd party app, you'd want some environment that can serve as your baseline - when you run whatever upgrade script is sent by the vendor, it goes against that environment. You'd then want to pull the appropriate changes into your project.
Once you have a project that looks the way you want, you use the publish option against your target database. In your case, I'd likely recommend generating a script. If you're in the VS environment, you can take a look at both the script and a summary of what will be changed.
For data compares, I'd really consider something like Red Gate's SQL Data Compare (pro edition if you can). You can set up a data compare against your baseline and automate pushing the data changes. You can do that through post-deploy scripts, but you'll need to hand-code the data inserts, updates, and deletes yourself.
I've blogged about SSDT before and that may give you some ideas. Jamie Thomson has also written quite a bit about Database/SQL Projects and inspired quite a bit of what I've done.
http://schottsql.blogspot.com/2013/10/all-ssdt-articles.html
How do I change process template to MSF for Agile on an already existing team project in TFS 2010?
We have upgraded our TFS 2008 to 2010, and now I would also like to change the process template to MSF for Agile (currently CMMI).
We haven't used the workitem functionality much so if some information gets lost in the conversion doesn't matter.
Once you've created a Team Project, you unfortunately can't just upload a new process template. As Robaticus says, you'll have to download the XML for the template and modify it, then re-upload it. The power tool lets you create NEW templates for NEW team projects, but it won't modify an existing one.
Instead, you can use the witadmin.exe tool (on any computer with Team Explorer installed, under \Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE, or just from a Visual Studio Command Prompt) to export the current workitem definitions and re-import them once you've made your changes.
Luckily, if you're not using workitem tracking much, then this might not be too difficult. You might be able to just delete all the existing workitem types and then re-upload the new types.
If this is too much trouble, consider how much you want to retain your source control history. It might be worth creating a new Team Project with the Agile template and then just moving all your source code into it.
You can't change the process template, however you can change the work item types. So for bugs, tasks you can swap to the Agile definitions.
You can do this in 2010 with witadmin, in 2008 it's importwit, by first downloading the template to disk (you'll need the TFS power tools for this). Then point the console app at bug.xml, task.xml etc..
Usage: witadmin importwitd /collection:collectionurl [/p:project] /f:filename [/e:encoding] [/v]
/collection Specifies the Team Foundation project collection. Use a fully specified URL such as
http://servername:8080/tfs/Collection0.
/p Specifies the team project in which the new work item type is imported. This is required, except when
the validation-only option is used.
/f Specifies the work item type XML definition file to import.
/e Specifies the name of the .NET Framework 2.0 encoding used to import the XML file. For example,
/e:utf-7 will use Unicode (UTF-7) encoding. Encoding is automatically detected whenever possible. If
the encoding cannot be detected, UTF-8 is used.
/v Validates the XML definitions for the work item type, link type, or global workflow without importing
them.
You can export the agile process template to disk, then import the work items into your existing project. You may need the TFS Power Tools to do this.
I may be too late for this question, but the TFS Integration Platform tools could really help here.
See this question on server fault that details on how to move from Scrum For Team System V2 to Microsoft Visual Studio Scrum 1.0.
You would need to setup your own mappings to move from your templates to the target template, but the process is the same.
Please note witadmin.exe could help in some scenarios but TFS Integration Platform is your ultimate choice to achieve this task. There is a user voice item still pending. Please check this SO thread.
I think the best way to accomplish this is to create a new Team Project with "the new" process template and use the TFS Integration tool to migrate your existing WorkItems and choose create a new branch from Source Control, so you'll have new work Items (with the new workflow) and the source control history (as well). You'd even do this across versions of TFS!! (On the case interested on migrate TFS 2005/2008/2010)
Another way might be to use the WorkItem Templates, but I think this is more a kind-of visual style (I've not much experience) applied to the Work Item. To do so, just right click on your project, import the WITDefinition and apply the template by selecting Apply template on desired WorkITems.