Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Quality Coding: What’s New with Visual Studio 2012

741 views

Published on

The newest release of Visual Studio 2012 is rich with new tools that enhance standard developer activities. In this session, we’ll review and demonstrate some of these new features, such as Unit Testing, Code Reviews, Code Clones, and other developer tools. Come join us for this free Webinar!

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Quality Coding: What’s New with Visual Studio 2012

  1. 1. Quality Coding: Whats New with Visual Studio 2012 The newest release of Visual Studio 2012 is rich with new tools that enhance standard developer activities. In this session, well review and demonstrate some of these new features, such as Unit Testing, Code Reviews, Code Clones, and other developer tools. Come join us for this free Webinar!
  2. 2. Agenda• ALM and Quality• Quality in Requirements• Quality in Development – Unit Testing – Fakes – Code Reviews – Code Analysis – Code Clones• Quality in Test – Manual Testing – Exploratory Testing – Automated Testing – Lab Environments• Conclusion
  3. 3. Recognizing the Iterative Nature of ApplicationsInitial Project Portfolio Retire Operate Define •Monitor •Requirements •Support •Validation •Upgrade •Prioritization •Release Plan Develop •Iteration Plan •Develop Plan Plan •Test Done Work Plan Plan Done Work Plan Done Work Done Work Done Work
  4. 4. New ALM Capabilities in Visual Studio 2012 Operate Define •Monitor •Requirements •Support •Validation •Upgrade •Prioritization •Release Plan Develop •Iteration Plan •Develop •Test
  5. 5. Quality in Requirements: Storyboarding• Tighter loop between the Business Stakeholders and Development Team• Graphical design tools built in PowerPoint• Embed other content including context slides• Capture screen shots and create lightweight animations• Store common elements within a shape library• Create master templates to simplify multiple similar views• Get feedback to others – Email, print and version control the document – leverage collaborative tools – leverage web viewing tools – Integration with TFS
  6. 6. Agenda• ALM and Quality• Quality in Requirements• Quality in Development – Unit Testing – Fakes – Code Reviews – Code Analysis – Code Clones• Quality in Test – Manual Testing – Exploratory Testing – Automated Testing – Lab Environments• Conclusion
  7. 7. Why invest in quality?• Quality is an expensive (and painful) afterthought 30 25 20 Relative Cost To Fix Bugs... 15 10 5 Courtesy of the National Institute of Software and Technology (NIST)
  8. 8. Problems...• It is expensive to find and fix bugs that get past daily development practices• It is hard to diagnose errors at runtime• Why does an application run slowly?• Individual Developers and Testers need to know if they are on track• Test and development are often out of synch• Final test phase for shipping is often ad-hoc• How much testing is enough?
  9. 9. Approach for Development Quality• Use defence in depth strategy – Unit testing – Code reviews – Continuous integration builds / Gated Check-ins – Static Code Analysis – Education / Patterns / Best Practices
  10. 10. Unit Testing RunnerNew Test Runner:• Tests run in background• Run automatically on build• Support for multiple unit testing frameworks: – MS Test – xUnit – nUnit – And More!• Deep integration in the IDE• Supports native C++ code• Multiple run options – Failed Tests – Not-run Tests – All Tests• Easy code coverage access
  11. 11. Unit Testing• Diagnostic checks during development – Automated test script for methods on a type – Basic sanity checking – Useful for regression testing public double MethodA() { ... } test methods corresponding one or more Each method has public void TestMethodA() { SomeClass c = new SomeClass(); // Arrange double d = c.MethodA(); // Act Assert.AreEqual(expected, d); // Assert }
  12. 12. Use the framework you want to use• In the box support for – .NET – Native C/C++• Third party plugins – NUnit – xUnit.net – MbUnit – QUnit/Jasmine – SQL Server Unit Testing (Under development)
  13. 13. MS-Test Improvements• Many performance and scale improvements – Especially when you stick to “classic” unit testing• Support for testing Async [TestMethod] public async Task MyAsyncTest() { var result = await SomeLongRunningOperation(); Assert.IsTrue( result ); }• Proper support for 64-bit and .Net multi-targeting• Available in Express!
  14. 14. Continuous Testing• “If you aren‟t running your unit tests, you are just compiling. You are not building.”• Chris Patterson Program Manager Team Foundation Build• Run Tests After Build option in Visual Studio 2012 will run your Unit Tests after each successful build of your solution
  15. 15. Code coverage in VS 2012• Analyze your code coverage with a single click• Analyze for selected tests to help find how specific tests are covering your system• Supports all managed & native frameworks
  16. 16. DEMONSTRATION• Unit Test Basics• Unit Test Explorer• Framework Plug-Ins• Continuous Testing• Code Coverage• Play Lists (Update 2)
  17. 17. What‟s missing?• Test Lists – Legacy mode only• Test Impact – Works on the server, not in the VS client• Private Accessors – Deprecated in VS 2010, removed in VS 2012• Generate Unit Test – Didn‟t actually generate a unit test
  18. 18. Unit Testing and Isolation• Unit Tests verify the smallest testable „unit‟ of code• Target code should be isolated from external influences• Unit Test frameworks can perform integration testingUnit Test Pseudo-Code: Target Pseudo-Code: T = new SomeClass() Function DoSomething(a) Response result = T.DoSomething(1) x = LookupInDatabase(a) controlled Assert.AreEqual(2,result) y = ProcessWithWebService(x)End Function LogToFile(“Processing complete”) by test End Function Response controlled by test Response controlled by test
  19. 19. What is un-testable code?Where do we find it? Common indicators• “Get „er done” code • Complex test setup and teardown – Business logic in code-behind • Environmental dependencies – Classes with too many • Public static methods dependencies • Hidden object creation – Database logic mixed with business logic • Complex external frameworks• Testability was not a • No tests at all! consideration – Or was explicitly avoided• Monolithic, highly-coupled designs Any system where the tests require complex setup or where the tests run very slowly is unsuitable for the kind of developer testing we really care about.
  20. 20. A simple test setup exampleThe method we want to unit test bool IsFileEmpty(string file) { var content = File.ReadAllText(file); return content.Length == 0; } void FileExistsTest() { File.Write("foo.txt", ""); var result = IsFileEmpty("foo.txt") Assert.IsTrue(result); }
  21. 21. Environmental DependenciesConsider the following Y2K code: public void ThrowIfEndOfTheWorld() { if (DateTime.Now == new DateTime(2000,1,1)) throw new Y2KBugException(); }
  22. 22. Environmental DependenciesHow about this? Why is this bad? [DllImport("kernel32.dll")] extern static bool SetSystemTime(ref SystemTime time); [TestMethod] public void Y2KTest() { SetSystemTime(2000,1,1,0,0,0); Assert.Throws( () => ThrowIfEndOfTheWorld() ); }
  23. 23. Isolating code with Microsoft Fakes• Visual Studio 2012 Fakes lets you isolate almost any .NET• Fakes come in two flavors – Stubs: concrete implementations of interfaces or abstract classes – Shims: run-time interception lets you replace calls, even those from the .NET BCL
  24. 24. Visual Studio 2012 Shims – Be Cautious• Runtime interception of any .NET method – Uses the profiler to detour calls – “Monkey patching” for .NET• Use it when you… – Have external components that cannot be refactored • SharePoint, ASP.NET, Office, etc. – Need to override non-virtual methods • Static methods, constructors, sealed types, properties – Have legacy code with untestable designs
  25. 25. SharePoint Development Enhancements• SharePoint improvements (Update 2) – Unit test emulator – Coded UI test support – Web Performance test support – Load test support – IntelliTrace collection plan
  26. 26. SharePoint and Unit Testing[TestMethod]public void ScheduleAppointmentReturnsTrueWhenNewAppointmentIsCreated(){ using (new SharePointEmulationScope(EmulationMode.Enabled)) { //Arrange SPSite site = new SPSite("http://localhost"); string listName = String.Format("List{0}", Guid.NewGuid()); // create a new temporary list Guid listId = site.RootWeb.Lists.Add listName, listName, SPListTemplateType.GenericList); SPList list = site.RootWeb.Lists[listId]; Assert.IsNotNull(list); // add fields to list list.Fields.Add("Name", SPFieldType.Text, true); list.Fields.Add("Date", SPFieldType.Text, false); list.Update(); // prepare string errorMsg = string.Empty; DateTime date = DateTime.Now; BookAnAppointmentWebPart webPart = new BookAnAppointmentWebPart(); // Act bool success = webPart.ScheduleAppointment(site.RootWeb, list.Title, "My Name", "888-888-8888", "My.Name@contoso.com", "23", date, out errorMsg); // Assert Assert.IsTrue(success); // cleanup list.Delete(); site.Dispose(); }}
  27. 27. Code ReviewsPurpose: – Find and fix bugs early in the process (much cheaper and easier than later) – Adherence to development standards – Improve consistency – Improve comments and maintainability – Share best practices across the team – Educate both experienced and new team members – Improve overall structural quality of the code and skillset of the team!
  28. 28. Integrated Code Review• Provides feedback from other team members• Shared knowledge across team• Code reviews can be set as a quality gate• Source changes highlighted and comments about the changes.
  29. 29. Automated Reviews?• Static Code Analysis: – Analyze code (MSIL/SQL) based on best practices (rules) – Rules created by and used at Microsoft – Rulesets: • Selectable groups of rules allow tailoring to your environment • Rulesets can be further customized for the exact rules you need – Can support both T-SQL and .NET – Can be „enforced‟ using check-in policies – Can be reported during the build (including CI and Gated)• Still not the same as manual/peer reviews
  30. 30. Code Clone Detection• Reviews common code blocks exposing refactoring opportunities• Detect code blocks with common structure and approach• Search is semantic, not just literal• Detects „copy and paste‟ errors• Detects code fragments with a common logical structure• Review common code and decide how to proceed
  31. 31. DEMONSTRATIONCode ReviewsCode ComparisonStatic Analysis
  32. 32. Agenda• ALM and Quality• Quality in Requirements• Quality in Development – Unit Testing – Fakes – Code Reviews – Code Analysis – Code Clones• Quality in Test – Manual Testing – Exploratory Testing – Automated Testing – Lab Environments• Conclusion
  33. 33. Tester Enhancements in Visual Studio 2012• Microsoft Test Manager – Performance – Exploratory Testing – Clone test suites via command line ("versioning") – Multi-line test steps – Rich-text in test steps – Improved Test Step grid usability – Read-only test case access from within Test Runner – Pass/Fail test cases without using Test Runner – Enhanced view of results for Test Plan – Manual testing for Metro-style applications – Code Coverage for Manual Testing (Update 1) – Suspend/Resume testing for test case development• Coded UI Testing – UI Map Access – Cross Browser UI Testing (Update 1) – Test data reduction through test settings configuration• Team Web Access - Test Hub
  34. 34. Web Access – Test Hub
  35. 35. Initiating Exploratory Testing or no work item.Explore based on specific work item(s)…
  36. 36. Performing Exploratory Testing• Familiar Test Runner interface customized for exploratory testing• Free-form comment area allows tester to record suggestions and problems encountered during the session• Comment area allows for rich-text, attachments, and easy insertion of screenshot• Session can be paused to perform activities outside of the Test Runner• Bug and Test Case work items can readily be created during the exploratory testing session
  37. 37. Coded UI – UI Map EditorIt‟s in the box now!
  38. 38. DEMONSTRATIONExploratory TestingCross-browserCoded UI Testing
  39. 39. Questions?
  40. 40. Want to know more...?
  41. 41. Imaginet‟s New Blog Keeps You In The KnowStay up to speed on the latest news from Imaginet, Microsoft,Visual Studio, and the entire software development world. http://blog.imaginet.com
  42. 42. More Webcasts on ALM / TFS / Visual Studio 2012 • Quality Coding: What’s New with Visual Studio 2012 • April 4 (1:00-2:30pm CT) • April 18 (1:00-2:30pm CT) • May 9 (1:00-2:30pm CT) • May 23 (1:00-2:30pm CT) • Getting Started With Coded UI testing: Building Your First Automated Test • April 11 (1:00-2:30pm CT) • April 25 (1:00-2:30pm CT) • June 13 (1:00-2:30pm CT) • June 27 (1:00-2:30pm CT) • The How, What, and Why of Performance Testing Your Applications • May 2 (1:00-2:30pm CT) • Top Business Benefits of Application Lifecycle Management (ALM) • June 3 (1:00-2:00pm CT) • Managing Test Labs Without the Headaches • June 6 (1:00-2:30pm CT) • June 20 (1:00-2:30pm CT)
  43. 43. Free Services from Imaginet & MicrosoftThere are a number of different Microsoft Programs that youmight be able to leverage to get some free services fromImaginet:• Deployment Planning Services (DPS) – You can trade in your Microsoft Software Assurance credits to receive some free TFS/ALM Deployment Planning Services days with Imaginet• Partner Services Credit (PSC) – Have you or are you about to spend money with Microsoft on Visual Studio 2012 products? If so, Microsoft may kick in some funding to help you successfully adopt.• Virtual Technical Specialist (VTS) hours –You may be eligible to receive some free remote consulting/training hours with Imaginet through the Microsoft Virtual Technical Specialist program. For more information, email bmadison@imaginet.com.
  44. 44. Need Help with YOUR Application Lifecycle Management? Imaginet’s Visual Studio 2012 TFS Upgrade 10-day Quickstart • Includes planning and upgrading of your Team Foundation Server (TFS) to TFS 2012 • Learn best practices for source control, build management, agile methodologies, and work management processes using TFS 2012. • Support and training for your team • Includes a high-level ALM assessment Interested? Just email us at info@imaginet.com.
  45. 45. ALM Planning & Implementation ServicesALM Planning Testing• ALM Assessment & Envisioning Workshops • Manual Testing with Test Manager Quick (3 or 5 days) Start (5 days)• VS & TFS Migration Planning Workshop (5 • Visual Studio Testing Tools Quick Start (10 days) days)• TFS Deployment Planning* (5 days) • Visual Studio Automated Testing Quick Start• Visual SourceSafe to TFS Migration (5 days) Planning* (3 Days) • Visual Studio Load Testing Quick Start (5 or• Visual Studio Quality Tools Deployment 10 Days) Planning* (5 days) BuildsUpgrade • Automated Build & Release Management• TFS 2010 Adoption Quick Start (5 or 10 Quick Start (5 days) days) • Automated Build Center of Excellence (CoE)• TFS 2012 Adoption Quick Start (5 or 10 days) Database• TFS 2010 Upgrade Quick Start (10 days) • Visual Studio Database Tools Quick Start• TFS 2012 Upgrade Quick Start (10 days) (10 days)Remote Support Integrations• Remote Support for TFS & Visual Studio • Team Foundation Server (TFS) & Project Server Integration Quick Start (10 days)Lab • TFS & Quality Center Integration/Migration• Visual Studio Lab Management Quick Start Quick Start (10 days) (10 days) Email us at:
  46. 46. For questions or more information, please contact us at: info@imaginet.com or (972)607-4830 Remember to add http://blog.imaginet.com to your favorite reader!
  47. 47. http://www.imaginet.com

×