Recent Changes

Sunday, June 25

Monday, June 19

  1. page INEFFICIENT EXECUTION edited ... Resolving Patterns Most recommended: INDEPENDENT TEST CASES: This pattern is useful if you …
    ...
    Resolving Patterns
    Most recommended:
    INDEPENDENT TEST CASES: This pattern is useful if you canPARALLELIZE TESTS - split the
    ...
    in parallel on(on different machines.machines), which requires INDEPENDENT TEST CASES.
    STEEL THREAD: Use this pattern to help define a minimal set of tests to be run.
    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.
    (view changes)
    8:12 am
  2. page INDEPENDENT TEST CASES edited ... A self contained test does NOT mean that just one test case tests the whole application! On th…
    ...
    A self contained test does NOT mean that just one test case tests the whole application! On the contrary each test should have ONE CLEAR PURPOSE derived from one business rule.
    If you PRIORITISE TESTS, you will also be able to run or rerun the tests independently from each other.
    This allows for PARALLELIZE TESTS
    Possible problems
    Manual tests are often performed sequentially in order to spare set-up time. They should be redesigned before automating to make sure that the automation is as efficient as possible.
    ...
    too much time,time and there is no other option, then this
    Issues addressed by this pattern
    FALSE FAIL
    (view changes)
    6:34 am
  3. page PARALLELIZE TESTS edited ... Instead of running all your tests sequentially, you break them up in different batches that ca…
    ...
    Instead of running all your tests sequentially, you break them up in different batches that can run concurrently on different machines
    Implementation
    AThe first step is to write the tests as INDEPENDENT TEST CASES. Another good way
    Potential problems
    ...
    same tests onin parallel!
    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:29 am

Thursday, June 15

Wednesday, June 7

  1. 2:05 am

Monday, June 5

  1. page Recent Changes edited Just a brief note about changes made. Feel free to comment on anything you see here. March June …
    Just a brief note about changes made. Feel free to comment on anything you see here.
    MarchJune 2017: Changed the Process Issue RANDOM AUTOMATION to UNFOCUSED AUTOMATION
    March
    2017: Removed
    ...
    home page.
    August 2016: Seretta and Dot have decided to eventually eliminate the General Issues. They will stay for the time being, but we have been working on improving the Diagnostic so that it covers everything that is in General Issues but independently. We are also breaking up some of the longer questions and issues to make them easier to use. Please let us know any comments or reactions you have - thanks!
    March 2016: Added new Execution Pattern EXPECTED FAIL STATUS and new Design Pattern COMPARISON DESIGN
    (view changes)
    3:50 am

More