Project Creation

Projects store all of the information related your project within Enterprise Tester, an unlimited number of projects can be created in Enterprise Tester and these can be grouped by using the Project Category function. 

When any project is added there are four folders created, the folder name will differ depending on the template chosen:

Enterprise Tester Folder Description
Requirements, User StoriesCaptures requirements or user stories that need to be tested.
Test Script Libraries,Test CasesA library of all test cases that can be built up, providing step by step instructions on how to conduct the tests.
Test Execution SetsAn area to organize the execution of testing into cycles or iterations of tests.
IncidentsLogged incidents created during testing. These may take the form of bugs, or requests such as new requirements, improvements or enhancements to the system.


Once a project is created,  project information is accessed via the Explorer tab.


To create a project:

 

  • Open the Admin tab of the tree view and expand out until you can see the projects folder.

  • Right click on the project folder and select Add Project from the menu. The New Project Wizard will appear.

 

 

 

 

  • Enter a name for your project. 


  • Select the Project Type:
    Project - creates a standard Enterprise Tester project that can be 
    Master - creates a Master Project where users can create Reusable Test Steps.  Reusable Test Steps can be referenced by standard Test Cases.

 

 

  • If you have chosen Project Type of Project then select a Project Template, the following templates are available:
    • Default - This template is the Enterprise Tester standard project set up using the organisation picklist values. 
      The project structure is as follows:

    • Agile - This template provides an agile project set up option. The project structure is as follows:

 

  The Agile project template also adds the number custom field, Story Points to User Stories and has the following set of picklist values:

 

FieldPicklist Values
Incident ResolutionDuplicateCannot ReproduceWon't FixFixedIncomplete
Incident StatusOpenIn ProgressResolvedClosedReopened
Incident TypeBugNew Feature Task   
PriorityBlockerCriticalMajorMinorTrivial
Requirement DifficultyHighMediumLow  
Requirement StatusIn ProgressReviewPendingApproved 
Requirement TypeUser StoryTaskEpic  
StatusIn ProgressReview PendingApproved  
Test TypeSmokeFunctionalRegressionNon-functionalUser Acceptance




    • Cascade - This template provides a hybrid option of classical and agile project set up. 
      The project structure is as follows:

 

 The Cascade project template has the following set of picklist values:


FieldPicklist Values
Incident ResolutionDuplicateCannot ReproduceWon't FixFixedIncomplete 
Incident StatusOpenIn ProgressResolvedClosedReopened 
Incident TypeBugNew FeatureTaskImprovement  
PriorityBlockerCriticalMajorMinorTrivial 
Requirement DifficultyHighMediumLow   
Requirement StatusIn ProgressReview PendingApprovedRequires ReworkRejectedOn Hold
Requirement TypeUser StoryTaskEpicFunctionalNon FunctionalUser Interface
StatusIn ProgressReview PendingApprovedRequires ReworkRejectedOn Hold
Test TypeSmokeFunctionalRegressionNon-functionalUser Acceptance

 

  • Click save to open the Add Project screen.

  • Complete the project details:

FieldDescription
OrganizationSelect from the pick list of Organizations you have defined.
NameA name that identifies the project.
Original TypeEnter a name that identifies the type of project.
Project ManagerSelect the Project Manager from the pick list of users.
Default Incident AssigneeSelect the default incident assignee if you only want one user to be assigned incidents.
Project TypeWill be populated based on the Project Type that was chosen during project creation.
Picklist ValuesInherit from Organization:Inherit your picklist values (inbuilt and custom fields) from the organization picklist.Only for this Project:Have an independent set of picklist values for your inbuilt fields, only for your project.
Auto-numberYou can select auto-numbering of requirements and/or scripts.
Read only numbersYou can configure the requirement and/or script number fields to be read only.
Start DateThe start date of the project.
End Date EstimateThe end date of the project.
DescriptionThe project description.

 

  • Click on Save to create the project.

 

 

Assigning Users to Projects

Users must be assigned to projects and can only access projects where they have been assigned; user access is also limited by associated permissions.

User permissions are typically set at the application level and should only require project specific permissions to elevate their permission level.

 

You can assign users to the project in the Assign Users tab of the project:

  1. Open the project by right clicking and selecting Edit Project or by double clicking the project.
  2. Select the Assign Users tab.
  3. You can then add users by simply typing in the user name and selected from the filtered results or by using the drop down and selecting the user.

 

Assign User Groups to a Project

Groups of users can be assigned to projects and project permission can then be assigned to the group.

Group permissions at the application level will take precedence.

You can assign groups to projects similarly to adding users, directly to projects.

 

Time Tracking

You can also set the time to be used for tracking progress for a project by selecting the Time Tracking tab.

Here you can select:

Working Hours Per Day The number of hours in a working day (1 - 24).
Working Days Per Week The number of days in a working week (1 - 7).

 

Version Control

You can add the following version control details for a project:

  1. Type the type of version control application you are using (selected from a supported list).
  2. Repository Url the url path for the version control repository you are configuring.
  3. Working Copy Path the working copy path for the version control repository you are configuring.
  4. Username a gateway user to access the repository.
  5. Password the password for the gateway user used to access the repository.
  6. Executable Path the path to the executable for the version control application.
  7. Additional Arguments any additional arguments required for the repository executable.

Note that you can choose to inherit Version Control from the organization. If you share version control repositories across Projects this enables you to define the connection once.