Recent Changes

Tuesday, May 8

Sunday, May 6

Tuesday, May 1

  1. page home edited ... Welcome to the Test Automation Experiences WikiTest Automation Patterns Wiki Important noti…
    ...
    Welcome to the
    Test Automation Experiences WikiTest Automation Patterns Wiki
    Important notice: Wikispaces will close this year. This wiki will be online here until September 2018. At some point before that, there will be a new host for this wiki. As soon as we have more information we will post it here. The link TestAutomationPatterns.org will continue to work.
    How to get started:
    If you are new to the wiki the best way to get started is using the Diagnostic. The diagnostic asks you questions about where you are now in your automation to lead you to the issue(s)/problem(s) that are most relevant for you, and then to the patterns that will help you.
    ...
    When you have looked around the wiki, please visit our Comments and Discussion about the patterns page and leave a comment! Recent Changes are described here.
    This wiki
    Important notice: Wikispaces will close this year (September 2018). At some point before that, there will be a new host for this wiki. As soon as we have more information we will post it here. The link TestAutomationPatterns.org should continue to work.
    This wiki is available to view publicly (read-only). If you would like to add or edit pages (e.g. to add your experiences), please ask to join the wiki, and we will approve your request, and keep you as a member for a minimum of 3 months. Access is currently free. We reserve the right to remove any member if needed. We may withdraw the invitation of those who haven't taken it up within a month. Full membership is reserved for contributors only. If after three months you haven't contributed with experiences, corrections or enhancements to patterns or issues you may be removed. Of course you will still be able to use the wiki (read only), and can ask to join again if you wish.
    We are keen to get feedback from you - please feel free to make edits to pages - particularly if you can add a short example experience of using a pattern! Before making any major changes or additions, please email us, thanks.
    (view changes)
    4:55 am
  2. page home edited ... Welcome to the Test Automation Experiences WikiTest Automation Patterns Wiki ... be online…
    ...
    Welcome to the
    Test Automation Experiences WikiTest Automation Patterns Wiki
    ...
    be online here until September 2018. We are lookingAt some point before that, there will be a new host for solutions in order to enable further use of thethis wiki. As
    ...
    post it here here. The link TestAutomationPatterns.org will continue to work.
    How to get started:
    If you are new to the wiki the best way to get started is using the Diagnostic. The diagnostic asks you questions about where you are now in your automation to lead you to the issue(s)/problem(s) that are most relevant for you, and then to the patterns that will help you.
    (view changes)
    4:53 am

Monday, April 30

  1. page Improve or revive test automation edited ... Lack of specific knowledge (how to test the Software Under Test (SUT), use a tool, write maint…
    ...
    Lack of specific knowledge (how to test the Software Under Test (SUT), use a tool, write maintainable automation etc.)
    Management expectations for automation not met (Return On Investment (ROI), behind schedule etc.)
    ...
    run unattended, etc.))etc.)
    Maintenance expectations not met (undocumented data or scripts, no revision control etc.)
    Return to Diagnostic
    (view changes)
    12:02 pm

Monday, April 16

Wednesday, April 4

Tuesday, April 3

Friday, March 23

Thursday, March 1

  1. page home edited ... Welcome to the Test Automation Experiences WikiTest Automation Patterns Wiki ... until Sep…
    ...
    Welcome to the
    Test Automation Experiences WikiTest Automation Patterns Wiki
    ...
    until September 18.2018. We are
    How to get started:
    If you are new to the wiki the best way to get started is using the Diagnostic. The diagnostic asks you questions about where you are now in your automation to lead you to the issue(s)/problem(s) that are most relevant for you, and then to the patterns that will help you.
    (view changes)
    9:01 am

More