Telerik blogs

Productivity: Testing

Sitefinity Automation with Test Studio (Why the Magic Happens)

by Petar Grigorov September 20, 2023

Latest

For the latest product updates, please visit Release.

  • 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

    KickStart Your .NET Mocking

    Getting started with mocking can be hard. In this article, I describe the path that I took on my way to becoming a frequent mocker.
    Japikse by Phil Japikse
    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 Testing

    Asserting Behavior with JustMock

    JustMock is a great tool for abstracting dependencies in unit tests, and the new automocking feature makes it even faster to develop unit tests.  Another great feature in JustMock and JustMock Lite is the capability to assert the behavior of your system under test.  Traditional TDD (Test Driven Testing) unit testing typically tests for state.  Did the user get logged in? Did the user’s shopping cart get loaded?  Important tests, of course.  But that only tests the end result of the method.  If the user does NOT successfully login, and the cart is not reloaded, is that because the call to the repository was never called? Or because some error happened that didn’t reload the cart in this particular use case?  The state of the application is correct, but is that because it executed the expected behavior, or because we got lucky? 
    Japikse by Phil Japikse
    January 10, 2013
Prev
... 81 82 83 84 85 86 87 88 89 90 ...
Next