Configurer l’environnement d’intégration (Office SharePoint Server)
Mise à jour : 2007-12-20
This section provides information about setting up the servers in your integration environment for testing coded elements for Microsoft Office SharePoint Server 2007. This information is for a multiple-computer farm environment, using Windows Server 2003, Office SharePoint Server 2007, and Microsoft SQL Server 2005.
The integration environment is where testers ensure that site elements created in the development environment function together as expected. For more information about this environment, see Examen des environnements.
.gif "Note") Remarque : |
|---|
You may need to troubleshoot your components and applications in the test environment, which might not have a source-level debugger like Visual Studio. To prepare for this, you should produce a program database (.pdb) file along with your coded elements, and enable logging, tracing, and other instrumentation options. For more information, see PDB Files (https://go.microsoft.com/fwlink/?LinkId=106290&clcid=0x409). |
Hardware and software requirements
Because your integration environment is not typically used for performance, reliability, scalability, or fail-over testing, the computer on which you run Office SharePoint Server 2007 and the other software does not need to be as robust as your production environment. For more information about system requirements, see Déterminer la configuration matérielle et logicielle requise (Office SharePoint Server).
Installing Office SharePoint Server 2007 and other software
You will need to install a Office SharePoint Server 2007 farm with all of the components or features that you developed coded elements for. Typically, the integration farm consists of at least two front-end Web servers, one or more application server, and one database server. For more information about creating a Office SharePoint Server 2007 farm, seeDéployer Office SharePoint Server 2007 dans un environnement de batterie de serveurs.
| Remarque : |
|---|
After you have finished installing Office SharePoint Server 2007, you should install the latest software updates. |
Importing test data
Some coded elements require existing data to test them, such as a search-related element or a Web part that retrieves information from Active Directory active directory. You can use the restore feature of Office SharePoint Server 2007 to import test data to the integration environment. For more information, see How to: Deploy Content Between Servers (https://go.microsoft.com/fwlink/?LinkId=106221&clcid=0x409).
Overview of testing
For more in formation about testing using Visual Studio 2005 Team System, see Development and Testing (https://go.microsoft.com/fwlink/?LinkID=106298&clcid=0x409) or Test Types (https://go.microsoft.com/fwlink/?LinkId=106300&clcid=0x409). For more in formation about testing using Visual Studio 2008 Team System, see Building, Debugging, and Testing (https://go.microsoft.com/fwlink/?LinkId=106494&clcid=0x409).
The following table shows some of the most common test types performed in the integration environment, with a description of each test and an example of the test on an in-house developed files property control that enumerates files in various folders and displays various properties for these files in a list control.
| Test type | Description | Example |
|---|---|---|
Functional |
Ensures that the element functions as specified. This can also include database and application server connectivity aspects not involving security. |
Checking that the drop-list populates correctly and that the chosen value persists. |
Usability and Access |
Ensures that the user sees and can use the element as expected. This might also include testing on third-party browsers. Ensure that the people with vision, hearing, or mobility issues can use the features. |
Ensuring that the control appears correctly under various page size conditions and that users can use the control in third-party browsers (if applicable). For more information about Office SharePoint Server 2007 browser compatibility, see Planifier la prise en charge des navigateurs (Office SharePoint Server). |
Security |
Ensures that the element can be accessed as expected and that the user can perform all tasks as designed and only those tasks. Involves testing of Single Sign-On capabilities and any user interface trimming. Involves user input testing; authentication and authorization testing; and testing against security issues like cross-side scripting, buffer overflows, and denial of service attacks. |
Ensuring that users can log on to the page, that they can use the control to view file properties from a specific store, and that they cannot view file properties from stores to which they are not designed to have access. For more information about Office SharePoint Server 2007 security, see Planifier et concevoir la sécurité (Office SharePoint Server). |
Error Handling |
Ensures that the element raises appropriate error messages and exceptions. Ensure that any .pdb files are correct for the deployed element and that the element can be successfully analyzed and a resolution found. |
Ensuring that the .pdb files for the control generate the correct information during a failure-injection test. Ensuring that proper error messages are returned when improper data is entered. |
Manageability |
Ensure that the element or page sends the correct events and/or writes the correct entries to any specified logs. |
Ensuring that the control generates the correct events during a failure-injection test. |
International and Multi-Lingual |
Ensure that Web pages and controls that allow user input can display and process international characters correctly. |
Considering such issues as whether the Web page or control truncates text that is too long, or that sorting orders for characters can differ depending upon language. |
Download this book
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable books for Office SharePoint Server 2007.