Continuous Delivery and Team Foundation Server Ognjen Bajić Ana Roje Ivančić Ekobit

Transcription

1 Continuous Delivery and Team Foundation Server 2013 Ognjen Bajić Ana Roje Ivančić Ekobit

2 Turn off your mobile. Thank you.

3 Agenda Continuous Delivery Challenges Automated Build with Build Verification Tests Functional Testing Test Lab Environments Automating the Release Cycle

4 Continuous Delivery Challenges

5 Continuous Delivery Continuous Quality Continuous Feedback

6 Delivery at the Speed of Sound Release cycles are getting shorter MS Office every 3-4 years MS Office every week TFS VS Online - every 2-3 years - every 3 weeks, bug fixes anytime Continuous deployment WordPress 16 releases daily over the period of four years Solves customer business problems in timely fashion

7 Achieving Continuous Quality on the Road Towards Continuous Delivery Continuous Deployment with Release Management Automated build and Continuous integration (CI) Source control everything Manual acceptance tests Exploratory testing Generation of automated regression tests End-to-end automated Build-Deploy-Test workflow Realistic test environments Test Lab Clean configuration on virtual machines Automated Functional acceptance tests Coded UI Tests (data driven) BVTs Static code analysis, Unit tests (Data driven), Code coverage, Code metrics, Layer Validation, Perf and Load Tests

8 Automated Build with Build Verification Tests

9 Automated Build with Continuous Integration - CI Reflects progress and ensures consistency of changes Establish the automated build from the day one No other measure is more useful Easy to implement with TFS and VS Build multiple solutions, managed/unmanaged code, different platforms/languages Setup wizard and runtime infrastructure Based on MS Build and Windows Workflow technologies Configurable, extensible, scalable

10 Convert automated builds to Continuous Integration builds Execute builds after each check in The fastest error warning system

11 Configure Build Verification Tests BVTs Execute automated tests and run different validations Default Build Template Static Code Analysis (FxCop) Unit Tests Code Coverage Layer Analysis Customized Build Template Style Analysis (Style Cop) Code Metrics Security Analysis (Code analysis tool - CAT.NET)

12 12

13 Functional Testing

14 Coded UI Tests = Automated tests of the user interface Simulate user interaction with controls on the screen (mouse click, typing) Can verify application behavior and results displayed on the screen Turn manual tests into automated tests Enable functional testing/validation of the user interface Enable automated regression testing Integrated with Build, Lab and Release Management Run as part of build Run as part of Build-Deploy-Test workflow in Test Lab Run as part of Release Management workflow VS 2013 extends list of supported technologies and platforms Fully supported: Partly supported: Not supported: Web, Win Forms, WPF, IE 8/9/10, SHPT, Windows Store Apps (XAML based) Chrome/Firefox, WIn32/MFC, Dynamics CRM IE 6/7, Opera/Safari, Office, Silverlight, Flash/Java

15 Automation Platform Support (VS 2013) Platform Support Notes IE 8/9/10 Fully supported Win Forms/WPF SHPT Windows Store Apps (XAML based) Dynamics (Ax) MFC Citrix/Terminal Srv. Fully supported Fully supported Fully supported Partially supported. Dynamics CRM web client is supported. Partial support Partial support Chrome/Firefox Latest version supported from VS Win32 May work with some known issues, but not officially supported. Office Client Apps IE 7/6/ Opera/Safari Silverlight/Flash/Java SAP

16 Coded UI Tests Unit tests for the UI (C# or VB.NET) Data-driven (CSV, Excel, Access-DB, SQL, Test Case) Depend on UIMap generation Generate some tests quickly without writing code Generate from recordings for manual Test Cases (used for fast-forward in manual testing) Generate manually by recording actions on the screen (Coded UI Test Builder) Develop full blown CUIT infrastructure Record controls (Coded UI Test Builder) and programmatically simulate user interactions Better manage UIMaps (page object pattern) Add assertions and validations Control mechanism for searching controls on the screen Use support for data-driven testing Add support for custom controls Add logging VS 13 lowers the price of automated testing Automation saves time for the testers, but increases load on developers

17 17

18 Test Lab Environments

19 Test Lab TFS includes virtualized Test Lab Test environment one or more physical/virtual machines managed together (may even use Azure VMs!) Integration of Build and Lab Automated workflow: BUILD - DEPLOY- TEST Easily setup testing environment for each test run Can save snapshot of the environment with the app. installed (only VMs) Facilitates automated and manual testing Automated - Run as part of build-deploy-test workflow Manual - Tester restores snapshot and runs tests Easy testing in all supported configurations Run same battery of automated tests in all your test environments Unit Tests, Data-Driven, CUITs, Generic (*.exe), Ordered

20 Test Lab: Build Deploy Test workflow Traditional build workflow 1 Build Application 2 Deploy Application 3 Run Tests Lab build workflow Build Application Restore Snapshot Run Tests Restore Environment Take Environment Snapshot Deploy Application

21 Test Lab: Build Deploy Test workflow Lab build workflow Build #1: Build Build Test App Application Restore Snapshot Run Tests Take Environment Snapshot Restore Environment Build #2: Lab Workflow Build Deploy Test Deploy Application

22 22

23 Automating the Release Cycle

24 Release Management for Visual Studio 2013 Provides a continuous deployment solution Simplifies managing multiple staging environments Automates the deployment process to all stages Enables configuration-based deployments Integrates with TFS ALM Automates workflow Enables a business-approval workflow Improves collaboration throughout the process Enables full traceability Provides release analytics and reporting Team Foundation Server DEV INT QA PROD

25 25

26 Step-by-Step Guide to Continuous Delivery Step 1 Source Control Everything Step 2 Automated Builds with Build Verification Test Step 3 Continuous Integration Step 4 Lab Environments Step 5 Release Management

27 Q&A.

28