Coding Naked 2023
•
0 gefällt mir•48 views
Coding Naked – Practical steps to moving towards & embracing TDD. We'll overview the normal roadblocks that people typically run in to, and practical ways to overcome those road blocks on your way to embracing Test Driven Development - make coding without tests as uncomfortable as coding naked! Code: https://github.com/calebjenkins/Acme.CodingNaked Presenting at events: https://developingux.com/tag/coding-naked/
Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie Coding Naked 2023
Ähnlich wie Coding Naked 2023 (20)
Mehr von Caleb Jenkins
Mehr von Caleb Jenkins (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Coding Naked 2023
- 1. u n i t t e s t i n g t h o s e h a r d t o r e a c h p l a c e s !
- 6. Automated Unit Test Fundamentals Hard to Reach Places
- 8. Is TDD only for coding elites?
- 9. or something for every developer?
- 10. How do we make Automated Tests the norm?
- 11. make coding without tests as uncomfortable as coding naked
- 12. * this is not me
- 13. 13 what are the 4 big parts of unit tests?
- 14. Test Framework Test Runner Code Tests 14
- 15. Test Framework Test Runner Code Tests 15 your application what you want to test your test code the code that tests the code that you wrote or are going to write attributes and asserts the framework provides the attributes and asserts so we know what the tests are doing. Examples: nUnit jUnit cppUnit runs the tests often associated with the test framework; is distinctly separate. sometime integrated in IDE, CI Server or stand alone exe
- 17. Start Test Runner Test Code Test Framework
- 21. Visual Studio (VS Test Adapters: xUnit ,nUnit, VS Test etc) > dotnet test (cli) Continuous Integration (Team City) Continuous Integration (GitHub Actions) Test Runners
- 22. Test Artifacts 22 BDD Artifacts Code Coverage / Complexity
- 23. 3 A’s 23 – Set up the scenario and the initial input values. Often in a common [TestFixtureSetup] or [Setup] method - Action that creates the outcome that is being tests, usually calling some method in your code to test the result. – Is a boolean statement to your testing framework to declare the expected outcome. Results in Pass or Fail Arrange Act Assert Test Code
- 24. Data Access Data Logic Integration Service Proxy App Domain Domain Validation UI Logic UI Building better Lego’s Tests are small Tests are fast Tests focus on one thing
- 28. Test Runner return values no dependencies… App Domain Domain Validation UI Logic Test Code Unit Tests focus on a Unit Test a unit in isolation from other units Control input => Testable output Simple Tests
- 29. VSTest
- 30. Start Test Runner Test Code Test Framework
- 32. Set the Scene
- 34. what if our “tests” matched our language? Discussion
- 35. what if our “tests” matched our language? Discussion
- 36. Discussion BDD
- 37. Discussion BDD
- 38. Resources & Frameworks BDD http://neelnarayan.blogspot.com/2010/07/bdd-is-more-than-tdd-done-right.html more than TDD done right http://dannorth.net/introducing-bdd/ introducing BDD http://lucisferre.net/2011/02/05/behavior-driven-test-driven-domain-driven-design/ behavior driven, test driven, domain driven nBehave, nSpec, SpecFlow, StoryQ, mSpec, StorEvil, Cucumber
- 41. Dependencies “The single greatest thing that you can do to make your code more testable and healthy is to start taking a Dependency Injection approach to writing software” - Real World .NET, C# and Silverlight Wrox Press 2012 Caleb Jenkins
- 42. Data Access Data Logic Integration Service Proxy App Domain Domain Validation UI Logic UI How do you test this with these dependencies Harder to Test
- 43. Data Access Data Logic Integration Service Proxy App Domain Domain Validation UI Logic UI
- 44. Test Runner Test Code Integration Service Proxy App Domain Domain Validation UI Logic Dependency Injection + Interfaces Faked dependencies to increase unit isolation Leverage mocking frameworks makes life better
- 45. Note: Dependency Injection will turn you in to a complete coding Ninja, however the full scope of DI with any of the many DI frameworks is beyond the scope of this talk
- 48. - Real World .NET, C# and Silverlight Wrox Press 2012 Caleb Jenkins Mocking Framework “A mocking framework allows you to create fake classes on the fly in- line with your test code. That is a bit of a simplification, mocking frameworks use a combination of emits, reflection and generics to create run-time instance implementations of .NET Interfaces – whew, that’s a mouthful - it’s a whole lot easier to say that they create fake classes on the fly!”
- 51. IData mockData = MockRepository.GenerateMock<IData>(); mockData.Expect(x => x.getAll<account>()) .Return(sampleAccounts).Repeat.Once(); IAccountServices accountService = new AcmeAccountService(mockData); var act = accountService.GetAccount(known_account_id); mockData.VerifyAllExpectations();
- 52. IData mockData = MockRepository.GenerateMock<IData>(); mockData.Expect(x => x.getAll<account>()) .Return(sampleAccounts).Repeat.Once(); IAccountServices accountService = new AcmeAccountService(mockData); var act = accountService.GetAccount(known_account_id); mockData.VerifyAllExpectations();
- 53. IData mockData = MockRepository.GenerateMock<IData>(); mockData.Expect(x => x.getAll<account>()) .Return(sampleAccounts).Repeat.Once(); IAccountServices accountService = new AcmeAccountService(mockData); var act = accountService.GetAccount(known_account_id); mockData.VerifyAllExpectations();
- 54. Set the Scene Handle your Dependencies (DI + Mocks)
- 55. the problem with edges
- 56. UI Data Business Edges are Hard to Test
- 57. Testing edges can be like testing to see if you’re good at cliff jumping
- 58. That’s not me
- 59. ..or you’re stuff on a rock. You’re either an expert and it works…
- 60. UI Data Data Logic UI Logic Business Edges are Hard to Test Edges are still Hard to Test by separating UI/Data edges from UI/Data logic we’re increasing the testable area we’ve also made it easier to implement various UI and Data platforms without affecting the application logic
- 61. Edges are all around us Data UI Network Disk IO other
- 62. Edges are all around us Network
- 63. Edges are all around us INetworkProxy Retry Logic / Formatting
- 67. These examples are for the expressed purpose of demonstrating unit testing scenarios.. none of this code (especially the supporting non-testing code) is intended to be deployed in production scenarios. This is just some code from a talk at some conference. There's no warranty, express or implied. Works on my machines. I don't know you and I don't know how you got here. Stop calling. Caleb Who?! 👀
- 72. “Don’t be silly” - Roy Osherove The Art of Unit Testing pg. 77
- 75. the problem with statics
- 77. shared state be like.. also applies to statics, hard-coded singletons, globally scoped variables
- 79. DI Lifecycles
- 82. IDependency Idependency Extension Method Class to Test Idependency Method Idependency Method (sometimes, not even) Idependency Method
- 90. // Clean up after test
- 96. the challenges with Microsoft Fakes
- 98. Find the edges Keep the edges thin Stop coding naked
Hinweis der Redaktion
- Ubiquitous language between Business <> Technology
- Ubiquitous language between Business <> Technology
- Nothing worse than seeing/…. Test 1, Test 2, Test 3.. What do those even mean?!
- Nothing worse than seeing/…. Test 1, Test 2, Test 3.. What do those even mean?!
- SpecFlow is very much Cucumber for .NET
- Build out slide.. Before you click through: take a minute to have student “read” test and talk out what it’s doing.
- Build out slide.. Before you click through: take a minute to have student “read” test and talk out what it’s doing.
- Build out slide.. Before you click through: take a minute to have student “read” test and talk out what it’s doing.
- Other edges.. Active Director / Oauth Claims / User Credentials Logging, Configuration, Property Files, many many more.
- I ❤Extension Methods.. But I have to be careful, and tread carefully.
- https://github.com/calebjenkins/Acme.CodingNaked/blob/main/src/WithExtensionsLibTests/BusinessProcessStartTests_Reset_Failure.cs#L37