visual studio testing capabilities - visual-studio

I am looking to find out the testing tool capabilities that are offered with Visual Studio. From my research, I understand that you offer both functional and load testing tools for both web and Windows-based applications. I read the ‘coded UI Tests’ feature automates UI testing. My questions is, does this feature only work on .NET-based applications or can I use it to do UI testing on an application that was written in PowerBuilder?

You can find here the configurations that are supported by coded UI.
PowerBuilder is not in the list but depending on the technology it relies on (MFC?) it might work.
You can download a trial version of VS and try it on a PB application.

Related

devops workflow for C# windows desktop based apps

What are the steps to implement DevOPs for a C# windows desktop based application.
What are the tools should be used to automate the manual process like testing, code review, code analysis, performance, build & release, deployment and change requests deployment
That is a very general question. It relies on specific needs, budget considerations, technologies, company size, and more.
You can try all sort of free offering out there, just to experiment. Since you're working on Windows with C#, so you're already have strong connection to Microsoft, I would say check out Visual Studio Team Services, it's a cloud-based ALM/DevOps tool, free for up to 5-users team.

UFT not recognizing controls in Microsoft Management Console App

I am evaluating UFT (formerly QTP) as an automation tool for testing a Microsoft Management Console app. The controls have the prefix MMC, e.g. MMCMainWindow.
I have contacted HP and so far they have not come up with a solution. The solutions architect I am working with suggested using the extensibility toolkit, but I'm not sure that was meant for creating custom controls for an entire application.
Any suggestions would be greatly appreciated.

Justifying Visual Studio upgrade for REST API project

Our group does not primarily develop in c#/.NET, but a few years ago we picked up a couple of licenses for Visual Studio 2008 for a few projects. Since we do not develop full time in .NET, we have not upgraded Visual Studio since then.
There is a project coming where we need to develop a web application that contains a REST API. We have been looking at all of the documentation that deals with creating REST APIs. It appears that while VS 2008 is capable of creating APIs (with WCF), later versions of Visual Studio seem to have much better support for creating REST APIs (ASP.Net Web API).
My questions are:
Would upgrading to Visual Studio 2012 or 2013 make that much of a difference in the development/maintenance of an API, or is Visual Studio 2008 sufficient?
How can we go about justifying an upgrade in our Visual Studio licenses (if needed)?
We don't want to justify an upgrade by just saying "it is newer so it is better". Are there any documents that show how Visual Studio 2012 or 2013 is much better at creating REST APIs than Visual Studio 2008?
Not sure if is enough to justify the money but here are some reasons to adopt Visual Studio 2013:
With Visual Studio 2008 you are restricted to .NET Framework 3.5 or lower. If you upgrade you have access to 4.0, 4.5 and future 5.0
If you use Framework 4.5 you can use new REST API Framework.
You can use latest versions of MVC.
You can use latest Microsoft Entity Framework versions (old version can be used in Framework 3.5.1 but you really want the latest version as it has important performance improvement)
You can benefit from ASP.NET WebAPI.
WCF was a way of improving web services, but not the best one. I would avoid WCF if possible.
What is Web API?
ASP.NET Web API is a framework for building web APIs on top of the .NET Framework. You can use the new MVC4 (ASP.NET MVC 4 Web Application project)
using Web API template.
You can actually get Visual Studio 2013 express for free and build all the web API's you'd like. The paid versions include lots of enterprise features and plugin support.
http://www.visualstudio.com/en-us/products/visual-studio-express-vs.aspx
For me, it will always be a factor of the business side of things. If they see the value, it is an easy sell.
If using Framework 4.5.1 (VS2013 required) will reduce both the server resources
(See:
ASP.NET application suspend
Just-In-Time (JIT) performance of 15%
"The .NET Framework 4.5 and Windows 8 introduce features that can help you achieve a significant performance boost for web-server workloads. This includes a reduction (up to 35%) in both startup time and in the memory footprint of web hosting sites that use ASP.NET."
)
AND bandwidth resources
(SEE:
.NET 4.5 and WCF Request Compression
http://www.topwcftutorials.net/2014/03/whats-new-in-wcf-v45.html under Compress and Cache
),
then one can actually do the maths and see if it makes sense already. Then, the developer and maintenance side (which is quite "neat" in Vs2013 - new intellisense, nice nuget, etc.), is just jam. From a developer point of view, you will also need to consider the cost to upgrade the application between versions, i.e. the cost from 2008 to vNext vs. 2013 to vNext.
Update:
As this is a very similar situation I find myself in, I have been doing some research. Our company standards is VS2012 (RE: Microsoft Dynamics environment).
According to "What's New in the .NET Framework 4.5, 4.5.1, and 4.5.2" at http://msdn.microsoft.com/en-us/library/ms171868(v=vs.110).aspx they suggest the following for your domain specific improvements:
•Ability to support multiple authentication modes on a single WCF endpoint when using the HTTP transport and transport security.
This is always a big seller for business. Please look at the other improvements under WCF at the link above.
I have also found an article at http://www.msmsoftware.com/2013/8/6/the-business-benefits-of-upgrading-net-35-to-45.aspx that is very specifically aimed at your question. They note, as I said, better performance, better security and increase development and support functions.
Your question is unique in that it targets the work side of things (WCF), so the fluff around better support for app stores, better web standards, etc. is somewhat pointless. Hopefully I have given you enough to make the answer somewhat clear.

How to test web apps on multiple browsers with Coded UI Test (CUIT)?

I wonder how to test web apps on multiple version of browsers with coded UI tests? Such as IE 7-9, Firefox 9-11, and latest Chrome.
My first thought was that I'll install those browsers on my development box or build server. But that really doesn't sound right even if it's technically possible.
I probably need some pointers on how to approach testing web apps on multiple browsers and multiple versions.
Visual Studio 2010
TFS 2008
OK, First see the Coded UI supported platforms as the following,
Second, for creating matrix test for the supported platforms, just see the following post,
Configuration matrix testing using Visual Studio Lab Management

Easy Language/IDE to Develop GUI Program?

I'm planning on developing an Windows desktop-based GUI application, and I don't have a clue which language or IDE to choose. I'd REALLY like something with a WYSIWYG GUI editor. My application will rely on web-based XML feeds, so built in support for that would be great. I don't want the application to have any dependencies or require admin rights to run. Cross-platform is nice, not not required.
I'm willing to learn a new language if that's necessary.
Delphi is well reputed for Windows GUI application developpment. It's even a 'RAD' Studio (rapid application development studio) as they call it.
Check out Delphi. Alternatively FreePascal with its Lazarus IDE is pretty much an open-source Delphi clone, which while not as polished, offers cross-platform support.
For Windows, I will definitely go for C#.
If you know c++ and have MFC experiences, it should be fairly easy to learn.
Yes, it has WYSIWYG GUI editor.
Designing a User Interface (Visual C#)
http://msdn.microsoft.com/en-us/library/ms173080(v=vs.80).aspx
and it seems this is what you are looking for?
SyndicationFeed Class
http://msdn.microsoft.com/en-us/library/system.servicemodel.syndication.syndicationfeed.aspx
Good Luck!
There are several variants.
Windows only
C# + MSVS:
One of the best choices on Windows platform today
+good documentation
+big developers community
-you need a system which has .net installed.
Delphi
+easy to start
all-in-one tool with GUI editor
not very widespread
Cross-platfrom
Qt or wxWidgets or some other toolsets
If you're looking for a free solution, you can use SharpDevelop, which is a free IDE for C# or VB.NET, and has a GUI designer similar to the one in Visual Studio. You should be able to use any classes and libraries from/for the .NET Framework.
You'll need the .NET Framework, but starting with Windows Vista it's installed by default (.NET Framework 3.0, I think).

Resources