Quel développeur n’a jamais rêvé d’avoir une assurance qualité de bout en bout pour éviter le stress et les cauchemars ? Historiquement avec SharePoint on a toujours dit que c’était chose compliquée, coûteuse etc… Nous verrons un ensemble d’outils et de solutions avec Visual Studio Team Services qui vous démontreront le contraire et vous n’aurez plus d’excuses après cette session pour automatiser la qualité dans vos processus. Au programme : - Gestion des sources et des branches - Build automtisé de solutions/apps SharePoint - Déploiements automatisés - Tests automatisés - Qualité de code Nombreuses démonstrations

1. Mise en place de
votre processus DevOps
avec Office, Office 365 et
SharePoint
@baywet#SPSMonaco

2. #SPSMonaco

3. @baywet
bit.ly/vincentbiret
Vincent Biret
MVP Office Servers and Services
Azure and Office 365 developer @ 2ToLead

4. Who’s this session for?

5. Agenda
•The new stack for SharePoint Framework
•Intro to Software lifecycle + devops
•Intro to VSTS/Azure
•The build system + deploy
•Unit tests with SPFX
•Intro to tech debt management
•Conclusion

6. Ready?

7. Modern toolchain for SharePoint/Office 365 developers at last
The new stack

8. IIS Express
Project Templates
Server side tool comparison

12. Bill is awesome!

13. The webpart project
Demo

14. Where it all begins
Software lifecycle

15. Software lifecycle : devops
Plan
Dev
Test
Production
Idea/Need Business Plan
Marketing Sales
Market
Feedback
Agile/CMMI/…
Architecture
Source Control
IDE
Build
xTests

16. Let’s talk about tooling
Visual Studio Team Services and Azure

17. You’ve probably heard about it
Azure
•Microsoft’s Cloud platform
•IaaS, PaaS, SaaS
•Literaly tons of services

18. Visual Studio Team Services
• TFS as a service
• Updated more frequently
• Pay per user/build
• Everything except
• SharePoint Integration
• Process Template Customization**
• Data Warehouse

19. Code as a team, not a guy in a cave
Branch management

20. Git + git flow
• Git is a decentralized source control technology
• Branches are cheap
• Merging is not a nightmare
• Cross platform
• Lot of tools
• Git flow is a process model for branch management
• Focused work
• Easy context switching
• Standard and no thinking required
• Semver…

21. Let’s increase the quality of releases
Build

22. Automated builds
•Predictable result
•Constant quality
•Time saving

23. Build 2015
•JSON definition
•Web edition
•Lot of third parties integrations
•Tasks on github! (see notes)
•Agent auto updates!

24. Agents
•Hosted Agents
•BaaS
•Installed Agents
•Azure, or anywhere else

25. Build section, build agents 2015
Demo

26. Automate all the things!
Deploy

27. Pick and choose!
Different schools
• Source promotion
• We promote to next level a certain state of source
• Rebuild if needed
• Build promotion
• Exact same binaries are promoted

28. VSTS – Release Management
•Same technology as the build 2015
•Notion of environments
•Approvals

29. Office 365 CDN
1. Configure Office 365 CDN to replicate site assets
2. Configure Urls in configuration files
3. Bundle files
4. Bundle app package
5. Upload js/json to sharepoint (custom task)
6. SharePoint replicates to CDN
7. Win!

30. MH and small project deployment with RM
Demo

31. Final touch to QA
Test

32. Tests levels
•Unit testing
•Load testing
•Integration testing
•System testing
•Functional/Acceptance testing

33. Tests types
•Installation
•Compatibility
•Regression
•Destructive
•Security
•L17N/I13N
•A/B
•…..

34. Test tooling
Runners Assertion libraries Emulators/Env Reporters Frameworks
Karma Chai + as promised PhantomJS Junit Mocha
MSTest MS.Test ns Node (backend) Coverage Casper
Istanbul Chrome Cobertura Jasmine
… … …
Runners: take care of running the tests and provide the infrastructure for (memory, processes…)
Asseration libraries: « ways » to write your unit tests
Emulators (or environments): context within the tests will run (server with node, browser, emulated browser…)
Reporters: take care of writing down tests results in comprenhensive format
Frameworks: provide a suite of functionnalities to help implement testing

35. Unit tests of demo webpart
Demo

36. Or how to avoid digging your own grave
Technical debt management

37. What is tech debt?
•Code we’re not comfortable with
•Preventing us from innovating
•Causing a lot of support
•Stressful for the team

38. Solutions?
•Rewrite everything every 2 years
•Pair coding
•Static analysis + linting

39. SonarQube for MH, linting for demo webpart
Demo

40. I swear, I’m going to stop talking soon and let you free
Conclusion

41. Conclusion
•Lot of time saved
•Consistent builds
•Automated tests
•Quality increased
•Money saved

42. Merci
Bit.ly/vincentbiret @baywet slideshare.net/VincentBIRET
#SPSMonaco