• Like

Quality Coding: What’s New with Visual Studio 2012 (08082013)

  • 484 views
Uploaded 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 …

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!

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
484
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
14
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • This is the teaser for the class – we will preview (in slides) many of the topics that we’ll dive into deeply as part of this training class…
  • This is the teaser for the class – we will preview (in slides) many of the topics that we’ll dive into deeply as part of this training class…
  • Speaker notes:1. While we are expanding support for 3rd party frameworks, we have lots of customers who are on MSTest and we will continue investing in it for them2. Potential rude QA, Mstest sucks because….Where is Assert.Throws?Where is DataRow support?Answer: We are fully aware that we are behind on some key features, we are not done yet and will keep working to close the gap here
  • As needed, use this as an opportunity to demonstrate work items in general. For an upgrade class, hopefully this is minimized.
  • Peter – fix the final sentence this time. 
  • Image source: http://www.sxc.hu/photo/1125087
  • Maybe retitle this?
  • BHARRY: Unit testing – One of the big problems with unit testing SharePoint is that most code requires SharePoint to be running and trying to run tests against a live SharePoint instance is a pain.  So we’ve built a SharePoint “emulator” using our new VS 2012 Fakes & Stubs capability.  This will make unit testing of SharePoint components WAY easier.Coded UI support – Our 2012 product was pretty close to supporting this but there were a few SharePoint specific issues that we weren’t able to address that made CodedUI (functional testing) not work well for SharePoint.  In our first update, we will have addressed those issues.Workarounds documented for Excel on Sharepoint 2010, Visio\Powerpoint controls, and SharePoint Silverlight controlsLoad testing – We now support load testing for SharePoint out of the box.  This is more involved than you might imagine due to how dynamic SharePoint is.  You can’t just record a script and play it back – it won’t work because SharePoint generates and expects dynamic data (like GUIDs).  We’ve built the extensions to our load testing solution to parse the dynamic SharePoint data and include it appropriately in subsequent requests.  So now you can record a script and play it back and we will dynamically adjust it to match what SharePoint expects.IntelliTrace collection plan – While this won’t be in the first CTP, we’re building a custom IntelliTrace collection plan for SharePoint that helps filter out a bunch of the SharePoint “infrastructure noise” and lets you focus on events related to your components that are the likely cause of problems you are seeing.SOMA: SharePoint Development. Beyond the core platform support for SharePoint development available via “Napa” and the Office Developer Tools for Visual Studio, with Visual Studio 2012 Update 1 we’ve invested in building out significant new application lifecycle management (ALM) capabilities for SharePoint applications.  This work is primarily centered around multiple forms of testing: from load testing that enables the stressing of SharePoint applications with simulated load and network conditions; to performance testing that enables recording and running performance suites against SharePoint solutions; to unit testing that enables coded UI tests for simulating user interaction and that enables using the Microsoft Fakes Framework for stubbing out SharePoint dependencies in unit tests.  Update 1 also updates IntelliTrace to capture SharePoint logging information, in order to provide a rich analysis experience for SharePoint applications.
  • VS Blog:SharePoint Emulators provide a system of Fakes based shims implementing the basic behaviors of the SharePoint 2010 server object model. SharePoint Emulators are available today through a NuGet package feed. Perform a simple search of the NuGet official feed for “SharePoint Emulators”.SharePoint Emulators are easy to incorporate into existing tests. You can write tests against the SharePoint Emulators using only the SharePoint API. All that is needed is the wrapping of test code in a SharePointEmulationScope.
  • There are also things like JSLint, etc. for other platforms
  • As needed, use this as an opportunity to demonstrate work items in general. For an upgrade class, hopefully this is minimized.
  • This is the teaser for the class – we will preview (in slides) many of the topics that we’ll dive into deeply as part of this training class…
  • Source: http://blogs.msdn.com/b/visualstudioalm/archive/2012/02/29/what-s-new-for-microsoft-test-manager-in-visual-studio-11-beta.aspx?PageIndex=2#comments
  • As needed, use this as an opportunity to demonstrate work items in general. For an upgrade class, hopefully this is minimized.
  • Want to know more?
  • Want to know more?

Transcript

  • 1. Quality Coding: What's 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, 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!
  • 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. Initial Project Portfolio Retire Recognizing the Iterative Nature of Applications Define •Requirements •Validation •Prioritization •Release Plan Develop •Iteration Plan •Develop •Test Operate •Monitor •Support •Upgrade Plan WorkDone Plan WorkDone Plan WorkDone Plan WorkDone Plan WorkDone
  • 4. New ALM Capabilities in Visual Studio 2012 Define •Requirements •Validation •Prioritization •Release Plan Develop •Iteration Plan •Develop •Test Operate •Monitor •Support •Upgrade
  • 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. 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. Why invest in quality? • Quality is an expensive (and painful) afterthought 5 10 15 20 25 30 Relative Cost To Fix Bugs... Courtesy of the National Institute of Software and Technology (NIST)
  • 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. 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. Unit Testing Runner New 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. public double MethodA() { ... } Unit Testing • Diagnostic checks during development – Automated test script for methods on a type – Basic sanity checking – Useful for regression testing public void TestMethodA() { SomeClass c = new SomeClass(); // Arrange double d = c.MethodA(); // Act Assert.AreEqual(expected, d); // Assert } Eachmethodhas oneormore corresponding testmethods
  • 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. 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. 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. 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. DEMONSTRATION • Unit Test Basics • Unit Test Explorer • Framework Plug-Ins • Continuous Testing • Code Coverage • Play Lists (Update 2)
  • 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. 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 testing Target Pseudo-Code: Function DoSomething(a) x = LookupInDatabase(a) y = ProcessWithWebService(x) LogToFile(“Processing complete”) End Function Unit Test Pseudo-Code: T = new SomeClass() result = T.DoSomething(1) Assert.AreEqual(2,result) End Function Response controlled by test Response controlled by test Response controlled by test
  • 19. What is un-testable code? Where do we find it? • “Get „er done” code – Business logic in code-behind – Classes with too many dependencies – Database logic mixed with business logic • Testability was not a consideration – Or was explicitly avoided • Monolithic, highly-coupled designs Common indicators • Complex test setup and teardown • Environmental dependencies • Public static methods • Hidden object creation • Complex external frameworks • No tests at all! 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. void FileExistsTest() { File.Write("foo.txt", ""); var result = IsFileEmpty("foo.txt") Assert.IsTrue(result); } File.Write("foo.txt", ""); A simple test setup example The method we want to unit test bool IsFileEmpty(string file) { var content = File.ReadAllText(file); return content.Length == 0; } File.ReadAllText(file);
  • 21. Environmental Dependencies Consider the following Y2K code: public void ThrowIfEndOfTheWorld() { if (DateTime.Now == new DateTime(2000,1,1)) throw new Y2KBugException(); }
  • 22. [DllImport("kernel32.dll")] extern static bool SetSystemTime(ref SystemTime time); [TestMethod] public void Y2KTest() { SetSystemTime(2000,1,1,0,0,0); Assert.Throws( () => ThrowIfEndOfTheWorld() ); } Environmental Dependencies How about this? Why is this bad?
  • 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. 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. 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. 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. Code Reviews Purpose: – 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. 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. 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. 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. DEMONSTRATION Code Reviews Code Comparison Static Analysis
  • 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. 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. Web Access – Test Hub
  • 35. Initiating Exploratory Testing or no work item. Explore based on specific work item(s)…
  • 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. Coded UI – UI Map Editor It‟s in the box now!
  • 38. DEMONSTRATION Exploratory Testing Cross-browser Coded UI Testing
  • 39. Questions?
  • 40. Want to know more...?
  • 41. Imaginet‟s New Blog Keeps You In The Know http://blog.imaginet.com Stay up to speed on the latest news from Imaginet, Microsoft, Visual Studio, and the entire software development world.
  • 42. More Webcasts on ALM / TFS / Visual Studio 2012 • Quality Coding: What’s New with Visual Studio 2012 • 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. Free Services from Imaginet & Microsoft There are a number of different Microsoft Programs that you might be able to leverage to get some free services from Imaginet: • 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. Need Help with YOUR Automated Testing? • Learn best practices for test selection, extension, data binding, maintenance, frameworks, community extensions (such as the CUITe and the UI Map Toolbox), and other real-world scenarios. • Includes automated test development & execution for YOUR application • Support and training for your team • Includes a high-level ALM assessment Imaginet’s Visual Studio 2012 Automated Testing 5-day Quickstart Interested? Just email us at info@imaginet.com.
  • 45. Email us at: ALM Planning & Implementation Services ALM Planning • ALM Assessment & Envisioning Workshops (3 or 5 days) • VS & TFS Migration Planning Workshop (5 days) • TFS Deployment Planning* (5 days) • Visual SourceSafe to TFS Migration Planning* (3 Days) • Visual Studio Quality Tools Deployment Planning* (5 days) Upgrade • TFS 2010 Adoption Quick Start (5 or 10 days) • TFS 2012 Adoption Quick Start (5 or 10 days) • TFS 2010 Upgrade Quick Start (10 days) • TFS 2012 Upgrade Quick Start (10 days) Remote Support • Remote Support for TFS & Visual Studio Lab • Visual Studio Lab Management Quick Start (10 days) Testing • Manual Testing with Test Manager Quick Start (5 days) • Visual Studio Testing Tools Quick Start (10 days) • Visual Studio Automated Testing Quick Start (5 days) • Visual Studio Load Testing Quick Start (5 or 10 Days) Builds • Automated Build & Release Management Quick Start (5 days) • Automated Build Center of Excellence (CoE) Database • Visual Studio Database Tools Quick Start (10 days) Integrations • Team Foundation Server (TFS) & Project Server Integration Quick Start (10 days) • TFS & Quality Center Integration/Migration Quick Start (10 days)
  • 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. http://www.imaginet.com