Your SlideShare is downloading. ×
Share point 2010 unit and integration testing
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Share point 2010 unit and integration testing

4,006

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
4,006
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
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

Transcript

  • 1. Feature Coding Part 3Unit and Integration Testing DEV_205 Eric Shupps
  • 2. About Me Eric Shupps, MVP  President, BinaryWave  Email: eshupps@binarywave.com Microsoft Patterns & Practices: spg.codeplex.com CKS:DEV cksdev.codeplex.com Blog: www.sharepointcowboy.com Twitter: @eshupps Facebook: www.facebook.com/sharepointcowboy
  • 3. Agenda Testing Fundamentals Code Optimization Unit Testing Integration Testing
  • 4. Testing Fundamentals
  • 5. Testing Objectives• Less rework • Eliminate defects• Shorter cycles • Validate functionality• Faster delivery times • Reduce complexity• Fewer support requests Reduce Ensure Costs Quality Increase Improve Efficiency Dynamics • Faster changes • Facilitate change • Repeatable processes • Simplify integration • Increased confidence • Increase modularity
  • 6. Testing Methodologies Any methodology is better than no methodology Select a methodology that supports the team dynamic and satisfies the testing objectives Code for the customer/end user, not the methodology Focus on modularity and sustainability
  • 7. Testing Lifecycle Unit Integration Regression
  • 8. Code Optimization
  • 9. Code Isolation and Refactoring Class Method Method Method Method Method Method Class Class Class Method Method Method Method Method Method Test Test Test Test Test Test
  • 10. Refactor the core solution components for testability.CODE ISOLATION
  • 11. Unit Testing
  • 12. Unit Testing Objectives Integrate Validate Refactor Isolate Code Maintain
  • 13. Unit Testing Principles Separate interface from implementation Fail first in order to succeed Tests do not drive functionality - they verify functionality Features define tests and tests define methods Tests should exercise all probable execution paths
  • 14. Unit Testing Methodologies Separate interface from implementation Fail first in order to succeed Tests do not drive functionality - they verify functionality Features define tests and tests define methods Tests should exercise all probable execution paths
  • 15. Create and execute unit tests for isolated code.UNIT TESTS
  • 16. IntegrationTesting
  • 17. Integration Testing Objectives Test code execution against Verify methods as Validate/invalidate target they will be used in unit test resultssystem/dependenci released code es Identify Exercise all points vulnerabilities in of interoperability execution chain
  • 18. Integration Testing Principles Tests should exercise actual dependencies – no mocks or stubs Tests should not be authored or driven by developer Tests should cover all application tiers (top- down, bottom-up, or both) Manual testing is acceptable (and often preferred)
  • 19. Integration Testing Methodologies Inverse Isolation  Reusing unit tests by replacing mock or stub objects with actual implementations Black Box  Open-ended, interface- driven tests that explore available functionality and are not driven by specific feature requirements White Box  Predefined set of test routines that verify specific functional requirements
  • 20. Create and execute integration tests for core solution components.INTEGRATION TESTS
  • 21. Thank you for attending!(This slide must always be the last slide in your deck)

×