Performance and Load Testing of SharePoint 2013/2016 with ADFS

%3CLINGO-SUB%20id%3D%22lingo-sub-3017%22%20slang%3D%22en-US%22%3EPerformance%20and%20Load%20Testing%20of%20SharePoint%202013%2F2016%20with%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3017%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20everyone%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20was%20a%20question%20I%20posed%20on%20Twitter%20with%20the%20hashtag%20of%20%23sphelp%2C%20but%20did%20not%20get%20a%20response.%20The%20question%20is%2C%20using%20Visual%20Studio%202015%20for%20performance%20and%20load%20testing%20of%20SharePoint%202013%2F2016%20doesn't%20appear%20to%20be%20truly%20viable%20because%20of%20the%20limitation%20of%20Visual%20Studio%202015%20test%20tools%20(doesn't%20allow%20for%20javascript%20to%20run%20at%20all).%20Since%20this%20is%20the%20case%20does%20anyone%20have%20any%20recommendations%20on%20a%20load%20or%20performance%20testing%20solution%20for%20SharePoint%202013%2F2016%20that%20will%20allow%20for%20pass-through%20of%20ADFS%20tokens%2Fcredentials%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-7267%22%20slang%3D%22en-US%22%3ERe%3A%20Performance%20and%20Load%20Testing%20of%20SharePoint%202013%2F2016%20with%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-7267%22%20slang%3D%22en-US%22%3EI%20don't%20agree%20VS%202015%20Test%20Tools%20are%20limited%20to%20do%20load%20testing...what%20you%20need%20is%20to%20plan%20and%20design%20carefully%20your%20performance%20and%20load%20test%20architecture%20so%20you%20can%20really%20extress%20your%20farm%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-7155%22%20slang%3D%22en-US%22%3ERe%3A%20Performance%20and%20Load%20Testing%20of%20SharePoint%202013%2F2016%20with%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-7155%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3EI%20have%20tested%20SP2013%20using%20Visual%20Studio%20ultimate.%20I%20used%20Visual%20Studio%20to%20capture%20interactions%20between%20the%20client%20and%20SharePoint%202013%20and%20then%20replay%20these%20interactions%2C%20usually%20as%20a%20performance%20test%2C%20to%20ensure%20that%20nothing%20I%20have%20done%20has%20comprimised%20the%20functionality%20and%20performance%20of%20my%20SharePoint%202013%20farm.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENigel%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Visitor

Hey everyone,

 

This was a question I posed on Twitter with the hashtag of #sphelp, but did not get a response. The question is, using Visual Studio 2015 for performance and load testing of SharePoint 2013/2016 doesn't appear to be truly viable because of the limitation of Visual Studio 2015 test tools (doesn't allow for javascript to run at all). Since this is the case does anyone have any recommendations on a load or performance testing solution for SharePoint 2013/2016 that will allow for pass-through of ADFS tokens/credentials?

 

Thanks!

2 Replies
Highlighted

Hi

I have tested SP2013 using Visual Studio ultimate. I used Visual Studio to capture interactions between the client and SharePoint 2013 and then replay these interactions, usually as a performance test, to ensure that nothing I have done has comprimised the functionality and performance of my SharePoint 2013 farm.

 

Regards

 

Nigel

Highlighted
I don't agree VS 2015 Test Tools are limited to do load testing...what you need is to plan and design carefully your performance and load test architecture so you can really extress your farm