Categories
- Agile (6)
- Architecture (1)
- art (2)
- Big Data (1)
- books (11)
- Cars (1)
- Change (9)
- common sense (3)
- Contracting (1)
- Cool (1)
- Design (5)
- development (1)
- emotions (3)
- entrepreneurship (2)
- google (1)
- great quotes (2)
- happiness (1)
- innovation (3)
- IT (8)
- IT Architecture (3)
- Knowledge Transfer (2)
- leadership (3)
- Lean (1)
- links (1)
- literature (1)
- lyrics (1)
- management (9)
- Media (1)
- Negotiating (1)
- networks (1)
- people (5)
- Personal Improvement (8)
- planning (5)
- productivity (3)
- Programming (1)
- Project Management (23)
- Projects (1)
- psychology (3)
- Requirements (5)
- Risk (2)
- scrum (2)
- strategy (6)
- struggle (1)
- summer (1)
- teams (5)
- Test Automation (3)
- thinking (5)
- Training (2)
- Travel (1)
- waterfall (4)
Tag Cloud
Agile
Architecture
art
Big Data
books
Cars
Change
common sense
Contracting
Cool
Design
development
emotions
entrepreneurship
google
great quotes
happiness
innovation
IT
IT Architecture
Knowledge Transfer
leadership
Lean
links
management
Media
Negotiating
people
Personal Improvement
planning
productivity
Programming
Project Management
Projects
psychology
Requirements
Risk
scrum
strategy
teams
Test Automation
thinking
Training
Travel
waterfall
Software Test Automation
Posted by Rich Crowley in books, Test Automation
Of the three testing books I read over the past few months, this one was the one that gave me the best overview of test automation as a discipline of its own.
What was interesting to me is that the book was written some time ago (1999) and in some places it feels “old”. However, the authors have spent considerable time in this area and are very articulate about the principles that govern automation and these principles seem to me to still apply today based on projects I manage.
While the high level principles are what guides the structure of the book, the book gets into considerable detail as well. There are excellent sections debunking myths about automation – for example, record and playback of test cases is not automation. Likewise the section on testware architecture is really good.
If you’re looking for a good grounding in automation as a starting point in either a project management capacity or general IT management capacity, this book is a good one. Read the table of contents and I’m sure you’ll be convinced.