Tests of SharePoint. First Steps


Starting to work with SharePoint’om, one of the first voporsov, ask themselves: "What can we do?". Indeed, the draft contains two or three site collections, dozens of sites, dozens (even hundreds) of web desk, designed for thousands of users, it’s hard not to get lost. In this case, as usual, time to deal with all this is not, and should test now. While surfing through endless expanses of the Internet is unlikely to bring the desired result. Of course, you will find a lot of manuals, but they are designed primarily for either developers or users, but not for the testers. I hope at least a little to fix this situation will help the material. Above all, it will be useful for those just beginning to familiarize themselves with SharePoint’om.

Pre-apologize for not fully / properly translated terms. I just have not turned language called Content Type – the type of material or Web Part – a web part. Yes, in fact, very few of you called Content or Test Case.

SharePoint As Is

Before proceeding to the testing, perhaps it is worth finding out what it represents SharePoint. By its very nature – it’s CMS (Content Management System) which contains an advanced DMS (Document Management System), ie workflow system. And to be quite so precise, the possibility SharePoint’a, as CMS is in its infancy, but with the objectives of the organization and collaboration capabilities file archive repository, it copes fine.

SharePoint – Web-based platform for collaboration and document management system developed and marketed by Microsoft. This solution can be used to create a corporate Web portal that hosts the shared documents or specialized applications, such as wikis or blogs. The data in SharePoint are organized as lists (eg, tasks, discussions, calendars) and document libraries. SharePoint functionality presented to the user through Web Parts – Controls, featuring lists and allowing you to edit them. These web parts are placed on pages, which, in turn, placed on the portal and accessible to the user through a browser. In fact, SharePoint is an application ASP.NET 2.0, IIS uses to display web pages and SQL Server for data storage.

Most often, the solution based on MOSS (Microsoft Office SharePoint Server) are used for corporate intranet portals, designed to facilitate collaboration among employees within an enterprise. But the application SharePoint’a not limited to intranet, now you can find many sites on the Internet is based on MOSS (links to many Web sites on SharePoint can be found here http://www.wssdemo.com/Pages/websites.aspx). I also recommend a look at the page http://classic.utopiasystems.com/spdemo.html – is a small demo website where you can use the admin panel, upload documents, customize Web desks, etc.

Before we proceed directly to the testing, I recommend at least cursorily familiar with MOSS 2007 Evalution Guide. Here you will find all the key concepts, as well as several SW Casey, who will assist you in further work.

Also, if you have any questions, I recommend to use the Site http://office.microsoft.com/en-us/sharepointserver/default.aspx

All the below will write a fully valid for Microsoft Office SharePoint Server 2007 (MOSS 2007). Also, all write a below is not the ultimate truth, but merely represents my views on how and what is tested in solutions based on MOSS 2007.  

Site Columns

That check. Checking Columns are in the gallery of Site Column Gallery. If your project a few Site Collection, each of which uses its own column, then they should be checked for each site collection (ie Rutaceae site each site collection).

Where to find it. Site Actions -> Site Settings -> Modify All Site Settings -> Site Columns (either by URL / _layouts / mngfield.aspx);

What to look for.

  • Column Name
  • Column Type – determines the type of data that can be stored in a column, eg, text, date and time, numeric type, etc.
  • Group – in terms of functionality or has no effect, but, placing all columns in the Custom odnnoy group (or several logically separated groups) will greatly facilitate the work of not only you but also for developers, as well as future users your application.
  • Additional Column Settings – determine the properties of the column depending on the type of data, for example, the column of type choice here can be set which will contain the column value is selected by default, etc.

What not to do

  • Do not check the standard columns, ie those who are not at deploymente your application, and are on the site after creating the site collection.
  • Do not put the speakers in the libraries, because they may differ from those found in the gallery, since they can be changed independently of the columns in the gallery.

Site Content Types 

That check. Check the content taips (Content Types) are in the gallery content Typo (Site Content Type Gallery). If your project a few site collections (Site Collection), each of which uses its own content Taipa, they must check for each site collection (ie Rutaceae site each site collection).

Where to find it. Site Actions -> Site Setings -> Modify All Site Settings -> Site Content Types (either by URL / _layouts / mngctype.aspx).

What to look for.

  • Name, description, and group – a functional data set on what not affected, but as in the case of speakers, it is desirable that all Custom kontentaypy were in one group. Another point which could ease a little work – is the prefix names Custom kontentaypov (eg ‘CT Article Page’ or ‘Project_Name Article Page’ instead of ‘Article Page’).
  • Columns – define what metadata may include content in Taipa. Column, actually determine the appointment kontentaypa. Also, pay attention to any of these speakers kontentaypov inherited, it is desirable that all the columns either had no parents, or were the heirs of the standard kontentaypov because then it will avoid problems when upgrading kontentaypov.
  • Column Order – functionally or has no effect, but that’s nice when everything looks beautiful.
    Workflows – workflows can not be used in your project, so check them only when needed.

What not to do.

  • Do not check the standard kontentaypy, ie those who are not at deploymente your application, and are on the site after creating the site collection.
  • Do not check kontentaypy in libraries, because they may differ from those found in the gallery, since they can be changed independently of the columns in the gallery.

Libraries and Lists

What to check. Check the settings of libraries and lists to be used in your application for storing documents and information displayed on the web desks (Web Parts), images, etc.

Where to find it. Site Actions -> View All Site Content -> <Library_Name/List_Name> -> Settings -> Document Library Settings / List Settings

What to look for.

  • Title, description and navigation – a name and description of functional no matter what do not affect the navigation settings determine whether the visible library or list to navigate the site (Current Navigation / Quick Launch).
  • Versioning settings. These settings determine how they will be working with documents: whether to use moderation of the upload process (Content Approval), whether the available editions of the creation of a document (Document Version History), and if the creation of editions available, will the available rough draft (Minor Versions / Draft Versions) or just the basic edition (Major Versions / Published Versions). In the same section defines who will have the right to view the rough draft (Draft Item Security), and includes the need to do Check Out when you edit a document (Check Out prevents simultaneous editing of documents).
  • Advanced Settings – will determine whether the documents the library included in the search results (Search), whether available to create new folders in the library (Folders), whether to open documents in a browser or client application (Browser-enabled Documents), allow you to add additional URL in the menu Send To (Custom Send To Destination), provide an opportunity to define a template document created when you click New (Document Template), also, here is an option to enable or disable content management Typo (Content Types).
  • Audience targeting settings – to enable or disable the target document from a library.
  • Permissions for this document library. To check these settings only if the right of access to a particular list or library must be unique. In general, these rights derive from rights of access to the site on which the library is located.
  • Information management policy settings. Check only if they are used in your project.
    Content Types. Make sure that all necessary kontentaypy added to the library. Check out some of kontentaypov set as the default and the order in which they are displayed when you click New. By default, the Content Types section may not be available in this case turn on the check Typo content management with the option ‘Allow management of content types?’ under Advanced Settings.
  • Views. Check only if your application creates a custom display methods.

Pay full attention to versioning settings, advanced settings and targeting options, because they are directly linked to workflow, job search and display Web content library desks.

Note that among libraries, library alone is worth Pages. All pages are stored only in the library. Despite the fact that the content taips pages can be added to any of the libraries to create the page itself it will be placed in the Library Pages. Should not be stored in the library any documents.

One of the known problems existing in the current version SharePoint’a – the inability to have multiple Pages Library on one site (ie, to create what they can, but that’s put into them from the page can not be)

What not to do.

Do not check the lists and libraries that will not be further used by your application.

Page Layouts and Design

What to check. Check that the page templates (Page Layouts) contain all the necessary controls and appropriate design.

Where to find it. Do not forget that each of the page templates corresponds to only one content Taipei (eg, Artcile Page with image on left can be used only with the content Typo Article Page, because only in this case, the page will display correctly). Therefore, to test the page templates you need to add all the content pages in the library taips Pages. If the necessary page templates available by default on a site where you are going to test, then you can add them here Site Actions -> Site Setings -> Modify All Site Settings -> Page layouts and site templates here (or URL _Layouts / AreaTemplateSettings.aspx) .

What to look for.

  • Check the pages in normal mode and in edit mode.
  • Make sure that all necessary controls are available and are in place.
  • Make sure that all the necessary web partner area available and are in place.
  • Insert the page number of the web lots more width (you can set the width of the fixing of the properties of the Web Party) and check the page looks like in this case.
  • Typically, projects in SharePoint – it is IE only projects, but even in that case you can not avoid checking in different browsers, or rather different versions of the same browser :-) (how to use multiple versions of IE on one PC is available here http:// iqa.com.ua / soft / tools / multiple_ie here http://iqa.com.ua/soft/tools/ie8_standalone).

What not to do.

  • Do not check the standard page templates, if they are not used in your project.
  • Do not carp at the design system pages. Their design may differ from page templates, but still they are only intended for administrators / content managers, and, perhaps, in the absence of special requirements of small discrepancies with the design can be ignored. In my opinion this is the case when the time saved is worth more than nepofiksheny bug.  

Site Templates  

What to check. Check the website development based on templates (Site Templates), check that your templates are configured correctly.

Where to find it. If necessary site templates available by default on a site where you are going to test, then you can add them here Site Actions -> Site Setings -> Modify All Site Settings -> Page layouts and site templates here (or URL _Layouts / AreaTemplateSettings.aspx). Do not forget to add a site page templates that are used by your site templates.

What to look for.

  • Make sure that after creating the site it has all the necessary libraries and lists the relevant settings.
  • Check that the libraries are all necessary pages and documents
  • If your application uses design as a theme, make sure that the appropriate theme chosen for the site (Site Actions -> Site Setings -> Modify All Site Settings -> Page layouts and site theme or URL _layouts / themeweb.aspx)

What not to do.

Do not check the standard site templates, if they are not used in your project.

Navigation

What to check. Check the settings are correct navigation on Web sites created by deploymente application.

Where to find it. Site Actions -> Site Setings -> Modify All Site Settings -> Navigation (or URL _layouts / AreaNavigationSettings.aspx)  

Web Parts

That check. Validates the settings partov Web (Web Parts), which are on the pages after deploymenta applications, as well as functional Custom Web of desk that can be added and configured by users.

Since the Web party can be a huge set and they can be very different in functionality, the general recommendations for testing to be difficult. Sufficiently comprehensive check list for testing web part can be found here http://msdn.microsoft.com/en-us/library/ms916830.aspx

Take a test web party as much time as precisely because they realized most of the functionality.

What to look for.

  • If possible, test the Web desk with a large number of test data.
  • If your project uses the target, then necessarily proeryayte Web desk with documents intended for different groups.
  • If your project contains a web desks, display documents which depends on the fields of type Date Time, be sure to check whether the data updated in the web desks when the alarm time. When making such a test does not perform any action on the site – just refresh the page.
  • If your project has a web of parties which are required to collect data from multiple collections sai, then check them by placing the test data on all the available site collections in your application.

What not to do.

Do not test standard web desk, unless they are placed on the site with deploymente vashgo application.

Permissions

What to check. Checking application functionality by working with user accounts with different access rights.

Where to find it. All necessary configuration of access rights can be found here Site Actions -> Site Setings -> Modify All Site Settings -> People and Groups (or URL _layouts / people.aspx).

What to look for.

  • Inspect the entire standard funktsonal, which by default can not be used by users with limited privileges, but your application is available for them (like adding pages the users of a group of Visitors).
  • To check whether the styles and images are displayed for users with limited privileges (for example, if an image that is part of the design does not have a main trunk, it will not be shown to the user from the group Visitors).
  • Inspect all non-standard functionality using accounts with different access rights.

Search

What to check. Check the search user profiles and content.

Where to find it. When testing the search, you will need to access SharePoint Central Administration, and more precisely to the Shared Services. Here, you will need a user profile (User Profiles) and control crawling (Crawling).

What to look for.

  • Testing the search do not forget to crawl after any changes to the content or profiles polzovateley.Prakticheski all changes to the site should become available after an incremental crawl (Incremental Crawl)
  • Note that in our search results may include only documents with the head revision
  • Check the search using key words and phrases containing punctuation marks and special characters (?,$,%,&, etc.)
  • Check the search for establishing various preferential localization of web pages in the browser (I know that sounds crazy, but try, maybe one fine day you change your mind)

Perhaps the search – one of the most mysterious parts of MOSS2007. For example, I still do not know one person who could fully understand how it works. I hope that these people have at least a Microsoft …

Integration

What to check. Check the integration of applications MS Office.

What to look for.

  • Check that all fields Custom content Typo can be filled out applications MS Office.
  • If your users will use Office Communicator, please check that the status is displayed correctly and in the right places.

Solution Deployment

What to check. Check the application deployment on a clean server, and deployment of patches (valid only if your application is delivered as a deployment package, not deploitsya manually or razmozhaetsya backup). Such testing is especially important if your company will no longer be providing a support.

To test deploymenta you need access to a server running Windows 2003 and MOSS2007.

What to look for.

  • Periodically to produce a clean deployment server to make sure that all changes made to the application had been made to solyushen and hit the deployment package.
  • Install patches on a server that already contains the test data, and then check the "integrity" of content.

Post Scriptum 

At this time, perhaps, all … Of course, this improvised How To is not exhaustive and you are in the process must still find a lot of things that are not described here. For symmetry let’s bow and wish everyone good luck in SharePoint development.

See Also

    Advertising

    Archives