Telerik blogs

Tag: Automation

  • Productivity Debugging Release

    Announcing Fiddler 2.4.3 Beta

    Yesterday, an updated Fiddler Beta was released, targeting .NET2 or .NET4. This update contains the usual set of bug fixes as well as a number of small features that I hope you’ll find useful. Column Customization Fiddler has always permitted you to customize the set of displayed columns to show information you’re interested in directly inside the Web Sessions list. However, adding new columns isn’t as easy as it could be, and this Beta includes the first steps toward simplifying this process. Simply right-click on the column headers and choose Customize columns… A simple popup will open to allow you ...
    February 08, 2013
  • Productivity Testing

    Creating Test Case Documentation via Test Studio’s Storyboards

    How much time to you spend documenting your test cases? Most of the time it’s “too much!” Test Studio’s Storyboard export feature can get you a great start on documentation with the click of a button. Test Studio captures storyboards as you record your test, giving you a visual walkthrough of what your test is doing in a series of frames, one per test step. Each frame shows the exact state of the UI after that step is completed: Navigation, coded steps, and other non-visual steps are represented with a plain frame and a generic description of the action: Storyboards ...
    February 04, 2013
  • Productivity Testing

    Using Data Driving Wisely

    [Update: Added links for Hexawise and Allpairs, which I’d meant to do earlier.] Data driving, also often called parameterization, is a wonderful way to increase your test coverage though parts of your system; however, it’s also a seductive, alluring tool that can needlessly explode your tests’ complexity and execution cost. Let’s tackle the cons of data driving first, then walk through how it can, when mindfully used, lend some great value to your automation suites. Problems with Data Driving Automated test scripts need to be treated like production code—because they are production code! With that in mind, as test ...
    January 25, 2013
  • Productivity Testing

    Data Driven Testing: What’s a Good Dataset Size?

    I thought I’d follow up that last post on Using Data Driven Testing Wisely with something specific around the size of the dataset for a data driven test (DDT). What’s a good size for a DDT? As with everything in software engineering/testing, the answer is “42.” That, or “It depends.” In all seriousness, the right size of a dataset for a carefully thought out scenario does indeed depend. My payroll algorithm in the last post was a simple test set. You may be working something much more complex relating to finance, rocket science, or environmental controls. Every situation’s different, but ...
    January 25, 2013
  • Productivity

    WaitForVisible Steps That Don't Wait

    Occasionally we get complaints that the WaitForVisible steps in Test Studio don't work correctly. Our response is "It's not our fault!"   Here's what I mean: the Visibility check relies on the Computed Style of the element as seen through the lens of the browser. Specifically we look at the Display property. Here's a video of me using the Google Developer tool to determine the visibility property of an HTML element. Display:none means element is not visible. So it might be that your browser of choice is not very good at determining the visibility factor. Personally I recommend that ...
    January 22, 2013
Prev
... 21 22 23 24 25 26 27 28 29 30 ...
Next