All pages
Jump to navigation
Jump to search
- ABSTRACTION LEVELS
- AD-HOC AUTOMATION
- ASK FOR HELP
- AUTOMATE EARLY
- AUTOMATE GOOD TESTS
- AUTOMATE THE METRICS
- AUTOMATE WHAT'S NEEDED
- AUTOMATION DECAY
- AUTOMATION ROLES
- Acknowledgements
- Automation isn't what they expected
- BRITTLE SCRIPTS
- BUGGY SCRIPTS
- CAN'T FIND WHAT I WANT
- CAPTURE-REPLAY
- CELEBRATE SUCCESS
- CHAINED TESTS
- CHECK-TO-LEARN
- COMPARE WITH PREVIOUS VERSION
- COMPARISON DESIGN
- COMPLEX ENVIRONMENT
- Charlie Chainer
- Creation or maintenance of test data
- DATA-DRIVEN TESTING
- DATA CREEP
- DATE DEPENDENCY
- DATE INDEPENDENCE
- DEDICATED RESOURCES
- DEFAULT DATA
- DEPUTY
- DESIGN FOR REUSE
- DOCUMENT THE TESTWARE
- DOMAIN-DRIVEN TESTING
- DON'T REINVENT THE WHEEL
- DO A PILOT
- Debbie Disappointed
- Debbie Disappointed Solution
- Design Issues
- Design Issues Mind Map
- Design Patterns
- Design Patterns Mind Map
- Developer
- Developers don't help the automation team
- Diagnostic
- Discussions and Challenges
- Disposing of redundant data
- EASY TO DEBUG FAILURES
- EXPECTED FAIL STATUS
- EXPECT INCIDENTS
- Execution Issues
- Execution Issues Mind Map
- Execution Patterns
- Execution Patterns Mind Map
- Exercise SET CLEAR GOALS
- Exercise Solutions
- Exercises
- Expectations for automated test execution not met
- FAIL GRACEFULLY
- FALSE FAIL
- FALSE PASS
- FLAKY TESTS
- FRAMEWORK COMPETITION
- FRESH SETUP
- FULL TIME JOB
- Failure Patterns
- Feedback
- Freddie Frustrated
- GET ON THE CLOUD
- GET TRAINING
- GIANT SCRIPTS
- GOING FOR THE NUMBERS
- GOOD DEVELOPMENT PROCESS
- GOOD PROGRAMMING PRACTICES
- Glossary
- HARD-TO-AUTOMATE
- HARD-TO-AUTOMATE RESULTS
- HIGH ROI EXPECTATIONS
- INADEQUATE COMMUNICATION
- INADEQUATE DOCUMENTATION
- INADEQUATE RESOURCES
- INADEQUATE REVISION CONTROL
- INADEQUATE SUPPORT
- INADEQUATE TEAM
- INADEQUATE TECHNICAL RESOURCES
- INADEQUATE TOOLS
- INCONSISTENT DATA
- INDEPENDENT TEST CASES
- INEFFICIENT EXECUTION
- INEFFICIENT FAILURE ANALYSIS
- INFLEXIBLE AUTOMATION
- INSUFFICIENT METRICS
- INTERDEPENDENT TEST CASES
- Improve or revive test automation
- Insufficient set-up information
- Introduction and Background
- Ivan Indispensable Solution
- Ivan Indispensible
- Ivy Independent
- KEEP IT SIMPLE
- KEYWORD-DRIVEN TESTING
- KILL THE ZOMBIES
- KNOW-HOW LEAKAGE
- KNOW WHEN TO STOP
- LATE TEST CASE DESIGN
- LAZY AUTOMATOR
- LEARN FROM MISTAKES
- LIMITED EXPERIENCE
- LITTER BUG
- LOCALISED REGIMES
- LONG SET-UP
- LOOK AHEAD
- LOOK FOR TROUBLE
- Lack of direction
- Lack of resources
- Lack of specific knowledge
- Lack of support
- MAINTAINABLE TESTWARE
- MAINTAIN THE TESTWARE
- MANAGEMENT SUPPORT
- MANUAL INTERVENTIONS
- MANUAL MIMICRY
- MIX APPROACHES
- MODEL-BASED TESTING
- MULTIPLE PLATFORMS
- Main Page
- Maintenance costs too high
- Maintenance expectations not met
- Management Issues
- Management Issues Mind Map
- Management Patterns
- Management Patterns Mind Map
- Management expectations for automation not met
- Managers don't see the value
- MediaWiki
- Mindmup
- NON-TECHNICAL-TESTERS
- NO INFO ON CHANGES
- NO PREVIOUS TEST AUTOMATION
- Nancy Naive
- Nobody helps new automators
- Not reusing existing data
- OBJECT MAP
- OBSCURE MANAGEMENT REPORTS
- OBSCURE TESTS
- ONE-CLICK RETEST
- ONE CLEAR PURPOSE
- Other costs
- Owen Optimistic
- PAIR UP
- PARALLELIZE TESTS
- PLAN SUPPORT ACTIVITIES
- PREFER FAMILIAR SOLUTIONS
- PRIORITIZE TESTS
- PT-Diagnostic
- PT-Test Automation Issues
- People costs
- Portuguese Main Page
- Preparing the expected results is difficult
- Process Issues
- Process Issues Mind Map
- Process Patterns
- Process Patterns Mind Map
- READABLE REPORTS
- REFACTOR THE TESTWARE
- REPETITIOUS TESTS
- RIGHT INTERACTION LEVEL
- RIGHT TOOLS
- Refactoring the automation scripts
- References
- SCHEDULE SLIP
- SCRIPT CREEP
- SELL THE BENEFITS
- SENSITIVE COMPARE
- SET CLEAR GOALS
- SET STANDARDS
- SHARED SETUP
- SHARE INFORMATION
- SHORT ITERATIONS
- SIDE-BY-SIDE
- SINGLE PAGE SCRIPTS
- SKIP VOID INPUTS
- SPECIFIC COMPARE
- STALLED AUTOMATION
- STEEL THREAD
- SUT REMAKE
- Setting up the initial environments is difficult
- Sharon Stressed
- Solution ideas for Automation Goals Exercise
- Solution to Charlie Chainer
- Solution to Freddie Frustrated
- Solution to Ivan Indispensible
- Solution to Ivy Independent
- Solution to Nancy Naive
- Solution to Owen Optimistic
- Solution to Sharon Stressed
- Solution to Ted Toolswitcher
- Solution to Ursula Unfocused
- Solutions
- Specialists don't help the automation team
- TAKE SMALL STEPS
- TEMPLATE TEST
- TESTABLE SOFTWARE
- TESTWARE ARCHITECTURE
- TEST AUTOMATION BUSINESS CASE
- TEST AUTOMATION FRAMEWORK
- TEST AUTOMATION OWNER
- TEST DATA LOSS
- TEST SELECTOR
- TEST THE TESTS
- THE NIGHT TIME FALLACY
- THINK OUT-OF-THE-BOX
- TOOL-DRIVEN AUTOMATION
- TOOL DEPENDENCY
- TOOL INDEPENDENCE
- TOOL MUSHROOMING
- TOO EARLY AUTOMATION
- Ted Toolswitcher
- Test Automation Issues
- Test Automation Issues Mind Map
- Test Automation Patterns
- Test Automation Patterns Mind Map
- Test Manager
- Test automators need training
- Tester
- Testers don't have time
- Testers don't help the automation team
- Testers think that the Software Under Test is too complex for automation
- The scripts are not reliable
- The scripts are so complicated that nobody understands them
- The scripts are too slow in execution
- Training
- UNATTENDED TEST EXECUTION
- UNAUTOMATABLE TEST CASES
- UNFOCUSED AUTOMATION
- UNMOTIVATED TEAM
- UNREALISTIC EXPECTATIONS
- Updating the automation scripts
- Ursula Unfocused
- VARIABLE DELAYS
- VERIFY-ACT-VERIFY
- VISUALIZE EXECUTION
- WHOLE TEAM APPROACH