We have test cases already present in ALM and now we want to migrate to MTM(Microsoft Test Manager 2017).
Already viewed some tool which are not supported by TFS and there are some 3rd party tools which are paid. We are looking for some exposed API's which can be automated and support migration of test cases from ALM to TFS.
Also free source tool would help but didn't found any tool yet.
Can someone please help to know how to migrate all the test cases from ALM to TFS?
What you can do is export your tests to xls and create a migration application that will use TFS API and import those tests.
For export check this link
For TFS API check this link (check test and test plan section)
Related
I've been asked to generate code churn report, but I don't have any clue on how to do it.
As a company, we are using DevOps On-Premises server.
After some analysis, I found that below articles could be helpful to achieve my requirement.
Analyze and report on code churn and coverage using the code churn and run coverage perspectives
Create Excel reports from a work item query
And the below article is to describe about how to setup the environment.
Add reports to a team project
But, these articles are available under SQL Server Reporting (Legacy) section. I could not understand what does "Legacy" refers here.
Can anyone please suggest me if there is some better way to generate Code Churn Report, or is this the only alternative!
The "Legacy" means the "SQL Server reporting" feature is the old preferred way for reporting.
Now, the new preferred way recommended for reporting is "Analytics service" feature with "Power BI integration", and currently this feature is in "Preview". More details, you can see "Analytics & Power BI integration (Preview)".
And please also reference to "Reporting roadmap for Azure DevOps".
You can choose any one of the two ways to generate reporting in your Azure DevOps Server 2019. This depends on which way you and your company prefer to use.
I want to know that after exporting solution to azure devops repos can we edit the code or add new features to the solution from repo itself by adding few lines of code and also i am able to see only files in XML format.
Actually in power app while editing we have some visualization of things but how can you do it in repos while developing new features. Please suggest if there is an alternative.
Editing the exported files is currently not supported. You must edit from within the designers in the browser. For powerapps (canvas apps) specifically, there is currently not an offline editing story, but if it does become enabled in the future, you'll see it on the blog at: https://powerapps.microsoft.com/en-us/blog
There are ALM tools for importing, exporting , and working with Azure DevOps. See https://powerapps.microsoft.com/en-us/blog/announcing-general-availability-of-microsoft-power-platform-build-tools/
Update: We've just announced new tooling to support this:
https://github.com/microsoft/PowerApps-Language-Tooling
More here: https://powerapps.microsoft.com/en-us/blog/source-code-files-for-canvas-apps/
Is there a way I can export the XML metadata for custom records I have created in a sandbox and create them in another environment?
Yes. NetSuite provides the SuiteCloud Development Framework (SDF) for exactly this purpose. Both the Eclipse and WebStorm official plugins provide SDF functionality, and there is a CLI you can download as well.
Search the Help docs for "SuiteCloud Development Framework" and get started.
Is it possible to automate the publish of dxp file to the server. What I want to achieve is build a command line tool, user navigates to the dxp file and runs a command (let's say publish), this should save the file to the library without opening spotfire client (something similar to running spotfire in Headless mode).
I got to know that Spotfire Automation Services can be of some help in this task, but I have never used the automation services and don't know how to install or find the automation services module. Any help or direction is highly appreciated. Thanks
Automation Services is a licensed framework from TIBCO that lets you automate several tasks including Open or Save analysis to library, replace or remap data sources, run alerts etc.
But if your sole requirement is to publish analysis to library then use the import-library-content on command line, or save it in a batch file and use IronPython to trigger that as using button from the DXP.
See API docs of import-library-content for usage.
you can check Google for Automation Services and see more details on its capabilities, but I'm pretty sure your use case is covered. Spotfire does not offer this feature out of the box (except maybe using the admin command tool, but that'd only be for admins).
your organization will need to buy a license for AS, since it's a separate product in the Spotfire suite. talk to your TIBCO rep or send me a PM.
Yes, you can use Automation Services for this. Automation Services needs to be licensed from TIBCO, but it provides a framework that will allow you to create job.xml files which specify a list of tasks for Automation Services to execute. You can then submit the job file to a web service when you want the tasks to be executed.
We are working on a web application (Javascript + php). We want to start using Team Foundation Server in order to apply application lifecycle management. but we don't know where to start! any good guide or tutorials?
If you are investigating TFS to be used as an ALM tool in your company, you probably want to take a look at the free preview of the service that is available in the cloud. That will allow you to see if this tool will get you what you need. There a lots of tools out there, but first you need to figure out what your problem is and what you are trying to solve. TFS may not be the solution you need, but it is a solution for certain teams.
You'll probably likely be using TFS as an ALM tool for the following:
Source Control. Ensure you have version history on your changes. Note: You can now tap into GIT as your repository, if you don't want to use the TFS source control.
Continuous Integration. You can make your build configurations deploy your files out to your environments, and run unit tests if necessary.
Bug Tracking. Use the built-in work items to track all your bugs.
Requirements Tracking. Use Scrum or Kanban for your project to take advantage of the boards that are available with the service. Work items like 'Stories' or 'Product Backlog Items' will let you track the work your team is delivering.
Burndown. The built-in reports should help you report to your management on progress, though you'll have to see if the TFS ones meet your needs.
Test Cases. Your QA team can write their test cases in TFS to document how to test the requirements. If you have the correct license, you can also tap in Microsoft Test Manager for your QA team to execute and plan their tests.
I would strongly advise doing some research into what ALM means, what it is used for, and why you should be doing it before deciding on a tool. The tool won't fix the problem, it just supports you in whatever you are doing to fix your problem.