Recent Changes

Wednesday, January 17

  1. page WHOLE TEAM APPROACH edited ... SUT REMAKE TOO EARLY AUTOMATION TOOL-DRIVEN AUTOMATION UNAUTOMATABLE TEST CASES UNFOCUSE…
    ...
    SUT REMAKE
    TOO EARLY AUTOMATION
    TOOL-DRIVEN AUTOMATION
    UNAUTOMATABLE TEST CASES
    UNFOCUSED AUTOMATION
    (view changes)
    5:06 am
  2. page WHOLE TEAM APPROACH edited ... INCONSISTENT DATA LATE TEST CASE DESIGN NO INFO ON CHANGES NO PREVIOUS TEST AUTOMATION S…
    ...
    INCONSISTENT DATA
    LATE TEST CASE DESIGN
    NO INFO ON CHANGES
    NO PREVIOUS TEST AUTOMATION
    SCHEDULE SLIP
    (view changes)
    5:03 am
  3. page MANUAL INTERVENTION edited ... The initial conditions for a test suite have to be set up by hand. In some tests there are wi…
    ...
    The initial conditions for a test suite have to be set up by hand.
    In some tests there are windows or components that could not be automated and have to be driven by hand.
    Execution times vary greatly and thus test execution is stopped and restarted manually
    In order to run a retest all the other tests in the test suite have to be inactivated manually.
    Test automation is started manually.
    Automated verification is only simple so you can't tell if a test has passed or failed without looking at it.
    Reporting of test results requires manual effort.
    ...
    costly and unreliable.unreliable
    Questions
    Does the current test automation tool drive the Software Under Test (SUT) reliably?
    ...
    Resolving Patterns
    Most recommended:
    ...
    1. and 4.5.
    ONE-CLICK RETEST:
    ...
    similar to Example 4.
    VARIABLE DELAYS: use this pattern if you have an issue like
    Example 3.
    The following patterns will help you solve issues like Example 2.
    MIX APPROACHES
    (view changes)
    4:26 am
  4. page VARIABLE DELAYS edited ... HARD-TO-AUTOMATE INEFFICIENT EXECUTION INFLEXIBLE AUTOMATION MANUAL INTERVENTION Experie…
    ...
    HARD-TO-AUTOMATE
    INEFFICIENT EXECUTION
    INFLEXIBLE AUTOMATION
    MANUAL INTERVENTION
    Experiences
    (view changes)
    2:56 am
  5. page INEFFICIENT EXECUTION edited ... TEST SELECTOR: Implement your test cases so that you can turn on various selection criteria fo…
    ...
    TEST SELECTOR: Implement your test cases so that you can turn on various selection criteria for whether or not a given test is included in an execution run.
    EXPECT INCIDENTS: automated scripts should be able to react to unexpected incidents without disrupting execution
    VARIABLE DELAYS: Use this pattern if execution times depend for instance on the state of the nework or on the different lenght of some SUT-processes
    Other useful patterns:
    UNATTENDED TEST EXECUTION: This pattern is what you want to automate your tests for! Use it!
    (view changes)
    2:55 am
  6. page HARD-TO-AUTOMATE edited ... TESTABLE SOFTWARE: use this pattern for issues similar to Examples 1. 2. and 3. THINK OUT-OF-…
    ...
    TESTABLE SOFTWARE: use this pattern for issues similar to Examples 1. 2. and 3.
    THINK OUT-OF-THE-BOX: try to look at the problem from unusual viewpoints
    VARIABLE DELAYS: use this pattern for issues Like Example 4
    Other useful patterns:
    EASY TO DEBUG FAILURES. use this pattern for issues like Example 8.
    (view changes)
    2:52 am
  7. page FLAKY TESTS edited ... TEST THE TESTS: this is really a no-brainer. Use it always VERIFY-ACT-VERIFY: use this patte…
    ...
    TEST THE TESTS: this is really a no-brainer. Use it always
    VERIFY-ACT-VERIFY: use this pattern if you cannot apply FRESH SETUP
    If different execution times are the reason for the 'flakiness' use the pattern VARIABLE DELAYS
    .................................................................................................................Home / Back to Execution Issues / Back to Test Automation Issues
    (view changes)
    2:50 am
  8. page VARIABLE DELAYS edited ... Description When SUT execution is slow it may be necessary to add delays to the automation sc…
    ...
    Description
    When SUT execution is slow it may be necessary to add delays to the automation script. Fixed length delays should be avoided, because in order to account for different test environments, traffic situations and so on you have to use the longest possible pause. New generation tools offer the possibility to wait only until an event happens. The tool will wait the given maximum wait-time only if the event doesn’t occur at all.
    Implementation
    The

    The
    actual implementation depends not only on the
    ...
    you are using. using, but also on how the System under Test (SUT) has been developed. Some suggestions when developing variable delays:
    If the SUT shows when an action has been terminated, check it and delay execution until it switches auf true:
    a window disappears or appears
    a GUI-Component is enabled or disabled
    a database field is updated
    With files, folders or databases there are usually parameters that tell the system to wait until the action is done
    Issues addressed by this pattern
    FLAKY TESTS
    HARD-TO-AUTOMATE
    INEFFICIENT EXECUTION
    INFLEXIBLE AUTOMATION
    MANUAL INTERVENTION

    Experiences
    If you have used this pattern, please add your name and a brief story of how you used this pattern: your context, what you did, and how well it worked - or how it didn't work!
    (view changes)
    2:45 am

Tuesday, January 16

  1. page TESTWARE ARCHITECTURE edited ... It is not necessarily easy to design a good testware architecture, and it does take effort and…
    ...
    It is not necessarily easy to design a good testware architecture, and it does take effort and time. But it is very worthwhile when done well.
    Issues addressed by this pattern
    BRITTLE SCRIPTS
    INFLEXIBLE AUTOMATION
    CAN'T FIND WHAT I WANT
    (view changes)
    6:12 am
  2. page TESTWARE ARCHITECTURE edited ... CAN'T FIND WHAT I WANT TOO EARLY AUTOMATION TOOL-DRIVEN AUTOMATION Experiences If you ha…
    ...
    CAN'T FIND WHAT I WANT
    TOO EARLY AUTOMATION
    TOOL-DRIVEN AUTOMATION
    Experiences
    If you have used this pattern, please add your name and a brief story of how you used this pattern: your context, what you did, and how well it worked - or how it didn't work!
    (view changes)
    6:09 am

More