Recent Changes

Friday, September 15

  1. page How to get started edited ... Test Manager If you are in doubt what to select, chose the role in which you think you are mo…
    ...
    Test Manager
    If you are in doubt what to select, chose the role in which you think you are more firm
    Back
    (view changes)
    1:53 am
  2. 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:
    ...
    PREVIOUS TEST AUTOMATION.AUTOMATION or, if you want to improve yourself see how to get started.
    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
    ...
    your test automation.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)
    1:52 am
  3. page Test Manager edited ... provide the resources, people, machines and tools (DEDICATED RESOURCES, DEPUTY, RIGHT TOOLS, P…
    ...
    provide the resources, people, machines and tools (DEDICATED RESOURCES, DEPUTY, RIGHT TOOLS, PLAN SUPPORT ACTIVITIES)
    planning development and maintainance of test automation (SHORT ITERATIONS, WHOLE TEAM APPROACH, MAINTAIN THE TESTWARE, REFACTOR THE TESTWARE)
    having the automated tests executed, eventually selecting an appropriate subset to run (UNATTENDED TEST EXECUTION, PRIORITIZE TESTS, TEST SELECTOR)
    recruiting and training test automators (AUTOMATION ROLES, GET TRAINING)
    ...
    INFORMATION, CELEBRATE SUCCESS)SUCCESS, SELL THE BENEFITS)
    Back
    (view changes)
    1:47 am

Thursday, September 14

  1. page Test Manager edited ... defining standards and processes developing the specific test plans and having them performed…
    ...
    defining standards and processes
    developing the specific test plans and having them performed
    ...
    the test status:
    - how
    status (how many tests have been executed
    -
    executed? how many
    ...
    (and how serious)
    -
    serious)? how many
    ...
    corrected (or not)
    -
    not)? how much
    ...
    resources are needed
    - etc.
    needed? etc.)
    helping decide if the application is ready for release
    recruiting and training testers
    (view changes)
    7:29 am
  2. page Test Manager edited ... between managing application development testing and test automation development Managem…
    ...
    between managing application developmenttesting and test automation development
    Management in application development

    A test manager
    is different depending whether the application is internal or external:
    Internal applications are developed in order to run in house (think of an accounting system or an online shopping site) so management has to
    responsible for:
    the master test
    plan
    defining standards
    and control not only development but also deploymentprocesses
    developing the specific test plans
    and operation
    External applications are developed for customers that use
    having them in their own environmentperformed
    giving information about the test status:
    - how many tests have been executed
    - how many bugs have been found (and how serious)
    - how many have been corrected (or not)
    - how much time
    and under their own control so management has only to plan and control development
    Test Automation
    resources are needed
    - etc.
    helping decide if the application
    is an internal applicationready for which similar management tasks apply as for other internal applications.
    Still there are important differences:
    Internal development applications:
    have but one goal: support their users. There may be changes later, but they are usually made
    release
    recruiting and training testers
    A test manager
    in order to enhance that support (eliminate errors, add or improve features)charge of test automation is also responsible for:
    defining the scope of test automation (SET CLEAR GOALS, DO A PILOT)
    defining standards
    and are thus not very frequent
    Logs and reports are mainly
    processes for operating
    Test automation:
    has always two goals: support testing and follow up on changes in
    test automation (SET STANDARDS, GOOD DEVELOPMENT PROCESS)
    defining
    the System under Test (SUT) Changes are actually the norm
    Logs
    strategy for test automation (TESTWARE ARCHITECTURE, ABSTRACTION LEVELS, MAINTAINABLE TESTWARE)
    deciding what to automate
    and reports are writtenwhat not only for(AUTOMATE WHAT'S NEEDED, KNOW WHEN TO STOP)
    provide
    the 'users' (testersresources, people, machines and tools (DEDICATED RESOURCES, DEPUTY, RIGHT TOOLS, PLAN SUPPORT ACTIVITIES)
    planning development and maintainance of
    test managers), but also to enableautomation (SHORT ITERATIONS, WHOLE TEAM APPROACH, MAINTAIN THE TESTWARE, REFACTOR THE TESTWARE)
    recruiting and training
    test automators to find(AUTOMATION ROLES, GET TRAINING)
    getting MANAGEMENT SUPPORT for test
    automation bugsby communicating with management, testers and more important still to enable developers to find SUT-bugsdevelopment (SHARE INFORMATION, CELEBRATE SUCCESS)
    Back
    (view changes)
    7:27 am
  3. page How to get started edited ... common 'Newbie-Problems'! What has been your role up to this point? Tester Developer …
    ...
    common 'Newbie-Problems'!
    What has been your role up to this point?
    Tester
    Developer
    ManagerTest Manager
    If you are in doubt what to select, chose the role in which you think you are more firm
    (view changes)
    5:53 am
  4. page Tester edited ... be performed on specific dates (testers can set and reset the date if needed) Automated tests…
    ...
    be performed on specific dates (testers can set and reset the date if needed)
    Automated tests should:
    be modular. This means that actions that are performed in many test cases are written each in a specific script that can be called when needed. In this way changes affect only one script and not the whole testware (see GOOD PROGRAMMING PRACTICES, KEYWORD-DRIVEN TESTING, SINGLE PAGE SCRIPTS)
    be written as INDEPENDENT TEST CASES so that they don't have to be executed together every time. See also PRIORITIZE TESTS, FRESH SETUP and TEST SELECTOR.
    FAIL GRACEFULLY so that the next test cases can execute normally
    ...
    be able to perform date sensitive test cases (look up DATE INDEPENDENCE)
    be written in such a way that changing the testing tool doesn't mean starting again from scratch. The patterns to look up in this case are TOOL INDEPENDENCE and OBJECT MAP
    be maintainablemaintainable. For instance writing modular scripts . This means that actions that are performed in many test cases are written each in a specific script that can be called when needed. In this way changes affect only one script and not the whole testware (see GOOD PROGRAMMING PRACTICES, KEYWORD-DRIVEN TESTING, SINGLE PAGE SCRIPTS). Other important patterns are MAINTAINABLE TESTWARE, DESIGN FOR REUSE,REUSE and ABSTRACTION LEVELS)LEVELS
    Back
    (view changes)
    5:52 am

Wednesday, September 13

Monday, September 11

  1. page Developer edited ... when developing test automation one should: always remember that there is no 'user', only the…
    ...
    when developing test automation one should:
    always remember that there is no 'user', only the tool and it is inherently stupid! See UNATTENDED TEST EXECUTION
    foresee anyplan for possible eventincidents because otherwise
    ...
    doesn't react (UNEXPECTED EVENTS)(EXPECT INCIDENTS)
    remember that the automated tests not only drive but also react to the System under Test (SUT). If the SUT takes different times to execute the same action (depending on the data, the database, the network etc.) the automated test must be able to wait a longer or shorter time (VARIABLE DELAYS)
    make sure that tests can be executed at any time and on any machine and eventually in parallel (INDEPENDENT TEST CASES, DEDICATED RESOURCES, PRIORITIZE TESTS, PARALLELIZE TESTS)
    (view changes)
    6:38 am
  2. page Test Manager edited The most important thing to learn about test automation is the difference between managing applicat…
    The most important thing to learn about test automation is the difference between managing application development and test automation development
    Management in application development is different depending whether the application is internal or external:
    ...
    deployment and executionoperation
    External applications are developed for customers that use them in their own environment and under their own control so management has only to plan and control development
    Test Automation is an internal application for which similar management tasks apply as for other internal applications.
    ...
    are important differences.differences:
    Internal development applications:
    have but one goal: support their users. There may be changes later, but they are usually made in order to enhance that support (eliminate errors, add or improve features) and are thus not very frequent
    Logs and reports are mainly for operating

    Test automation:
    has always two goals: support testing and follow up on changes in the System under Test (SUT) Changes are actually the norm
    Logs and reports are written not only for the 'users' (testers and test managers), but also to enable test automators to find automation bugs and more important still to enable developers to find SUT-bugs

    Back
    (view changes)
    6:31 am

More