Tag Info

Hot answers tagged

13

CruiseControl.NET, NAnt/MSBuild, WSPBuilder and some PowerShell scripts along with a virtual machine. Cruise kicks off the process where the VM starts up from a template and the scripts/solutions are deployed (via a network share). The VM runs automated scripts (Selenium) to automate some tests and report back out to Cruise (and other tools). The entire ...


8

There are a couple of options here: Use STSADM -o backup/restore Use STSADM -o export/import Use Content Deployment, perhaps with the SharePoint Content Deployment Wizard (a tool I wrote) When you use backup/restore, you get everything - including recycle bin content, running workflows, alerts etc etc. This may or may not be what you want. Such ...


5

My biggest issue with testing timer jobs was getting the job to start so that I could debug it. It seems like I when I reset the timer service whenever I deployed new code and when the service restarted, even though I had my job to run every minute, sometimes it would take up to an hour for it to "catch up" and get around to running my timer job. I think ...


5

RIGHT click on IE hold SHIFT and then RIGHT click again on IE LEFT click "Run as different user" login Repeat 1.- 4. for other users :)


4

Setup a content deployment job. Do a Backup-SPSite, Restore-SPSite Use the content deployment wizard tool (Neeed to install this on both servers for export, import) Database detach and reattach. (4) is laborious and it also seems to retain webapp urls as-is. So you will see http://test urls in your content after you move to prod. I'd do #2 or #3 (if you ...


4

Ok there are a few ways to do it: "Save as template" and include content (The amount of content is limited but should be enough in most cases) Database backup/restore as PirateEric wrote Granular backup in the CA (To find in Backup and Restore / Granular Backup) You can then select a site or List and export it. It can include the permissions but I am not ...


4

I'd say either a content database detach and restore into production, or using stsadm/powershell to backup the site collection and restore into production.


3

You could use SPDeploy from Codeplex (of which I'm a contributor). http://spdeploy.codeplex.com/ You supply an XML file (there samples included, as well as full XSD so you can get intellisense when building your XML), and SPDeploy will create the structure. You want to create hundreds of teamsites though, so you'd have to create hundreds of lines of XML ...


3

You can use Pex and Moles to unit test SharePoint in isolation. There are 2 tutorials to get started: Unit Testing SharePoint with Moles Unit Testing SharePoint with Behaviors


3

Unit Testing on SharePoint only really begins to work properly when you mock the SharePoint object model using one of a few methods. Andrew Woodward over at 21apps.com has documented his findings of this, particularly with using TypeMock Isolator for SharePoint. http://www.21apps.com/category/agile/testing/ I also seen a recent presentation of his which ...


3

You can use System.Diagnostics.Debugger.Launch(); to attach a debugger (Visual Studio) instead of attaching the timer job in VS. Also i tend to use DebugView alot to just write out asserts or messages like System.Diagnostics.WriteLine("sometext","MYCATEGORY"); Another tip for testing is to encapsulate the logic in its own class. Then you can test ...


3

Their are two options for test farm either stand alone or single server farm(complete). Stand Alone: The standalone installation type installs SharePoint using the Local Service and Network Service accounts and a SQL Express instance. It is not a farm and has limitations such as: Standalone is not a SharePoint farm Cannot join additional servers (since ...


3

There's a bunch of options: You can easily open up to 6 browser sessions: IE, IE InPrivate, Chrome, Chome Incognito, Firefox, Firefox Private browsing (+ Opera or else if you want!). They all have their own session/authentication information, and you can log in with 6 different users. At the same time, if you're developping in SharePoint, you can test ...


3

Personally, I use 3 browsers for testing with different users, this is the best way I think, you don't need to install a small VM, that's too dear and long to do it. Chrome, Firefox, Safari, Opera and Maxthon is your friends. Easy to install and test, just enjoy it.


2

A couple of small things you have probably already considered. Stop and restart the Timer service as part of the pre-build event to release any of your solution's GAC dlls. Rather than attaching to the process using the debugger I prefer to use System.Diagnostics.Debugger.Break(); For other SharePoint related guidelines, check out our free SharePoint ...


2

Visual Studion 2010 Team Suite - test edition is definitely the way to go. I created custom code to create a site collection with a deep enough page hierarchy and enough documents to produce a 2GB website automatically. That was more work than creating the load tests to actually load it. Using a load test agent and controller to generate more load ...


2

When creating the workflow, assuming you're using SharePoint Designer, you can store the information in a variable and output it to the workflow history or email yourself the value. That's how I test data I'm not entirely sure how it will come back or what the format of it will be.


2

As you seem to want to do this in production mode, I would suggest looking at a supported third-party tool. It may be overkill in your case (and over budget too!). You will need to weigh your needs versus the additional capabilities these types of tools provide. Two tools that come to mind are: AvePoint DocAve Replicator Repliweb Operations Suite for ...


2

As both Anders and Steve have pointed out, write the main processing of your timer job in a separate Class Library. For debugging "wrap" a Console App around it, and when you're happy wrap it in a timer job. If at a later point you want to debug, you use your Console App again - F5 and there you go. On a related note, check out SharePoint Layered ...


2

As a newer answer, we're using Visual Studio test lab management to spin up Hyper-V snapshots. Once they're up, the system is installed/upgraded using a custom deployment application launched from TFS Build. We haven't got automated tests working against the deployed system quite yet, but that's the general plan.


2

I get the impression that when you say "test" you mean "learn how to use advanced/admin features of SharePoint". For your purposes, it may be sufficient to set up a 2nd web application or even site collection on your existing farm. For other purposes (e.g. if you want to experiment in central admin) you can install SharePoint and SQL on the same server - ...


2

Remember the old "log in as different user" from SP2010? Well it's still there - just browse to <yourSharePoint>/_layouts/15/closeConnection.aspx?loginasanotheruser=true


2

Use chrome and create multiple users In settings you can shift to a different user using top right menu every user opens in a seperate window. Each window uses its own cache, saved passwords, bookmarks etc.


1

I followed the steps in this blog - http://www.sharepointnutsandbolts.com/2012/04/sharepoint-2010-and-unit-tests-from.html, except it worked for me without step 1 (changes to devenv.exe.config) Basically, make sure the project targets 3.5, use "Any CPU", and make sure the .testsettings files are set to use 64 bit. The blog says it is NOT supported through ...


1

You can just script the rename's with Powershell utilizing the Set-Spsite cmdlet with the URL parameter. If you script your restores to your enviroments, you can just have the rename kick off after restore is completed and DB attached to a webapp. URL rewritting isn't supported with SharePoint, that's why they have AAM's (of course you can't use them with ...


1

Since you need to install Farm-Trust solutions (like Timer Jobs), shared hosting solutions are not gong to work. Dedicated hosting solutions are more aligned with running a production SharePoint environment and are going to be very expensive (since they often include production licensing costs). For temporary testing environments I would suggest either ...


1

I usually just don't put in an outgoing e-mail server. If email functionality is needed, alerts are easy to remove for a test farm. It's unsupported to modify the sp databases directly but all the alerts for a db are stored in two tables: SchedSubscriptions and ImmedSubscriptions. Just delete all of the rows in those two tables and there won't be any ...



Only top voted, non community-wiki answers of a minimum length are eligible