The Administrator allows the system administrator to manage users, roles, projects, and fields.
The Administrator allows you to create user accounts, assign them user names and passwords, and assign the type of access that they have in Oracle Test Manager. The Administrator allows you to manage users, roles, projects, and fields.
Two default administrator accounts are created at installation. The usernames for the default accounts are administrator and default. The default password for both the administrator and default accounts is the master password specified during the Oracle Application Testing Suite installation process. You can change the password after logging in to the Administrator. It is recommended that you change the default password as soon as you log in.
To start the Administrator:
For Windows installations, select Administrator from the Oracle Application Testing Suite Start menu or enter http://<machine>:8088/admin or http://localhost:8088/admin in your browser where <machine> is the name of the machine where the Oracle Application Testing Suite is installed.
For Linux installations, enter http://<machine>:8088/admin or http://localhost:8088/admin in your browser where <machine> is the name of the machine where the Oracle Application Testing Suite is installed.
Enter your password.
Select the Oracle Test Manager database that you want to access.
If this is the first time you are logging in, change the administrator password by clicking the User tab, selecting the Administrator user, and clicking Edit.
Enter the new password, verify it, and click OK.
The Administrator consists of tabs for configuring users, roles, projects, and customizing both custom and default fields.
The Users tab is where you add, delete, and configure users and their roles in projects. Roles determine the permissions the user has in each project. The users are displayed at the top of the screen and the roles for the selected user are displayed on the bottom of the screen.
This tab has the following options:
Add - displays the Add User dialog box for adding a new user.
Edit - displays the Edit User dialog box for the selected user. You can change the user's name, username, or password.
Assign - Displays the Edit Role dialog box for assigning roles to the selected user for the selected projects.
Delete - deletes the selected user.
Sync LDAP Users - synchronizes users with the LDAP server. Use this option to keep Oracle Test Manager authentication in sync with the LDAP server updates. This option is only used when using LDAP authentication.
Restore - displays the Restore Previously Deleted User dialog box for restoring a previously deleted user to the users list.
Username - displays the name the user will use to log on. Click the column header to sort users in ascending order by this field.
LDAP Username - displays the Lightweight Directory Access Protocol (LDAP) server authentication name the user will use to log into Oracle Test Manager if LDAP Server authentication is configured. Click the column header to sort users in ascending order by this field.
First Name - displays the user's first name. Click the column header to sort users in ascending order by this field.
Last Name - displays the user's last name. Click the column header to sort users in ascending order by this field.
E-mail - displays the user's email address. When Enable E-mail notification is selected for the user, the user will receive email notifications when items are created, or when the owner or assigned to field is changed for issues. Click the column header to sort users in ascending order by this field.
E-mail Notify - indicates whether the user will receive email notifications. Click the column header to sort users in ascending order by this field.
Administrator Access - indicates whether the user can access the Oracle Test Manager Administrator.
Assignments for <user> - displays the roles assigned to the selected user for each project in the database.
Project - displays a list of the projects in the database.
Role - displays the role of the selected user for the project.
The Roles tab is where you configure roles. Roles determine the read, write, delete, and execute permissions for users in projects. Once roles are created, you assign them to users for each project that you want them to have access to. A user's role can differ from project to project. Click Assign on either the Projects tab or Users tab to assign roles.
Add - displays the Add Role dialog box for adding a role.
Edit - displays the Edit Role dialog box for editing the selected role.
Delete - deletes the selected role. If a role is in use, you will be asked to assign another role to users assigned to this role.
Permissions for <role> - displays the read, write, delete, and execute permissions for this role for projects, test plans, requirements, tests, and issues.
Project - displays the read, write, and delete permissions for projects for users assigned to this role.
Test Plan - displays the read, write, and delete permissions for test plans for users assigned to this role.
Requirement- displays the read, write, and delete permissions for requirements for users assigned to this role.
Test - displays the read, write, delete, and execute permissions for tests for users assigned to this role.
Issue - displays the read, write, and delete permissions for issues for users assigned to this role.
Public Reports - displays the read, write, and delete permissions for public reports assigned to this role.
My Reports - displays the read, write, and delete permissions for reports assigned to this role.
The Projects tab is where you maintain projects.
Add- displays the Add Project dialog box for adding a new project.
Clone - displays the Clone Project dialog box for duplicating the selected project. When you clone a project, user roles are the same as the original project.
Edit - displays the Edit Project dialog box for changing the name of the selected project.
Assign - displays the Edit Role dialog box for assigning roles to users for the selected project(s).
Map LDAP - displays the LDAP Group Mapping Details dialog box for mapping LDAP Groups to Oracle Test Manager Projects and Roles.
Delete - deletes the selected project.
[project list] - displays a list of projects in the database.
Project - displays a list of projects in the database.
Track History - displays if history tracking is enabled or not for the project. See Section 11.9.1, "Adding Projects" for additional information.
Assignments for [selected project] - shows the users and role assignments for the project selected in the project list.
User - displays the users in the database.
First Name - displays the user's first name.
Last Name - displays the user's last name.
Role - displays the users' roles in the project.
All Mapped LDAP Groups - shows the selected LDAP Groups, projects, and roles for the project selected in the project list. See Section 11.5.5, "Mapping LDAP Groups to Oracle Test Manager Projects and Roles" for additional information.
The Fields tab is where you customize both default and custom fields. These fields are used in Oracle Test Manager for maintaining details about requirements, tests, test sets, issues, and test runs.
This tab has the following options:
<Field List> - lists the categories and types of fields that you can customize. The categories are:
Test Plans - fields that pertain to test plans that appear in the Add/Edit Test Plans dialog boxes and are displayed in the right pane.
Requirements - fields that pertain to requirements that appear in the Add/Edit Requirements dialog boxes and are displayed in the right pane.
Tests - fields that pertain to tests that appear in the Add/Edit Tests dialog boxes and are displayed in the right pane.
Test Sets - fields that pertain to tests that appear in the Add/Edit Test Execution dialog boxes and are displayed in the right pane.
Issues - fields that pertain to issues that appear in the Add/Edit Issues dialog boxes and are displayed in the right pane.
Test Runs - fields that pertain to test runs that appear in the Run Test dialog box and are displayed in the Result Parameters section of the right pane when you click the run date of a test in the Run History section.
Each category has two types of fields:
Default Fields - these are the fields that are shipped with the product. You can add and delete options and change the labels.
Custom Fields - these are user-created fields. These fields are used for entering information in Oracle Test Manager. They are added to the input and edit dialog boxes for requirements, tests, and issues. They are displayed in the right pane with the default fields, and they can be used for grouping and reporting.
Name - displays the field name.
Label - displays the label displayed in Oracle Test Manager.
Type - displays the type of field. The options are:
Option List - lets you select an option from a list.
Option List/Text - lets you select an option from a list or enter text.
User List - creates a list of the users in the database and lets you select one.
Text - lets you enter one line of text.
Multiline Text - lets you enter multiple lines of text.
Multiline/Append - creates a multiline text field and when editing, lets you choose to append new text to existing text. If you choose to append, the date and user name are automatically added.
Heading - lets you create a heading for grouping custom fields. The heading is for display purposes only in the right-hand pane of Oracle Test Manager.
Trigger Email Notification - indicates whether an email will be sent to the configured recipients when this field changes. Click the pencil icon to display the Setup E-mail Configuration dialog box for configuring email recipients. The logged in user should not be the same as the username that is specified for the trigger. The trigger checks the email address of the user who changes the field and does not send notification to any users with the same email address.
Include In Email - indicates whether the field should be included in email.
Required - indicates whether the field is required, that is, data must be entered when the requirement, test, or issue is created.
Enabled - indicates whether the field is being used in Oracle Test Manager.
Project - indicates the project to which this field applies.
Add - displays the Add Field dialog box for adding a custom field.
Edit - displays the Edit Field dialog box for the selected custom field.
Delete - deletes the selected custom field.
Move Up - moves the selected field up one place.
Move Down - moves the selected field down one place.
Option List - lets you maintain the options for the selected field if the field is an option list type of field.
Add - displays the Add Option dialog box for adding an option to the selected field.
Edit - displays the Edit Option dialog box for renaming the selected option.
Delete - deletes the selected option.
Move Up - moves the selected option up one place.
Move Down - moves the selected option down one place.
Project - lets you select the project to which the options apply. This field is only available when you select the Project Specific Options check box in the Add Custom field dialog box for this field. When this check box is selected you can add options specific to each project; otherwise, all projects will have the same options.
Email Recipients - lists the roles and/or email addresses of the people that will receive an email when the selected field changes.
Project - select the project for which you want to display the email recipients.
MailIds - lists the email addresses to which email will be sent when the field changes.
Roles - lists the roles of the email recipients to which email will be sent when the field changes.
When you select the category in the left pane, the associated fields are displayed in the top right pane. When you select the field in the top right pane, its associated options are displayed in the Option List.
The Usage Audit tab is where you review and audit the load testing sessions stored in the Oracle Load Testing database.
This tab has the following options:
OLT Databases - lists the installed Oracle Load Testing Databases available for auditing.
User Name - shows the name of the user who ran the load test. "Anonymous" indicates the login feature was disabled for the instance of Oracle Load Testing that ran the test and there is no username associated with the test. "Command Line" indicates the load test ran from the command line interface.
Session Name - shows the name of the load testing session.
Start Time - shows the start date and time for the load testing session.
End Time - shows the end date and time of the load testing session.
Duration (HH:MM:SS) - shows the duration of the load testing session in hours, minutes, and seconds.
Machine Name - shows the name of the machine on which the load testing session was run.
Max VU Count - shows the maximum count of Virtual Users that were run for the load testing session.
The menus provide options for saving changes to the database and for accessing the database maintenance tools.
The Tools menu lets you purge the database, unlock locked records, set up the LDAP and e-mail configurations, and manage default reports.
Unlock Locked Records - unlocks locked records in the database. This is an emergency feature to be used to clear out locks in the database when the product fails and leaves entries locked for editing.
Purge Deleted Records - physically removes all deleted data from the database. Deleted items are marked as such and are not shown in the user interface; however, they are kept in the database until the database is purged.
Setup E-mail Config - displays the Setup E-mail Configuration dialog box for configuring the mail server to use for e-mail notifications.
Setup LDAP Config - displays the Setup LDAP Server Configuration dialog box for configuring the LDAP server to use for user log-in authentication.
Manage Default Reports - displays the Manage Default Reports dialog box for selected which default reports will be visible to individual users.
You can set up individual users so that they receive email notification when a new requirement, test, or issue is created, or when the owner or assigned to field is changed for an issue. In addition, you can configure emails to be sent to the owner and creator when certain conditions occur. For this to work, the email server must be configured.
To configure the email server and email preferences:
Select Setup E-mail Config from the Tools menu.
Click Configure SMTP Settings.
This dialog box has the following options:
SMTP Server - enter the server name, and optionally a colon (:) followed by a port number. The default port number is 25.
Return Address - enter the return address for email sent by Oracle Test Manager.
Send To - enter the email address to which you want to send a test e mail when you click the Test button.
Test - displays the Test E-mail Configuration dialog box for testing your configuration.
Enter the SMTP Server name.
Enter the return address for emails sent by Oracle Test Manager.
Enter the email address to which you want to send the test email.
Click Test to test the configuration.
Click Traceability to select options for when to send email.
Notify creator of changes - sends an email to the node creator when the owner changes. Email is not sent if the node creator becomes the current owner or if the node creator initiated the activity.
Notify Owner of associated test(s) when a requirement changes - when a requirement changes, sends an email to the owner of tests associated with this requirement.
Notify Owner of associated issue(s) when a test runs - when a test runs, sends an email to the owner of issues associated with this test.
Select when you want to send email.
Click Save.
You can implement Lightweight Directory Access Protocol (LDAP) server authentication to allow Oracle Test Manager users authentication against the LDAP server providing users a single sign-on solution. This section provides instructions for implementing LDAP user authentication for Oracle Test Manager.
Implementing LDAP user authentication for Oracle Test Manager has the following prerequisites:
An LDAP server is step up with users and groups.
You have the LDAP server configuration information necessary to configure the server in the Oracle Application Testing Suite Administrator. The following information is required to set up the LDAP sever configuration:
LDAP Host - specifies the host name of the LDAP Server.
Port - specifies the port number to use for the LDAP server.
Option Values - specifies the base LDAP server group option, as follows:
Base DN - specifies the base distinguish name (for example, dc=maxcrc,dc=com).
Security - specifies the LDAP server authentication information, as follows:
Level - specifies the LDAP security level: ssl=SSL+User+Password and simple=User+Password.
User DN - specifies the user distinguish name.
Password - specifies the user password for authentication to the LDAP server.
Activate LDAP User Authentication - when selected, LDAP user authentication for Oracle Test Manager login is enabled and the local authentication is disabled for all users except the Administrator and Default user. Oracle Test Manager users must use a valid LDAP user name and password to log into Oracle Test Manager.
Note:
For OATS Administrators who have an existing base of Oracle Test Manager users with Oracle Test Manager login credentials currently being used, DO NOT enable LDAP User Authentication until after the time frame provided for users to specify their LDAP username in the Oracle Test Manager User Options.Group Attributes - specifies the group attibutes and search filter, as follows:
Attributes - specifies the name of the attribute(s) that Oracle Test Manager retrieves the group name from. If your server configuration uses more than one, include additional attributes separated by a semicolon (;). The default value is ou.
Search Filter - defines the filter to use when searching groups. The default value is (objectClass=organizationalUnit).
User Attributes - specifies the user attibutes, as follows:
User Name - defines the attributes of an LDAP entry that contains the username information. The default value is cn.
First Name - defines the attributes of an LDAP entry that contains the user first name information. The default value is givenName.
Last Name - defines the attributes of an LDAP entry that contains the user last name information. The default value is sn.
Mail - defines the attributes of an LDAP entry that contains the mail information. The default value is mail.
When connecting to LDAP over SSL, you must import the LDAP Server CA certificate.
When connecting to LDAP over SSL, you must import the LDAP Server CA certificate to cacerts, the certificate store, of the Oracle Test Manager server.
To import the LDAP Server CA certificate:
Obtain the LDAP Server CA certificate file from the LDAP server administrator and save it to a temporary location on the OATS server.
Enter the following command on the OATS server:
c:\OracleATS\jdk\jre\bin>keytool -import -trustcacerts -alias maxcrcCA -file c:\temp\maxcrc.pfx -keystore c:\oracleATS\jdk\jre\lib\security\cacerts -storepass changeit
where maxcrcCA is the certificate alias and maxcrc.der is the certificate file name.
Enter Yes at the prompt, Trust this certificate? [no]:.
Verify the certificate was added to keystore.
Once the certificate is imported successfully, restart 'Oracle ATS Server' service and connect to LDAP over SSL using the OATS Adminstrator.
This section provides an overview of the steps that should be followed to implement LDAP user authentication for Oracle Test Manager.
The following steps are for OATS Administrators who are installing the Oracle Application Testing Suite for the first time and want to implement LDAP authentication but do not have an existing base of Oracle Test Manager users.
An OATS Administrator sets up the LDAP server configuration in the Oracle Application Testing Suite Administrator and enables LDAP Authentication. See Specifying LDAP Properties and Setting Up an LDAP Server Configuration - New Users for additional information.
An OATS Administrator maps LDAP groups to Oracle Test Manager projects and roles in the Oracle Application Testing Suite Administrator. See Mapping LDAP Groups to Oracle Test Manager Projects and Roles for additional information.
An OATS Administrator notifies Oracle Test Manager users that LDAP Authentication is implemented and users should use their LDAP username and password to log into Oracle Test Manager.
The following steps are for OATS Administrators who have an existing base of Oracle Test Manager users with login credentials currently being used.
An OATS Administrator sets up the LDAP server configuration in the Oracle Application Testing Suite Administrator but DOES NOT enable LDAP Authentication yet. See Specifying LDAP Properties and Setting Up an LDAP Server Configuration - Upgrading Users for additional information.
An OATS Administrator maps LDAP groups to Oracle Test Manager projects and roles in the Oracle Application Testing Suite Administrator. See Mapping LDAP Groups to Oracle Test Manager Projects and Roles for additional information.
An OATS Administrator notifies existing Oracle Test Manager users that LDAP Authentication will be implemented and provides existing users with a time frame in which to add their LDAP username to Oracle Test Manager. The time frame can be any time frame decided by An OATS Administrator implementing LDAP authentication.
An OATS Administrator instructs existing Oracle Test Manager users to specify their LDAP username in the Oracle Test Manager User Options (Select Options from the Oracle Test Manager Tools menu and then select User Information. Enter the LDAP user name and click Save.) Users should continue to use their Oracle Test Manager username and password to log in to Oracle Test Manager until LDAP Authentication is enabled by an OATS Administrator for Oracle Test Manager.
After the specified notification time frame, an OATS Administrator enables LDAP Authentication in the Oracle Application Testing Suite Administrator. See Enabling LDAP User Authentication for additional information. Once LDAP Authentication is enabled, OATS Administrator notifies all existing Oracle Test Manager users to begin using their LDAP username and password to log into Oracle Test Manager.
The LDAP server configuration must be specified by an Oracle Test Manager administrator to define the LDAP server to use for user authentication.
To set up the LDAP server configuration for OATS Administrators of a new installation that does not have an existing base of Oracle Test Manager users:
Start the Oracle Application Testing Suite Administrator and log in with Administrator credentials.
Enter the LDAP Server name.
Enter the LDAP server port number.
Specify the LDAP Base DN (for example, dc=maxcrc,dc=com).
Specify the LDAP security level.
Specify the LDAP User DN (for example cn=manager,dc=maxcrc,dc=com).
Specify the LDAP User password.
Click OK.
The LDAP server configuration must be specified by an Oracle Test Manager administrator to define the LDAP server to use for user authentication.
To set up the LDAP server configuration for OATS Administrators who have an existing base of Oracle Test Manager users with Oracle Test Manager login credentials currently being used:
Start the Oracle Application Testing Suite Administrator and log in with Administrator credentials.
Enter the LDAP Server name.
Enter the LDAP server port number.
Specify the LDAP Base DN (for example, dc=maxcrc,dc=com).
Specify the LDAP security level.
Specify the LDAP User DN (for example cn=manager,dc=maxcrc,dc=com).
Specify the LDAP User password.
Note:
DO NOT enable LDAP User Authentication until after the time frame provided to users to specify their LDAP username in the Oracle Test Manager User Options.Click OK.
LDAP Groups must be mapped to Oracle Test Manager Projects and Roles to provide users with specific access rights within Oracle Test Manager.
To map LDAP groups to Oracle Test Manager Project and Roles:
Start the Oracle Application Testing Suite Administrator and log in with Administrator credentials.
Select the Projects tab.
Click Map LDAP. The LDAP Group Mapping Details dialog box has the following options:
All LDAP Groups - lists the LDAP groups available for the specified LDAP Server configuration.
Selected LDAP Groups - lists the LDAP groups selected from the All LDAP Groups list.
Project - specifies the Oracle Test Manager project to map to the selected LDAP Group.
Role - specifies the Oracle Test Manager user role to map to the selected LDAP Group.
Select the group name in the left pane.
Click the right arrow button (>) to add the group to the Selected LDAP Groups list.
Select the Project and Role to map to the group.
Repeat steps 4, 5, and 6 to add additional groups to the Selected LDAP Groups list and map the Project and Role to the group.
Click OK.
For OATS Administrators who have an existing base of Oracle Test Manager users with Oracle Test Manager login credentials currently being used, enable LDAP User Authentication after the specified notification time frame. An OATS Administrator activates LDAP Authentication in the Oracle Application Testing Suite Administrator.
To activate LDAP user authentication after a notification period:
OATS Administrators can use the Sync LDAP Users option to keep Oracle Test Manger users in sync with user changes to the LDAP server. The Sync LDAP Users option only applies if using LDAP authentication.
To synchronize LDAP Oracle Test Manager users with the LDAP server:
In the case of LDAP servers that have multiple CN entries under an LDAP group, you may need to configure group and user attributes in the Setup LDAP Configuration dialog box. For LDAP users, Oracle Test Manager retrieves username, first name, last name and mail from LDAP entries on the server when adding them to the Oracle Test Manager database. See Section 11.5.1, "Prerequisites" for additional information.
You can select the default reports that are available for each user on the Reports tab in Oracle Test Manager. To manage default reports:
Select Manage Default Reports from the Tools menu.
Users - lists the users. You can select more than one user using the Shift and Ctrl keys.
Check all - selects all reports.
Uncheck all - deselects all reports.
Visible - when checked, the report will be available to the selected user(s). When unchecked, the report will not be available to the selected user(s).
Reports - displays the report names.
Select the user(s) that you want configure reports for. Use the Shift and Ctrl keys to select more than one user.
Select the reports that you want to be available to the user(s) on the Reports tab in Oracle Test Manager.
Click Apply.
Click OK.
After you add a user you can then assign roles to the user for each project in the database.
To add users:
Click the Users tab.
Click Add. The Add User dialog box is displayed.
The Add user dialog box has the following options:
First Name - enter the user's first name.
Last Name - enter the user's last name.
E-mail - enter the user's email address for receiving email notifications.
Username - enter the username for logging on.
Password - enter the user's password.
Confirm Password - re-enter the user's password to confirm that it is correct.
Enable E-mail notification - select this option to enable email notification when new issues are created and when the owner or assigned to fields are changed for issues.
Enable Administrator Access - gives this user the ability to log on to the Administrator for managing the database.
Enter the user's first name.
Enter the user's last name.
Enter the username that the user will use to log in.
Enter the user's password.
Confirm the user's password.
Click OK. You can now edit the user's project permissions by selecting the project and clicking Edit.
To delete a user:
Click the Users tab.
Select the user you want to delete.
Click Delete.
Click Yes when asked to confirm.
You can restore a previously deleted user to the user list. To restore users:
Click Restore.
Enter the Username of the user to restore.
Click OK.
To change a user's name, login user name, password, or enable email notification:
Click the Users tab.
Select the user whose information you want to change and click Edit.
Make the necessary changes.
Click OK.
Roles determine the project permissions that each user has for a project. Project permissions determine what users can do within the project. Read, write, and delete permissions are assigned to the project, requirements, tests cases, and issues within each project. Execute permission is also assigned to test cases. To assign roles to one user for all projects:
Select the Projects tab.
Select the user for whom you want to assign roles.
Select the projects for which you want to assign roles for the selected user. Only the selected projects will be displayed in the Edit Roles dialog box.
Click Assign.
Username - displays the user for whom you are assigning roles.
All - selects or deselects all of the listed projects.
Apply to all selected - applies the selected role to all of the selected projects. If none is selected, the user will not have access to those project.
Checkbox - indicates if the project is selected.
Project - lists the projects that you previously selected on the User tab.
Role - select the role to assign to this user for the project. If none is selected, the user will not have access to this project.
Select the role to assign to this user for each project.
Click OK.
The Roles tab is where you configure roles. Roles determine the read, write, delete, and execute permissions for users in projects. Once roles are created, you assign them to users for each project that you want them to have access to. A user's role can differ from project to project. Click Assign on either the Projects tab or Users tab to assign roles.
To add a role:
Click the Roles tab.
Click Add.
Name - enter a name for this role.
Description - enter a description for this role.
Base Role - when you select an existing role, the permissions for that role can be used to start configuring the new role.
Select All - selects all permissions.
Select None - deselects all permissions.
The following permissions are available for the project, requirements, test cases, issues, and reports:
Read - indicates whether users assigned to this role has read access to the project, requirements, tests, issues, public reports, and private reports.
Write - indicates whether users assigned to this role can change the project, requirements, tests, issues, public reports, and private reports.
Delete - indicates whether users assigned to this role can delete the project, requirements, tests, issues, public reports, and private reports.
Execute - indicates whether users assigned to this role can execute tests.
Set/Override results - indicates whether users assigned to this role can set or override test results for tests and Test Sets.
Enter a name and description for this role.
Adjust the permissions for this role.
Click OK.
To edit a role:
Click the Role tab.
Select the role you want to edit.
Click Edit.
Make any changes.
Click OK.
When you delete roles, Oracle Test Manager checks to see if the role is being used, that is, if it is assigned to a user. If the role is in use, you will be prompted to assign another role to the users assigned to the role. To delete roles:
Click the Roles tab.
Select the role that you want to delete.
Click Delete.
If the role is not in use, click Yes when asked to confirm the deletion. Otherwise the Assign Role dialog box is displayed.
Username - displays the users that are assigned to this role.
Project Name - displays the project for which the users are assigned this role.
Please choose a role for re-assignment - select the role that you want to use instead of the role you are deleting. The default is none.
Are you sure you want to delete the role <role> - click Yes to delete the role and reassign the new roles to the user. Click No to exit without deleting the role.
Select the new role to assign to the users assigned to the role you are deleting.
Click Yes.
You can add, clone, rename, assign roles to users for the project, and delete projects from the database.
To add a project:
Select the Projects tab.
Click Add.
This dialog box has the following options:
New Project - enter the name of the new project.
Enable History Tracking - when selected, history tracking audit trails are enabled for the project. The audit trails track changes to every node for almost every field. This results in additional rows in the Oracle Test Manager Database which may eventually cause some performance degradation.
When cleared, history tracking audit trails are disabled for the project and Oracle Test Manager updates only the last activity for a given tree node. The history will be available only to the last activity. If the setting is enabled again to start tracking history, activities going forward from that point in time will be available in the history window. The activities for the duration when the history tracking was disabled are not tracked and will not be available or visible.
Enter the project name.
Select or clear the Enable History Tracking options.
Click OK.
Cloning a project lets you copy an existing project and then modify it so that you do not have to do all of the configuration from scratch. Cloning a project copies the project structure including the fields and assignments. You can select which data to clone.
Note:
Cloning from different databases is not supported. If you need to clone data between different Oracle Test Manager databases, export a database dump from one database and then import the dump file into the new database. See the Oracle Database Utilities documentation for additional information about using the original Export (exp) and Import (imp) utilities and the Data Pump Export (expdp) and Data Pump Import (impdp) utilities.To clone a project:
Click the Projects tab.
Select the project that you want to clone.
Click Clone.
Clone Project - shows the name of the project to clone.
Copy Test Plans - when selected, all test plan data in the project being cloned is are copied to the new project.
Copy Requirements - when selected, all Requirements data in the project being cloned is copied to the new project.
Copy Tests - when selected, all Tests data in the project being cloned is copied to the new project.
Copy Test Sets - when selected, all Test Set data in the project being cloned is copied to the new project.
Copy Issues - when selected, all Issues data in the project being cloned is copied to the new project.
Copy Reports & Dashboard - when selected, all Report and Dashboard data in the project being cloned is copied to the new project.
Copy Test Run History - when selected, all Test Run History data in the project being cloned is copied to the new project.
Enable History Tracking - when selected, History Tracking is enabled for the new project.
Enter the project name.
Select the modules to clone to the new project.
Click OK. The Clone Result window appears when the cloning process is finished.
The system clones data sequentially. If the schema is large enough and cloning is in progress and you want to terminate the process, then delete the Target project (**projectname cloning in progress**) to stop the system from cloning additional data.
There may be situations where the database is not able to support cloning due to resource constraints. In this situation, even after deleting the project, the system does not stop the process, then run the following SQL query:
SELECT SID, SERIAL#, opname, SOFAR, TOTALWORK,ROUND(SOFAR/TOTALWORK*100,2) COMPLETE FROM V$SESSION_LONGOPS WHERE TOTALWORK != 0 AND SOFAR != TOTALWORK order by 1;
The above query provides the long running transaction with sid (sessionid). Kill the session by running the following query:
alter system kill session <sid>;
To rename a project:
Select the Projects tab.
Select the project you want to edit.
Click Edit.
Enter the new name.
Click OK.
To delete a project:
Click the Projects tab.
Select the project you want to delete.
Click Yes when asked to confirm.
Roles determine the project permissions that each user has for a project. Project permissions determine what users can do within the project. Read, write, and delete permissions are assigned to the project, requirements, tests cases, and issues within each project. Execute permission is also assigned to test cases. To assign roles to one project for all users:
Click the Projects tab.
Select the project for which you want to assign roles.
Select the users for which you want to assign roles. Only the selected users will be displayed in the Edit Role dialog box.
Click Assign.
Project - displays the project for which you are assigning roles.
All - selects or deselects all of the listed users.
Apply to all selected - applies the selected role to all of the selected users. If none is selected, the user will not have access to those project.
Checkbox - indicates if the user is selected.
User - displays the users that you selected on the Projects tab.
Role - select the role to assign to this user for the project. If none is selected, the user will not have access to this project.
Select the role to assign to each user for this project.
Click OK.
Fields are used in Oracle Test Manager to describe issues, requirements, and tests. There are two types of fields that apply separately to requirements, tests, issues, and test runs:
Default fields - these are fields that come with the product such as Type, Priority, and Status for requirements. You cannot add or delete default fields. You can change whether they are required or enabled, and you can add, delete, or rename their associated options.
Custom fields - these are fields that you add that are specific to your product. For each custom field, you define its properties, then add options where appropriate.
Role-based field security settings specify which roles have read/write permissions and which roles have read-only permissions for specific fields. When you add or edit fields or field options, a Permissions link in the dialog box provide access to the Permissions settings for the selected field or field option.
Before adding custom fields, make sure to logout and close Oracle Test Manager. When finished adding custom fields, logout and close the Administrator before starting Oracle Test Manager.
To add an option to a default or custom field:
Click the Fields tab.
Select Default Fields or Custom Fields for the category of the field to which you want to add an option.
Select the field to which you want to add an option.
Click Add to the right of the Option Lists section. The New Option dialog box has the following options:
Name - enter the name of the new option.
Permissions - opens a dialog box for setting the role-based field security settings for the field.
Insert the new option at the top of list - when selected, the new option appears at the top of the list. When cleared, the new option appears just below the currently selected item in the Option List. If you want to have a new item appear in a specific location in the option list, close the Add Option dialog box, select the option in the Option List that you want the new option to appear after, then click Add. Leave this Insert the new option at the top of list checkbox cleared when adding the new option.
Enter the name of the new option.
Click Permissions if you want to specify which roles have read/write or read-only access to the option. Move the roles to the desired permissions using the arrow buttons and click OK.
Select the Insert the new option at the top of list option if you want the new option to appear at the top of the list. Clear the Insert the new option at the top of list option if you want the new option to appear after the currently selected option in the Option List.
Click OK. Use the arrow buttons to reorder the list. The order in which they appear in this list is the order in which they will appear in the drop down option lists in Oracle Test Manager.
Note:
The order of the priority field for requirements determines the color of the icons displayed in Test Manager. For example, if High priority is first in the list, the icon will be green. Following is a list of colors and the corresponding display orders:1 -Green
2-Orange
3-Red
4-Blue
5-Silver
6-Purple
7-Dark Orange
8-Light Blue
9-Gray
To rename an option:
Click the Fields tab.
Select Default Fields or Custom Fields for the category of the field containing the field with the option you want to change.
Select the field containing the option you want to change.
Select the option you want to rename.
Click Edit.
Enter the new name.
Click Permissions if you want to specify which roles have read/write or read-only access to the option. Move the roles to the desired permissions using the arrow buttons and click OK.
Click OK. Use the arrow buttons to reorder the list. The order in which they appear in this list is the order in which they will appear in the drop down option lists in Oracle Test Manager.
Note:
If you delete a custom field option that has been used in a requirement, test, or issue, Oracle Test Manager will default the custom field to the first value in the option list the next time you edit the requirement, test, or issue. For requirements, tests, or issues that have not been edited and saved, the original value will remain unchanged.To delete an option:
Click the Fields tab.
Select Default Fields or Custom Fields for the category of the field containing the field with the option you want to delete.
Select the field containing the option you want to delete.
Select the option you want to delete.
Click Delete.
Click Yes when asked to confirm the deletion.
You can edit whether a default field is required, enabled, triggers an email when changed, and whether it is included in the email. To edit a default field:
Click the Fields tab.
Select Default Fields in the left pane for the category of the field you want to edit.
Select the field you want to edit.
Click Edit to display the Edit Field dialog box.
This dialog box has the following options:
Name - displays the field name.
Label - displays the field label that is displayed in Oracle Test Manager.
Permissions - opens a dialog box for setting the role-based field security settings for the field.
Field Properties - select a property to enable it; deselect the property to disable it.
Required - requires that the field be entered in Oracle Test Manager when selected.
Enabled - indicates whether the field is used in Oracle Test Manager.
Trigger Email Notification - indicates whether an email will be sent to the configured recipients when this field changes. Click the pencil icon to display the Setup E-mail Configuration dialog box for configuring email recipients. The logged in user should not be the same as the username that is specified for the trigger. The trigger checks the email address of the user who changes the field and does not send notification to any users with the same email address.
Include this field in notification mails - indicates whether the field should be included in notification emails.
Click Permissions if you want to specify which roles have read/write or read-only access to the option. Move the roles to the desired permissions using the arrow buttons and click OK.
If you select Trigger Email Notification, the Setup E-mail Configuration dialog box for this field is displayed.
Projects - select the projects for which you want to configure this field.
Checkbox - when checked, notification email will be sent to all users assigned tot his role.
Roles - lists the roles. Users assigned the selected role(s) will receive email notifications if they have email notifications enabled as part of their user configuration.
E-mail - enter the email addresses of the people you want to receive notification emails, separated by commas or click To to select from a list of users who have email notifications enabled as part of their user configuration.
To - displays the Select Email recipients dialog box for selecting email recipients. The Select email recipients list includes email addresses of the users who have email notifications enabled as part of their user configuration.
Set - saves the settings for the selected project.
Select the project for which you want to configure this field.
Select a role if you want all users assigned to the role to receive a notification email.
Enter the email addresses of recipients or click To to select from the list of users in the database that have email notification enabled.
<recipient list> - lists users in your database that have email notification enabled.
Select - adds the selected recipients to the To field.
To - displays the selected recipients separated by a comma.
Select the recipients you want to add and click Select and then click Done.
Click Set to save the email settings for the selected project.
Click OK to close the Setup E-mail Configuration dialog box.
Make any other changes and click OK to close the Edit Field dialog box.
Click the Fields tab.
Select Custom Fields in the left pane for the category to which you want to add a custom field.
Click Add to display the Add Custom Field dialog box.
This dialog box has the following options:
Name - enter the name of the field.
Label - enter the field label that will appear in the Oracle Test Manager dialog boxes.
Permissions - opens a dialog box for setting the role-based field security settings for the field.
Type - select the type of field. The options are:
Option List - lets you select an option from a list. You must add at least one option before exiting the Administrator.
Option List/Text - lets you select an option from a list or enter text.
User List - creates a list of the users in the database and lets you select one.
Text - lets you enter one line of text.
Multiline Text - lets you enter multiple lines of text.
Multiline/Append - creates a multiline text field and when editing, lets you choose to append new text to existing text. If you choose to append, the date and user name are automatically added.
Heading - lets you create a heading for grouping custom fields. The heading is for display purposes only in the right-hand pane of Oracle Test Manager.
Applies To - select the project to which this field applies.
Properties - select the properties that apply to this field.
Required - indicates whether the field must be entered.
Enabled - indicates whether to make this field available to Oracle Test Manager. Disabled fields are not available in Oracle Test Manager.
Trigger Email Notification - indicates whether an email will be sent to the configured recipients when this field changes. Click the pencil icon to display the Setup E-mail Configuration dialog box for configuring email recipients. The logged in user should not be the same as the username that is specified for the trigger. The trigger checks the email address of the user who changes the field and does not send notification to any users with the same email address.
Include this field in notification mails - indicates whether the field should be included in notification emails.
Project Specific Options - when selected, you can add options specifically for each project by selecting the project in the Option Lists section. If not selected, all projects will have the same options.
Click Permissions if you want to specify which roles have read/write or read-only access to the option. Move the roles to the desired permissions using the arrow buttons and click OK.
If you select Trigger Email Notification, the Setup E-mail Configuration dialog box for this field is displayed.
Projects - select the projects for which you want to configure this field.
Checkbox - when checked, notification email will be sent to all users assigned tot his role.
Roles - lists the roles.
E-mail - enter the email addresses of the people you want to receive notification emails, separated by commas.
To - displays the Select Email recipients dialog box for selecting email recipients.
Set - saves the settings for the selected project.
Select the project for which you want to configure this field.
Select a role if you want all users assigned to the role to receive a notification email.
Enter the email addresses of recipients or click To to select from the list of users in the database that have email notification enabled.
<recipient list> - lists users in your database that have email notification enabled.
Select - adds the selected recipients to the To field.
To - displays the selected recipients separated by a comma.
Select the recipients you want to add and click Select.
Click Done.
Click OK.
Enter other field information.
Click OK. For list type items, enter the options that will appear in the list. If you have add an Option List, you must enter at least one option before exiting the Administrator.
You can unlock locked records and purge deleted records.
The Reset Password utility allows the installing user of the Oracle Application Testing Suite web applications to reset the password for the Administrator account in an Oracle Load Testing or Oracle Test Manager database.
The installing user of the Oracle Application Testing Suite can reset the password for:
Oracle Load Testing Administrator user
Oracle Test Manager Administrator user
The default Administrator user password is the password specified during the Oracle Application Testing Suite installation.
See the Oracle Application Testing Suite Installation Guide for additional information about using the Reset Password utility.