![]() ![]() MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.Ĭall all test types from command line with MSTest.exe Unit tests, Coded UI tests, Load tests, Etc. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. 9:56 AM demo Testing SharePoint with Coded UI Tests Chris O’Brien SharePoint MVP Independent © 2007 Microsoft Corporation. navigate to web part gallery, check web part presentġ0 Testing SharePoint with Coded UI Tests to pass data) Point and click to add assertions E.g. AJAX), Silverlight, WPF, forms apps Generate code which can be modified (e.g. Recorded on test agent desktop Support: browser (inc. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. 9:56 AM demo Automating the build Chris O’Brien SharePoint MVP Independent © 2007 Microsoft Corporation. Customize workflow Mandatory for SharePoint builds Several workflows OOB DefaultProcessTemplate, LabProcessTemplate “Rebuild everything” Suits pre-live “Build current sprint against production state” Suits post-liveĨ Chris O’Brien SharePoint MVP Independent nightly), every check-in, Rolling builds etc. teardown/setup site PowerShell remoting (preferred over PsExec) Allows PS on SharePoint box to be called from build server Invoke-Command -ComputerName “foo” ħ Build definition Customize workflow Styles: What’s the trigger? “Good enough” PowerShell “Good enough” workflow (3.5 OK) TFS Team Build workflow (.Net 4.0) Specifies sequence of steps PowerShell Deploys WSPs, other deployment steps e.g. Deployment of WSPs to remote SharePoint 2010 environment Test environment, not developer machine UI testing Build fails on UI test failure Developer notificationsĦ Solution ingredients Skills TFS Team Build workflow (.Net 4.0) Release mode Testing of actual WSPs Communicationĥ Solution recipe Auto-compile of assemblies and build of WSPsĬorrect versions in source control Add a label in source control to help rollback Auto incrementing assembly version number Better tracking of deployments/fixes etc. Tracking Hard to keep track of deployments/fixes Many developers = many deployments? Inefficiency Devs keeping environment up-to-date Inconsistent builds (or buildmaster bottleneck) Silly mistakes e.g. Many dependencies Code, Features, timer jobs Deployment is complex No native support for WSP rollback Challenging to unit test Still not much traction in SharePoint world?Ĥ Challenges in *large* SP2010 dev projects Independent SharePoint consultant Blog: Book: Real World SharePoint 2010 (20 MVPs) LinkedIn: ![]() Presentation on theme: " 9:56 AM OSP432 Application Lifecycle Management - automated builds and testing for SharePoint projects Jay Schmelzer © 2007 Microsoft Corporation."- Presentation transcript:ġ 9:56 AM OSP432 Application Lifecycle Management - automated builds and testing for SharePoint projects Jay Schmelzer © 2007 Microsoft Corporation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |