locked
SharePoint 2010 Quality Performance Testing RRS feed

  • Question

  • Hello, I am apart of a small SharePoint team that is searching for a reviewer tool that searches our created SharePoint site  through quality performance measures before we send it out to the customer (similar to a diagnostic test or so) Is there a prexisting program to do this?
    Thursday, May 30, 2013 2:22 PM

Answers

  • You've got two categories of testing there. Functional and Non Functional.

    Assuming you've done the requirement capture well you'll have a spreadsheet or list of all the requirements and methods of testing them as a pass/fail process.

    From the functional requirements you should be able to draw up some tests, i.e. If the requirement is that the home page should have a carousel which rotates through images every 15 seconds then the test is to go to the home page and check that the image rotates every 15 seconds.

    You can in most cases automate this testing process. This is most useful in scenarios where you need to perform the same tests against multiple versions of a project or over a long period. There are loads of ways to perform this testing in an automated fasion. The Visual Stuido approach can do the job very well and there are innumerable web page test applications which can be used with SharePoint.

    If you're really hard core PowerShell bods you can do it yourself with PowerShell, i've got a couple of blog posts on that but in general it's going to be more cost effective to use a dedicated testing tool.

    The non functional requirements might be harder to test in some cases, those you'll have to evaluate on a case by case basis to see if they are easy to automate and if not if they are worth automating.
    Thursday, May 30, 2013 2:57 PM

All replies

  • A good blog article on this topic can be found here.  In terms of tools (taken from that blog entry)

    Testing Tools

    This section provides links to the tools that helps in the load testing.

    Tools to generate load and test data:

    Browsers Add-Ons: There are many good tools (mostly free) that integrate with your browser to analyze each and every activity happening through your browser. You can use these tools for tuning the performance of a web site by measuring parameters such as download times, caching or the number of network round trips. [Thanks to Ed Glas for suggesting some of these tools.]

    • Fiddler – a very handy and light weight tool that can provide quick overview of you web site performance. It can also records scripts that you can use in VSTS. This MSDN article provides detailed information on how Fiddler can be used for performance tuning.
    • neXpert - an add-on to Fiddler which automates the classic performance best practice checks and produces a HTML report on the issues found in a Fiddler capture. Also adds the ability to insert step markers in Fiddler sessions to associate network objects together (create transactions). Check out more here
    • HttpWatch - an HTTP viewer and debugger. Available in commercial as well as free variants. 
    • FireBug – provides many web development tools. Integrates only with FireFox
    • YSlow - analyzes web pages and tells you why they're slow based on the rules for high performance web sites. Integrates only with FireFox

    At times, you need to focus on end-user response time. As it is difficult to simulate real life network bandwidth, it becomes difficult to test, how your application perform for end users. The following tools help you to find end-user experience

    • Visual Round Trip Analyzer - Web page performance visualizer and analyzer tool. You can find Ed Glas’s blog post introducing this tool and detailed article on using the tool.
    • webPageTest -   webPageTest is a free over-the-web tool for performance testing a page from either Dulles, VA, USA or Wellington New Zealand. Pagetest allows you to provide the URL of a webpage to be tested provides a waterfall of your page load performance as well as a comparison against an optimization checklist.

    Steven Andrews | SharePoint Professional | http://www.twitter.com/backpackerd00d | https://baron72.wordpress.com/

    • Proposed as answer by Libin.NET Thursday, May 30, 2013 6:24 PM
    Thursday, May 30, 2013 2:26 PM
    Answerer
  • I need to apologize for the rushed question, I need to clarify. We receive projects from our major contractor ranging from site designs, to custom workflows, to file migrations. Now, once these projects are complete, we want to be able to verify we have met all the requirements and it is ready to be implemented for the customer.

    We are wondering if there would be a manual solution (another developer to verify the quality of work) or a pre-existing program.

    Thank you for the response

    Thursday, May 30, 2013 2:39 PM
  • You've got two categories of testing there. Functional and Non Functional.

    Assuming you've done the requirement capture well you'll have a spreadsheet or list of all the requirements and methods of testing them as a pass/fail process.

    From the functional requirements you should be able to draw up some tests, i.e. If the requirement is that the home page should have a carousel which rotates through images every 15 seconds then the test is to go to the home page and check that the image rotates every 15 seconds.

    You can in most cases automate this testing process. This is most useful in scenarios where you need to perform the same tests against multiple versions of a project or over a long period. There are loads of ways to perform this testing in an automated fasion. The Visual Stuido approach can do the job very well and there are innumerable web page test applications which can be used with SharePoint.

    If you're really hard core PowerShell bods you can do it yourself with PowerShell, i've got a couple of blog posts on that but in general it's going to be more cost effective to use a dedicated testing tool.

    The non functional requirements might be harder to test in some cases, those you'll have to evaluate on a case by case basis to see if they are easy to automate and if not if they are worth automating.
    Thursday, May 30, 2013 2:57 PM