Please enable JavaScript.

Coggle requires JavaScript to display documents.

Conference - Coggle Diagram

- - - - • Not suitable for long execution time.
      - • Critical defects can be missed.
      - • Tests invented and performed on the fly can't be reviewed in advance.
      - • Hard to produce status report and metrics.
      - • No Visibility on the execution progress.
      - • It is very difficult to reproduce the problem as you do not follow specific steps.
      - • Determine the critical and high priority test cases to execute can be difficult.
      - Don't know when to stop the testing.
      - • Documentation of all events during execution is difficult to record if you do not have tools.
      - • Inexperienced testers would not be effective.
- - - - • Enforces good design and
        testability from a start
      - • Much better cooperation between Devs and AQA's, any minor issues which may prevent or complicate automation will be fixed immediately
      - • Much more confidence in newly released features, as they are considered done only when fully covered by automation
      - • No wasted time in trying to understand old manual test cases, which may not be properly written for automation
      - • Testing Pyramid is properly used - some test cases can be automated on a lower level
      - • Manual testers could be
        freed to do more exploratory testing or take part in definition of requirements
    - - Why 50/50 unlikely?
        
        • Development doosn't stand still. More and more, features are added that need to be automated, so it's unlikely we will ever "catch up"
        
        • Where do you expect to find most bugs?
        
        • Manual test cases for old functionality may be written poorly, application area may not be very suitable for automation
        
        .• Some minor bugs may prevent you from automating a feature, but they will not likely to be fixed quickly
        
        • Lack of good teamwork between developers and AQAs
  - - - • Use unique accounts/users for automation
      - • Don't use existing entities (e.g. products), always create unique set of data for each test
      - • If tests rely on some configuration, inject it at runtime before test is run
      - • Clean up your data