Software Testing with Visual Studio 2013 & Team Foundation Server 2013

1. Software Testing with Visual Studio 2013 & Team Foundation Server 2013 Benjamin Day

2. Benjamin Day • Brookline, MA • Consultant, Coach, & Trainer • Microsoft MVP for Visual Studio ALM • Team Foundation Server, Software Testing, Scrum, Software Architecture • Scrum.org Classes • Professional Scrum Developer (PSD) • Professional Scrum Foundations (PSF) • www.benday.com, benday@benday.com, @benday

3. Online courses at Pluralsight.com

5. On with the show.

6. Overview ofVisual Studio ALM.

7. A comprehensive ALM offering Web • Client • Server • Cloud • SharePoint • Java • iOS Visual Studio • Team Explorer Everywhere Scrum • CMMI • Agile Team Foundation Server Continuous Deployment Feedback Management Planning SCM Work Item Tracking Build Automation

8. Three types of testing in the VS ALM World. • Developer • “Does the code work?” • Manual Testing / Quality Assurance (QA) • “Does the app work?” • Load Testing & Performance Testing • “Does the app work under load?”

9. Test types & features. • Developer • Unit Tests • Manual / QA • Coded UI tests • Load & Performance • Web Performance Tests (WPTs) • Recorded or Coded • Load Tests

10. There are only so many minutes in the day.

11. The real question is ‘what to test?’

12. Testing ROI.

13. Testing ROI for Developers. • Write unit tests. • Test First. Test-Driven. Test-Eventually. (Whatever.) • Write something and try to be honest. • Watch your code coverage. • Why? • Helps you refactor. • Helps you modify feature functionality. • Helps you to know if it’s working a lot faster. • Tends to push you into better/cleaner architecture.

14. $1m for IT to support an application. That’s looking grim.

15. What’s that feel like? • Costs more to run the app than you actually have. • App breaks if you breathe funny. • Can’t add new features. • Changes take *FOR-EVER*. • Competitors are catching up. • You’re hosed. It’s hopeless.

16. Why’s it getting like that? • Technical Debt. • Excess “inventory”. • Too much architecture. • Brittle code. • Too hard to refactor.

17. Time to re-write the app.

18. Use tests to keep it clean.

19. Or start adding tests to change the ROI trajectory.

20. $1m for IT to support an application.

21. Solid developer testing pays huge dividends.

22. Better long-term ROI.

23. Faster time to market on new features.

24. More responsive to market withchanges to existing features.

25. Catch problems early in dev process.

26. Vastly higher quality builds for QA testing.

27. Testing ROI for QA / Manual Testing. • Track your requirements with TFS. • Track test plans, progress, and do defect trackingwith TFS and/or Microsoft Test Manager (MTM). • Use MTM Action Recordings to minimize tedium. • Look for opportunities for test automationwith MTM and Coded UI Tests.

28. Rule of thumb:At least one Test Case per Scrum PBI.

29. Coded UI Tests.

30. Coded UI helps you test a running application’s user interface.

31. Unit Tests vs. Coded UI Tests Unit Tests Coded UI Tests UI testing Test a running application Simulates a user’s keyboard and mouse activities Test stuff that’s pretty much done Integration testing • Classes and methods at the API level • If it tests a UI, it’s testing an abstraction. • (not quite testing the UI) • UI testing has been hard • Test stuff as you build it

32. The layers in your app.

33. The layers in your app. Coded UI tests Unit tests

34. Unit tests test your APIs.Coded UI Tests test your running user interfaces.

35. I tend to think of QA identifying a case that needs automation and then requesting a Coded UI Test from developers.

36. Action Recordings vs. Coded UI Tests • Action Recordings • Exist in Microsoft Test Manager • It’s there to help QA automate away tedious clicks and typing. • Make QA testing go faster. • The idea: created by non-technical users. • Coded UI Tests • Action Recordings on steroids. • It really helps to be a programmer. • You can do “asserts”. • (aka. you can do actual checks) • You can still associate them to MTM Test Cases as “Associated Automations.”

37. Structure of a Coded UI Test UIMap.designer.cs Supporting information for the test Auto-generated by the recorder Partial class UIMap.cs Partial class Customizations and extensions to the stuff in UIMap.designer.cs • The Test Fixture Class • [CodedUI] attribute • Editable like any other class • (You can even make it data-driven!) • UIMap.uitest • Auto-generated XML-based “map” of your UI • Not editable

38. Avoiding hard-coded paths in Coded UIs. • BrowserWindow class • ApplicationUnderTest window

39. Load & Performance Testing.

40. You have an application.

41. The Goal: Performance Test The Application

42. The purpose of performance tests? • Identify the capabilities of your application • Possible goals • Explore • Verify • Find the limits • Crush

43. Performance testing in a nutshell. • Throw traffic at the app. • Does it perform as expected? • Recreate any performance problems. • Fix the performance problems. • Repeat.

44. What can you load test with Visual Studio 2012 Ultimate? • ASP.NET with an HTML UI • Web Forms or MVC • (This is the sweet spot.) • SharePoint Applications • HTTP-based applications • ASP.NET-based SOA apps • Service-based apps with WebAPI or REST • Coded UI Tests • Pretty much anything you can call from a Visual Studio Unit Test

45. Demos.

46. Demos Web & Load Tests WPT Basics Load Test Basics Custom PerfMon Counters Load in the Cloud Load using Test Rigs • Unit Tests • Code Coverage • QA Testing • Project Management • Sprint Planning • Test Case Management • Test using MTM • Test using web • Test using web + test runner • Test environment manager

47. Any last questions?

48. Thanks.benday@benday.com | www.benday.com