• .NET Testing & ALM

    The "Remove Script File" Button

    This one is kind of advanced. You can add a coded step to your test (or convert  an existing step to code). When you do that - a so-called "code-behind file" is generated. The file in question is simply a C#/VB class file that has the exact same name as your test:   You can open and edit the entire class file from Standalone by using the View Class button: And you'll be able to do anything you would expect from a class file - define custom functions, add assembly references, define global variables etc. In fact, all your coded ...
    September 11, 2012
  • .NET Testing & ALM

    Here we grow again. Telerik acquires Fiddler. What’s next?

    We have some very exciting news to share with the Telerik community.  Telerik has just acquired Fiddler!  Even more exciting is that Fiddler’s brilliant creator Eric Lawrence will come over from Microsoft to join the team fulltime.  For those of you who don’t know, Fiddler is a web debugging proxy which logs all HTTP(S) traffic between your computer or device and the Internet. In other words, it is an essential tool for any web, desktop or mobile developer.  The popularity and sophistication of Fiddler is hugely impressive considering this has been Eric's informal side project for more than 8 years.  With Eric joining the team ...
    September 10, 2012
  • .NET Testing & ALM

    In Nashville Area on 9/21? Join us for Breakfast!

    Are you in the Nashville, TN area the morning of 21 September? Please consider joining me, Phil Japikse, and Burke Holland for a Breakfast at Telerik event! You’ll get a free light breakfast (and coffee!), then be able to sit in on three sessions covering writing great requirements, building solid web UI automation tests, and determining whether or not to chose HTML 5 or Silverlight for your next project. The point of these morning breakfast events is to get in, have a bite to eat (and coffee!), learn something useful, then get out and back to your office in time ...
    September 07, 2012
  • .NET Testing & ALM

    Closing Tabs in Chrome

    Occasionally a customer will want to do something unusual like close a tab in Chrome. I worked on this request today and I found some interesting things. I though it might be nice to share my finding. First off: Test Studio doesn't like tabs - you should always open links in a new window Some browser actually allow you to pick your preference - open links in tabs or new windows. If the option is available - you should always go by "new window" (but Chrome does not have it). A new window is actually a pop up and Test ...
    September 04, 2012
  • .NET Testing & ALM

    Regular VS Simulated Clicks

    Test Studio's clicking and typing steps come in two varieties: regular and simulated clicks. You can flip between the two by going into the Properties menu for the respective step: A regular (non-simulated) click/typing is an action that is injected directly into the DOM of the page. This has advantages - it's faster and more reliable. It will work even if you run the test on a locked desktop. But it's fundamentally different from a real user clicking/typing on a control. And the disadvantage is that it will not trigger any events that are associated with the control in question.  ...
    September 04, 2012