Recent Changes

Sunday, June 17

  1. page Diagnostic edited ... Note: we are talking about automating system level tests, not unit-tests. Here are some quest…
    ...
    Note: we are talking about automating system level tests, not unit-tests.
    Here are some questions to get you started looking for the issues you may be encountering:
    Are you satisfied with your current automation? Did you try automation and it didn't work and is now abandoned, or it just isn't giving you the benefits you had wanted and expected? In this case you now want to improve or revive your test Automation.
    Are you just starting with automation and have never done it before? Look at the issue NO PREVIOUS TEST AUTOMATION.
    Are you are joining a test automation team and have no experience in test automation? Look at the issue LIMITED EXPERIENCE for suggestions on how to catch up fast.
    Are you completely happy with your automation at this time? Then please share your knowledge with other Wiki users. You don't have to read further ;-).
    Do you already know what your specific issues are? If so, you can go straight to the relevant issue(s) from the list of Test Automation Issues.
    At this point, we presume that you are not satisfied with your current automation. Perhaps you tried automation and it didn't work and is now abandoned, or it just isn't giving you the benefits you had wanted and expected. So now you want to
    improve or revive your test Automation.

    Tips:
    If the first option you try doesn't seem to fit your situation, come back to this page and try another.
    (view changes)
    10:14 am

Friday, June 15

Monday, June 11

Tuesday, June 5

  1. page Acknowledgements edited ... this wiki: Lars Nordin for comments on several patterns, thanks. (CAPTURE REPLAY, OBJECT…
    ...
    this wiki:
    Lars Nordin for comments on several patterns, thanks. (CAPTURE REPLAY, OBJECT MAP and INTERDEPENDENT TEST CASES)

    James Tony for a lot of useful ideas for different patterns or issues
    Freddy Vega for adding his experience to the pattern OBJECT MAP
    (view changes)
    1:40 am

Monday, June 4

  1. page Lack of direction edited ... More reasons for lack of direction: Management doesn't support automation so it is done under…
    ...
    More reasons for lack of direction:
    Management doesn't support automation so it is done underhand by a lonely crusader. INADEQUATE SUPPORT is the issue to look up in this case
    ...
    case of SORCERER'S APPRENTICE SYNDROME"Sorcerer's Apprentice Syndrome" or MANUAL MIMICRY. If your tests are linked together, with each test depending on the result of the previous test, then see the issue INTERDEPENDENT TEST CASES.
    Testers doing automation don't know how to do it well. The issue LIMITED EXPERIENCE can help you solve this kind of problem
    Tool use or testware architecture is different from team to team. Look up the issue LOCALISED REGIMES
    (view changes)
    4:39 am

Tuesday, May 29

  1. page INTERDEPENDENT TEST CASES edited ... Design Examples ... fixed sequence and preceding test cases must succeed because the Q…
    ...
    Design
    Examples
    ...
    fixed sequence and preceding test cases must succeed because the
    Questions
    Who designed the test cases, and for what purpose? Are manual test cases being automated "as is"?
    (view changes)
    10:46 am
  2. page OBJECT MAP edited ... Description Declare all the GUI-Objects in the Object Map of the tool (note: this may also be…
    ...
    Description
    Declare all the GUI-Objects in the Object Map of the tool (note: this may also be called a GUI map or Object Repository). You can then write your scripts using standardized names. The scripts will be more readable and if you have to migrate to another tool you will not need to change the scripts to allow for new names even if tools seem never to use compatible naming conventions.
    Note, this concept can also be applied to non-GUI testing - that there are test lib objects use to interact (or control) parts of the system under test.
    Implementation
    This is one way to implement TOOL INDEPENDENCE, as your tests will be one layer removed from the specific names in the software.
    (view changes)
    10:44 am
  3. page CAPTURE-REPLAY edited ... With a so called capture-replay tool you can record a test in the script language of the tool …
    ...
    With a so called capture-replay tool you can record a test in the script language of the tool while you perform it manually. By running the script you can let the tool perform the test automatically
    Possible problems
    ...
    for instance set-ups.set-ups but some consider this to be an anti-pattern due to how brittle it is.
    If you capture a test not only as a script but also as video clip you can get the information you need to automate it even if testers have no time to support you.
    Beware: If you want your automation scripts to be easily maintainable, you should avoid creating them solely using capture-replay: every small change in the SUT can force you to record the test again and you will get BRITTLE SCRIPTS or TOOL-DRIVEN AUTOMATION
    (view changes)
    9:57 am

Tuesday, May 8

Sunday, May 6

More