• .NET Testing & ALM

    Working With Visual Studio: A Familiar Environment

    As I mentioned in my last post's closing, Test Studio's plugin for Visual Studio lets developers and coding testers work right in an environment they’re familiar and comfortable with. You’ve undoubtedly customized Visual Studio to fit your particular needs: display settings, window behavior and layout, and any number of other plugins and productivity tools such as Telerik’s JustCode. Working with Test Studio inside of Visual Studio leaves you the ability to pull in other tools easily through NuGet. Do you prefer using NUnit or MbUnit for their powerful Assert and fluent interfaces? Go right ahead! (Note that you can also ...
    April 08, 2013
  • .NET Testing & ALM

    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 ...
    April 05, 2013
  • .NET Testing & ALM

    Working with Visual Studio: Write Code Where Needed - Part 2

    In the first part of this blog post we covered some common scenarios for setup and configuration of your tests to ensure the overall test suite maintainable over the long run. Now, we’ll talk about backing APIs, extended tests, and test oracles. Backing APIs As powerful as Test Studio is, every project will end up needing some form of coded infrastructure at some point. Backing APIs make it much easier to handle the setup and configuration tasks mentioned above. You could work with Test Studio Standalone and use an empty coded step in an empty test as ...
    April 04, 2013
  • .NET Testing & ALM

    Configuring Firefox for Fiddler

    Mozilla Firefox is unlike most Windows browsers in that it does not use the system’s proxy and certificate settings by default. That means that Firefox may require some additional configuration to work properly with Fiddler.To get Firefox running with Fiddler, you need to:Configure Firefox to proxy its traffic to Fiddler.Configure Firefox to trust Fiddler’s root certificate.Fortunately, both of these are simple tasks.Configuring the ProxyFirefox’s proxy settings are found by opening its Tools menu, clicking the Options item, and opening the Advanced settings. Select the Network tab. At the top of the tab, click the ...
  • .NET Testing & ALM

    Working with Visual Studio: Write Code Where Needed - Part 1

    Every test automation project will require some level of coding to be successful. Test Studio’s record and playback creates powerful, maintainable tests, but you’ll still need to write code at some point to cover common, critical aspects such as configuration, backing APIs, or test oracles. Setup and Teardown/Configuration Complex tests require clear, flexible configuration actions that keep the overall test suite maintainable over the long run. Pushing setup, teardown, and configuration to code versus the system’s interface dramatically speeds up test execution by leveraging the system’s own internal functionality through internal APIs, web service endpoints, or database stored procedures. Here are some common ...
    April 01, 2013