�ݺ�ߣ

100% walkaway automation
100% Walkaway Automation

100%
› 100% automated
› 100% walkaway
› 100% of the time

Walkaway
› Runs unattended
› Doesn’t need maintained
› Doesn’t break
› Fails fast when it does
› You know exactly what went wrong
› It’s easy to fix

Automation
› Fast
› you don’t wait for it
› Reliable
› it doesn’t break
› Accurate
› no false positives

It ain’t gonna happen.
› 100% walkaway automation is an ideal
› How do you work towards a goal that’s not achievable?
› That’s not S.M.A.R.T.
› Don’t let the perfect be the enemy of the good
› Don’t use it as an excuse to procrastinate

What can I do now?
› Evaluate where you are
› Identify weak points
› Pick low hanging fruit
› Make a plan
› Set S.M.A.R.T. goals
› Short , medium, long term

Where are you now?
› Unit tests
› Integration tests
› System tests
› Builds
› Deployments
› Requirements coverage

Test Certification
http://dw/Teams/Test_Tools/Test_Certification_Guide

Go
› PKG pipeline
› ACC pipeline
› PRD pipeline
What do you need to make Go work for you?

Step away from the GUI
› It’s brittle
› It’s too high level
› Isolate the system
› Use fakes
› Test features at the feature level

Apps are like Ogres
› Big, green, and smelly
› No, layers
› Isolate concerns
› What is your testing perspective?

UI tests are fragile
› The UI changes frequently
› Layers of abstraction
› Too much maintenance
› Feedback is not instant

What should you
automate?
› Repetitive
› Slow
› Error-prone
Automate if it is faster than doing it manually

Unit Tests
› Code coverage
› Are they really unit tests?
› Mock dependencies
› Design for testability
› Architecture
› Components

Feature Tests
› Test the feature
› Isolate the system
› Use fakes
› Describe the feature
› Tests as documentation

System Tests
› Stable environment
› Stable tests
› Real (or nearly real) data
› For testing the whole system
› Not end-to-end unit tests

Manual Tests
› Presentation & Layout
› Usability
› Exploratory testing

Regression Tests
› Repeatable
› Automated
› Every time you build

Automate defects
› Write a test that fails for every defect
› Automate it

Build Automation
› Works for me
› Anyone should be able to checkout and run
› It should build on GO agents
› It should be clear why it fails
› Know your dependencies
› tools , scripts, environment variables, data

Deployment
› Can you do it without manual intervention?
› What would it take?
› Manual tests, automated decisions

Requirements
› Executable tests
› Traceability
› Testable acceptance criteria

Let’s put the “D”
back in TDD
› Test Driven Development
› Write the tests first
› Anyone should be able to test
› It doesn’t have to be 100% automated yet

Let’s put the “D”
back in BDD
› Behavior Driven Design
› Product should own acceptance criteria
› Business can help write tests
› Tests should express a user’s needs

User Stories
› Are about the user
› Tell a story
› Have a plot
› with conflict and resolution
› Not just “Gherkin” unit tests

Test Harnesses
› Make developers write the code
› Define the requirement
› What are your inputs?
› How do you check expected results?

Who you gonna call?
SETs
› Evaluate your test certification goals
› Write test harnesses & tools
› Embed on your team
› Short term
› Help make code testable
› Teach test automation practices

�ݺ�ߣ

walkaway-automation

More Related Content

walkaway-automation

Editor's Notes