I’m frequently asked what applications we test internally with Symantec Workspace Virtualization (SWV), what are the pitfalls for each application, and if I can make that information available here on Connect. Well I’ve always shared what information I know from capturing applications here on Connect as I learn it via my various articles and blog posts but I’ve never really taken the time to share what applications we consistently test and provide an easy way to find the content I’ve got up here if you just want to see what information is available—as opposed to just running a search for a specific application.
First up let me cover a little about what we test. There are two levels of application compatibility tests that I run with SWV, Streaming is very similar but they tend to test older versions in addition to newer ones of apps while I only test newer apps, and that’s SMOKE and ACCEPTENCE level tests. The tests for each application involve at least capturing and launching the application as well as, if viable, opening and saving files. If the application is COM automatable then we generally have automation tests that check the behavior of more features of the application to make sure that, when virtualized, there’s no loss of functionality.
The SMOKE test suite contains applications as determined by Project Management based off of what we know our customers are virtualization, such as Office, and we run these tests very frequently—sometimes once a week—to make sure there are no issues with these important applications. This list is very static and only changes when PM decides it’s time to add or remove stuff—though I do version apps as new ones become available.
The current list of SMOKE apps are:
- Microsoft Office (2003, 2007 and 2010)
- Microsoft Visio (2007, 2010)
- Acrobat Reader
- Acrobat Pro
- Internet Explorer
- Open Office
The ACCEPTENCE level tests are much broader, as I choose what to add and I want to make sure we have a variety of functionality—such as services and media—covered by our tests. This list is usually generated by things brought up here on Connect (I’ve even asked for peoples input on the forums before), had issues with before or things I just want to try out to see how they behave when virtualized. In contrast to the SMOKE level applications these tests are only run a handful of times a year or used for other test validations.
I’m not going to list everything but it includes some of the following apps:
- Google Desktop
- Many Adobe applications
- Brower plug-ins such as Flash
As I stated at the beginning of this post when I find an issue I put it up here on connect but it can be really scatter shot trying to find all the content for one specific application. So, for applications with multiple sources of information or only a single blog post, I’m going to create a blog post with the key word SWV Application Database that can be searched and sorted against here on connect.
I also invite others to do the same. If you’ve got information on an application, meaning there’s something that has to be done to get it to behave correctly outside of normal capture, please post it as a blog post unless it’s really involved then create an article (if it meets the qualifications for an article you should get the extra points for it right?) and then a blog post linking to your article, the SWV Application Database key word and a short summery of the article so people can easily sort through the content.