Working With Visual Studio: Developers and Functional Testing

Developers working on functional testing don’t have to be focused solely on coding tasks. They should also able to work with any of the tasks around creating, editing, and maintaining automated UI testing. Test Studio’s plugin gives developers (and coding testers!) the ability to work seamlessly with functional tests directly within Visual Studio.

Working inside Visual Studio leaves team members with complete access to the critical features that make Test Studio Standalone so useful:

• Recorder: Record and update tests. Use the DOM explorer to craft custom find logic to ensure your tests make the best use of locators specific to your particular application and UI.

• Debugger: Debug both code via Visual Studio and recorded steps via Test Studio’s Visual Debugger straight from within your Visual Studio environment.

• Element repository: The element repository is one of the most powerful features of Test Studio. Within Visual Studio you’ve got full access to this centralized storage for all your element find logic/locators. Elements are easily updated with the same Edit Find Logic dialogs you get within the Standalone version.

• Cross browser compatibility: As a developer or coding tester you’re not limited to one browser. The Visual Studio plugin for Test Studio enables you to work with all our supported browsers: Firefox, Safari, Chrome, and Internet Explorer.

Developers Can (and Should!) Write Automation Too

I'm a huge proponent of whole team testing, and I firmly believe teams adopting this approach will see tremendous successes over those that don't. Developers (or coding testers) working with Test Studio's plugin for Visual Studio can help create and maintain great automation suites without leaving their regular working environment. You've got access to all the great tools that make Test Studio so terrific right in the same place you're doing all your coding-fu!

More blog posts on the topic of Developer Testing: Working with Visual Studio: Write Code Where Needed & Working in a Familiar Environment.

About the author

Jim Holmes

Jim Holmes is the Director of Engineering for Test Studio. He has around 25 years IT experience. He's a blogger and the co-author of "Windows Developer Power Tools" and Chief Cat Herder of the CodeMash Conference. Find him as @aJimHolmes on Twitter.

CodeProject