Set up the test environment for Project Server 2013
Applies to: Project Server 2013
Topic Last Modified: 2013-12-18
Summary: Learn about configuration and metrics involved in setting up a Project Server 2013 test environment.
In addition to the servers composing the Project Server 2013 farm and the needed infrastructure services such as domain controllers, you should set up a Visual Studio Team System 2008 Test Edition controller agent topology. For more information about Visual Studio Team System 2008 Test Edition, see Controllers, Agents, and Rigs in the MSDN Library Online. We strongly recommend that you use dedicated hardware for the controller, the agent(s), and the database that stores test results in order to minimize the effect on systems being tested.
Similarly, in order to test operations involving Project Professional, you should set up a test infrastructure that can automate client operations across multiple Terminal Services sessions and control test scenarios in a centralized manner. An example of such a test solution is the community-based project named Test Framework, which is available at Project 2010 Thick Client Test Framework (http://go.microsoft.com/fwlink/p/?LinkId=190449).
Directly after the setup is complete in your test environment, we recommend that you perform a full backup. Save the backup set so that you will always be able to revert to the baseline state if it is necessary.
When your Project Server 2013 farm is up and running, you can start to generate the data profiles that you planned for. A tool that you can use to help in this process is the community-based solution called EPM 2010 Test Data Population Tool, which is available at Project Server 2010 Test Data Population Tool (http://go.microsoft.com/fwlink/p/?LinkID=190449) and currently applicable to Project Server 2013.
After you generate one specific data profile, perform a full backup of the Project Server databases (and the SharePoint Server content database if you include Project Workspaces in your test scenarios). Then save the backup set so that it will be available for recovery every time that you need to start a test run with that data profile. It's important that every time that you start a new test run you perform a recovery of the backup set that contains the appropriate data profile. By doing this you can ensure the same initial conditions of multiple test runs for the same scenario.
Load tests must impersonate several different users in order to provide the most accurate simulation of reality. This can be achieved by using the data binding feature in Visual Studio Team System 2008 Test Edition so that every test instance will randomly select one user from the whole list. The same approach can be taken for binding other data to your coded tests, such as for example project names, resource UIDs, and so on.
The "Data Population Tool," "Thick Client Test Framework," and "PWA Web Tests" tools are part of the Microsoft Project 2010: Project Server Stress Testing Toolkit (http://go.microsoft.com/fwlink/p/?LinkID=190449), which can be downloaded from the MSDN Code Gallery. This toolkit provides samples that can be used to enumerate all the resources from the Enterprise Resource Pool and to generate XML files that contain key information that will be made available to the tests.
|Tools available for Project Server 2010 are still applicable to Project Server 2013.|
Run a Project Server 2013 performance test lab
Plan a Project Server 2013 performance test lab
Key performance metrics for Project Server 2013
Test user-initiated write operations that involve Project Server 2013
Test user-initiated operations that involve Project Professional 2013
Test background operations in Project Server 2013
Extract and analyze test data in Project Server 2013