Test your own stuff agile testing days usa 2018
•
1 j'aime•81 vues
Presentation given at Agile Testing Days USA in Boston June 2018
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Test your own stuff agile testing days usa 2018
Similaire à Test your own stuff agile testing days usa 2018 (20)
Dernier
Dernier (20)
Test your own stuff agile testing days usa 2018
- 1. Test Your Own Stuff! Dealing With Dependencies Between (and on) Agile Teams Alex Kell Agile Testing Days USA 2018 @wiggly
- 2. Dependencies Kill Agility @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 3. @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 4. LOTR Wikia @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 5. What are some “true” dependencies? Go to this page on your computer or mobile device https://pollev.com/alexkell820 and write in your own answer! @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 6. Assumptions https://sites.google.com/site/reflection4learning/double-loop-learning @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 7. Dependencies Blocker s Yaks Us @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 8. Dependencies Blocker s Yaks Us @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 9. Dependencies as Blockers Troy Aikman recollected that Deion Sanders considered tackling a “business decision.” Sanders responds: “Hey, these shoulders are made for suits, not Brandon Jacobs.” (SBNation - 11/23/2009) @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 10. Dependencies as Blockers Troy Aikman recollected that Deion considered tackling a “business decision.” Sanders responds: “Hey, these shoulders are made for suits, not Brandon Jacobs.” (SBNation - 11/23/2009) Excuses @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 11. Dependencies as Yaks You’ve been on a call for two hours trying to upgrade the server infrastructure for the entire company…why? Well it all began because their tests aren’t working because our system is down so you check the logs and determine that the system downstream of yours is down so you try to contact their lead, but you remember he’s on west coast time and isn’t in yet so you decide to turn on the mocks you wrote last sprint but when you turn them on they don’t work on the shared servers because they all have .Net 3.5 on them so you decide to upgrade the server to 4.2, but you can’t because they belong to the Enterprise Infrastructure department and you don’t have access rights so you call up the help desk and try to open a ticket to get the servers upgraded… @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 12. Dependencies of our Own Making • Debt – We’ll build it now even though we can’t test it • Rules – Let’s agree or conform to a rule that says we have to wait to test until software has been installed on the “Test” server • Process – Ready In Progres s Done @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 13. Dependencies of our Own Making • Debt – We’ll build it now even though we can’t test it • Rules – Let’s agree or conform to a rule that says we have to wait to test until software has been installed on the “Test” server • Process – Ready Dev QA Done @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 14. I M P A C T High Impact Low Control Low Impact High Control High Impact High control Low Impact Low Control C O N T R O L @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 15. I M P A C T High Impact Low Control Many “true” dependencies – order these. Low Impact High Control High Impact High control Test Your Own Stuff Low Impact Low Control (laws, policy) C O N T R O L @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 16. Discussion Take a few minutes and write down some dependencies you have – maybe from what you’ve already written – see if you can classify them based on the model: BLOCKER YAK US What How to Fix Bypass/Mitigate Examine -> stop! Identify -> change What How to Fix Bypass/Mitigate Examine -> stop! Identify -> change @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 17. Conway’s Law Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure. – Melvin Conway @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 18. Component Teams vs. Feature Teams FeatureA FeatureB FeatureC FeatureD Component 1 Component 2 Component 3 @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 19. Component Teams vs. Feature Teams FeatureA FeatureB FeatureC FeatureD Component 1 Component 2 Component 3 TEAM TEAM TEAM @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 20. Component Teams vs. Feature Teams FeatureA FeatureB FeatureC FeatureD Component 1 Component 2 Component 3 TEAM TEAM TEAM @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 21. Component Teams vs. Feature Teams FeatureA FeatureB FeatureC FeatureD Component 1 Component 2 Component 3 TEAM TEAM TEAM TEAM @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 22. We can’t test until the other team finishes their: •Service •UI •Database update •API •… @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 23. Types of Automated Checks Unit UI Smoke Component SystemAcceptance Integration Micro Functional Performance Load End-To-End @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 24. Functional /Integration Story /Feature Acceptance Simulations/Workflows Exploratory Usability User Acceptance Unit Component Performance Load Security Other “ility” Business Facing SupportingtheTeam Technology CritiquingtheProduct Automated and Manual Manual Automated/ ToolsAutomated Copyright @ 2009 Crispin/Gregory
- 25. Unit A Test is NOT a unit test if • It talks to the database • It communicates across the network • It touches the file system • It can’t run at the same time as any of your other unit tests • You have to do special things to the environment (like editing config files) to run it Michael Feathers http://www.artima.com/weblogs/viewpost.jsp?thread=126923 @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 26. Why Unit Checks? Or Integration Tests are a Scam! 10 States 10 States 10 States 5 interactions 5 interactions 5 interactions Functional Grenning http://www.renaissancesoftware.net/blog/archives/514#more-514 @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 27. 10 States 10 States 10 States 5 interactions 5 interactions 5 interactions Unit Unit Grenning http://www.renaissancesoftware.net/blog/archives/514#more-514 Why Unit Checks? Or Integration Tests are a Scam! @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 28. Calculator Example @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 29. @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 30. Functional • Check the interactions of one or more component within the system • Do make use of configurations, networks, databases, and file systems • Sometimes check performance @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 31. Acceptance • Ideally written during “refinement” • Given/When/Then format • Like Functional tests, but not as comprehensive • Meant as a: – Guide for the team – Progress checker for the Feature team – Documentation for internal and external people • Automated! @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 32. ATDD @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 33. End-to-end Functional Unit Exploratory The Test Automation Pyramid Originated by Mike Cohn @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 34. End-to-end Functional Unit Acceptance Acceptance Acceptance Exploratory The Test Automation Pyramid @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 35. End-to-end Functional Unit Acceptance Acceptance Acceptance Exploratory Exploratory Exploratory The Test Automation Pyramid @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 37. How do we decide what tests we need?
- 38. Continuous Integration • You should do it – drives changes in behavior • Gated check-ins? Yes or No Build Type Unit Functional Acceptance Check-in/On-Demand X ? “Nightly” X X ? Deployments X X X @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 39. @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 40. Service Service Service Application DB DB External System External System Service @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 42. Example Functional Tests • Consumer Driven Contracts {“Id”:123456, ”AccountType”:”Checking”, ”AccountNum”:”495928832”, ”Amount”:250, ”SenderId”:5555, ”ReceiverId”:4444} Consumer 1 Consumer 2 Consumer 3 {“Id”:123456, ”AccountType”:”Checking”, ”Amount”:250} {“Id”:123456, ”SenderId”:5555} {“Id”:123456, ”AccountType”:”Checking”, ”AccountNum”:”495928832”, ”Amount”:250, ”ReceiverId”:4444} @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 43. Example Functional Tests • Consumer Driven Contracts {“Id”:123456, ”AccountType”:”Checking”, ”AccountNum”:”495928832”, ”Amount”:250, ”SenderId”:5555, ”ReceiverId”:4444} Consumer 1 Consumer 2 Consumer 3 {“Id”:123456, ”AccountType”:”Checking”, ”Amount”:250} {“Id”:123456, ”SenderId”:5555} {“Id”:123456, ”AccountType”:”Checking”, ”AccountNum”:”495928832”, ”Amount”:250, ”ReceiverId”:4444} @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 44. Example Functional Tests • Consumer Driven Contracts {“Id”:123456, ”AccountType”:”Checking”, ”AccountNum”:”495928832”, ”Amount”:250, ”SenderId”:5555, ”ReceiverId”:4444} Consumer 1 Consumer 2 Consumer 3 {“Id”:123456, ”AccountType”:”Checking”, ”Amount”:250} {“Id”:123456, ”SenderId”:5555} {“Id”:123456, ”AccountType”:”Checking”, ”AccountNum”:”495928832”, ”Amount”:250, ”ReceiverId”:4444} @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 45. Example Functional Tests • Consumer Driven Contracts {“Id”:123456, ”AccountType”:”Checking”, ”AccountNum”:”495928832”, ”Amount”:250, ”SenderId”:5555, ”ReceiverId”:4444} Consumer 1 Consumer 2 Consumer 3 {“Id”:123456, ”AccountType”:”Checking”, ”Amount”:250} {“Id”:123456, ”SenderId”:5555} {“Id”:123456, ”AccountType”:”Checking”, ”AccountNum”:”495928832”, ”Amount”:250, ”ReceiverId”:4444} @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 46. Example Functional Tests • Consumer Driven Contracts {“Id”:123456, ”AccountType”:”Checking”, ”AccountNumber”:”495928832”, ”Amount”:250, ”SenderId”:5555, ”ReceiverId”:4444} Consumer 1 Consumer 2 Consumer 3 {“Id”:123456, ”AccountType”:”Checking”, ”Amount”:250} {“Id”:123456, ”SenderId”:5555} {“Id”:123456, ”AccountType”:”Checking”, ”AccountNum”:”495928832”, ”Amount”:250, ”ReceiverId”:4444} @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 47. Example Functional Tests • Consumer Driven Contracts {“Id”:123456, ”AccountType”:”Checking”, ”AccountNum”:”495928832”, ”Amount”:250, ”SenderId”:5555, ”ReceiverId”:4444, “Duration”,.005} Consumer 1 Consumer 2 Consumer 3 {“Id”:123456, ”AccountType”:”Checking”, ”Amount”:250} {“Id”:123456, ”SenderId”:5555} {“Id”:123456, ”AccountType”:”Checking”, ”AccountNum”:”495928832”, ”Amount”:250, ”ReceiverId”:4444} @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 49. Wait, but…You can’t go to Prod like this!!
- 50. Wait, but…You can’t go to Prod like this!! Yes, um…you can, and we have many times!
- 51. ASTEROID Debit Card Network Payment Service Payment Service SIMULATOR/MOCKS Promote to Production @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 52. ASTEROID Debit Card Network Payment Service Payment Service SIMULATOR/MOCKS ISO Format ISO Format Promote to Production @wiggly Agile Testing Days USA 2018 #AgileTDUSA
- 53. References • XUnit Patterns – Gerald Meszaros • Developsense blog – Michael Bolton • Dependencies Break Agile – Michael Cottmeyer • I’ve got Integration and System Tests, Why do I Need Unit Tests? – James Grenning • Integration Tests are a Scam! – J.B. Rainsberger • Managing Requirements Dependencies Between Agile Teams – Scott Ambler • Driving Development With Tests: ATDD and TDD – Elisabeth Hendrickson • Consumer Driven Contracts – Ian Robinson • Feature Teams (LeSS) – Bass Vodde, Craig Larman • Conway’s Law – Melvin Conway • Don’t Shave That Yak – Seth Godin @wiggly Agile Testing Days USA 2018 #AgileTDUSA