Download to read offline
Uploaded byEatDog
Стероиды для Дотнетчика
The document discusses strategies for .NET developers to enhance their coding efficiency and streamline development processes. Key concepts include implementing continuous integration and delivery pipelines, establishing an iterative workflow, and utilizing various testing methodologies, including acceptance tests and unit tests. Tools such as Git, TeamCity, and Octopus are recommended for version control and deployment, along with resources for further learning and improvement.
More Related Content
Similar to Стероиды для Дотнетчика
Стероиды для Дотнетчика
- 1. Steroids for .NET Developers SerhiyKalinets @skalinets kalinets@gmail.com Rails Reactor
- 2. About Me 16 yearsin the business In .NET since 2005 Love to code Software Architect @ Rails Reactor @skalinets 2
- 3.
- 4.
- 5. Developer Should Spend moretime coding Spend less time for other stuff Get the most fun while coding @skalinets 5
- 6.
- 7. IRL • Non technicalsh*t (meetings etc.) • Deployment • Debugging • Troubleshooting • Environment Setup @skalinets 7
- 8. Everything should beno-brainer • Continuous Integration • Continuous Delivery • Continuous Deployment • Continuous Development @skalinets 8
- 9.
- 10. Main Ideas • Iterativeprocess • Start with infrastructure and delivery process (Iteration 0) • Requirements Acceptance Test Development via TDD Ready Feature @skalinets 10
- 11. Iteration 0 (WalkingSkeleton) • Build • Run Unit Tests • Prepare Deployment Package • Deploy to Dev • Run Acceptance Tests • Deploy to QA @skalinets 11
- 12.
- 13. Build: Fake (F#Make) • If you ever wanted to use F# @skalinets 13
- 14.
- 15. Delivery Pipeline Tools VCS:git CI: TeamCity Deployment: Octopus Versioning: gitversion @skalinets 15
- 16.
- 17. 40 34 36 30 26 28 26 0 2 4 6 8 10 12 0 4 0 4 6 2 2 1 23 4 5 6 7 Bugs Regression Features @skalinets 17
- 18. Levels of Testing •Unit • Integration • Acceptance • Manual (Exploratory) @skalinets 18
- 19. Acceptance Tests • Testsystem or application from end to end • In most cases interact with UI • If not possible – test closest to UI (API) @skalinets 19
- 20. • Regression • Shouldalways be Green • In-Progress • Can be red while feature is being developed 2 Acceptance Sets @skalinets 20
- 21. Acceptance Tests: Canopy •Human friendly DSL for web testing • Wraps WebDriver • Uses F# @skalinets 21
- 22. module MyTests open canopy letfwdays () = // context is used to group tests context “Just some tests" // this is a test name "Demo canopy on fwdays 2017" &&& fun _ -> // open URL url "https://frameworksdays.com" // the rest might not need explanation click ".NET fwdays '17" click "Программа" click "Стероиды для Дотнетчика" @skalinets 22
- 23.
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30. Mock, stub, fake,spy, test double? Strict or loose? Nah, just substitute for the type you need! From http://nsubstitute.github.io/ @skalinets 30
- 31.
- 32. • When addingnew post to the blog • It should be saved in database Demo Scenario @skalinets 32
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42. • http://bit.ly/dotnet-steroids • http://fsharp.github.io/FAKE/ •http://nsubstitute.github.io/ • https://github.com/AutoFixture/AutoFixture • http://approvaltests.com/ • https://lefthandedgoat.github.io/canopy/ • https://xunit.github.io/ • http://fluentassertions.com/ links @skalinets 42
- 43.