The document discusses the benefits and challenges of test automation, emphasizing its importance for efficient regression testing and faster deployments. It outlines common reasons for the lack of adoption, such as the initial time investment and maintenance challenges, while proposing strategies for developing effective testing approaches. The document advocates for a balanced testing strategy that includes a mix of unit tests and selected end-to-end tests, promoting the adoption of test-driven development (TDD) practices.

1. Test Automation Benefits
“There’s no place for
human beings to be doing
regression testing
manually.”
-Jez Humble

2. Save resources
Example:

3. More testing during development

4. Speedier deployments
• Faster through the testing phase
• More likely the 1st deployment will be correct

5. Why don’t more people use them?

6. Reasons used for not having them
• Extra time to create them
• Learning Curve/Experience
• They can be more code than the actual software
• More to maintain
• They take time to run

7. Overcoming the Impediments

8. Browser API Services Domain DAL
• Limited paths
• Smoke
• Slow, hardest to maintain
• More test setup required
than unit
• Closely-
collaborating
components
• Complex
interactions, many
permutations faster
to test
Browser automation
JavaScript unit
tests
API-level AATs
(integration
tests)
Integration tests
Integration tests
Unit testsUnit tests
• Complex
query
permutation
• Logic
permutati
ons
• Fastest
• Isolated
• Fast
• Checks any
UI
• Processes /
preparing
and what is
sent to the
API is ok
• Check
business
requirements
• Limited paths
• Slower than
unit
• More test
setup required
than unit
Develop a
Testing
Strategy

9. Know what tests to write when
• Balance high # of unit tests + selected end-to-end & acceptance
• AATs should be a small portion of your test suite
• Is your new feature entirely new?

10. Acceptance
Component
Unit
Black box
White box
End-to-end
Business facing
Localized
Technology
facing
Testing Strategies

11. The First Tests…
• Find the most crucial and most changed functionality.
• Determine if the code is testable. If not, start with black box end-to-
end tests.
• Once code is being covered by tests in some way, start refactoring it
so unit tests can be written.

12. When a bug isn’t caught
• See why bug got through the existing unit/integration tests
• Add unit, integration tests for it
Unit

13. Test First Approach
• Create tests up front. Helps guide code creation and makes it easier
to think through the functionality, and tests.
• Start using TDD when appropriate

14. Champion Testing
• Show the data on how automated testing reduces bugs, results in
better architected code, and saves time and money.
• Coach team members who don’t have enough experience
• Pair program
• Review open source projects test strategies and code