How High? For How Long? Using Which Foot? Data Manager


Many tests don’t care exactly what data they are executed against. Our Data Manager uses techniques similar to those used with Execution Behaviors to manage Data Providers that generate test data. This solves with a single stroke the dual problems of eliminating hard-coded test values and enabling common test values to be shared across test cases.

Comments (6)

  1. Is this similar to an O/R Mapping tool concept? I see this as the test data is stored in some fashion, and the tests pass a key to the tool which then retrieves the data for them. Am I on the right track?

    This test series is really cool, I’m enjoying reading it. I’d like to hear more. It would be really neat to try some of this out with an open source test tool to demo examples. 🙂

    -Jonathan

  2. Not that I have much experience with them, but no, this isn’t much luck an O/R data mapper. Data Providers generate test data. A simple String Data Provider might have a hardcoded set of values that it hands out (e.g., TestValue, testvalue, TESTVALUE, tEstvaLue). Many Data Providers are more complex; one might for example generate RTF-encoded text strings.

    A demo app, eh? I’ll see what I can do. <g/>

  3. Your Logical Functional Model lets you write test cases from your user’s point of view, test cases that…

  4. In many of my posts I have alluded to the automation stack my team is building, but I have not provided…

  5. I think my team – much of Microsoft, in fact – is going about testing all wrong.

    My team has a mandate…

  6. In many of my posts I have alluded to the automation stack my team is building, but I have not provided…