Settings

All XStudio's settings can be set through the Settings menu. This is where you can configure how to connect to the database.
This is also where you specify how to connect to third-party bug-tracking systems (Generic, JIRA, Mantis, Bugzilla or Trac)
or requirement management systems (Generic or JIRA).

Database

The following settings are used to define the connection details to the database server.


Highslide JS

Field Description
driver jar path This indicates where XStudio can find the JDBC driver to connect to the database. This field must indicates a relative path from <Install_folder>\bin\jdbc folder to the jar file.

For instance:

  • MySql: mysql-connector-java-5.1.12/mysql-connector-java-5.1.12-bin.jar
  • Oracle: oracle-11g-R2/ojdbc6.jar
  • SQLServer: sqljdbc_3.0/enu/sqljdbc4.jar
driver class path Classpath to instanciate the driver from the JAR file.

For instance:

  • MySql: com.mysql.jdbc.Driver
  • Oracle: oracle.jdbc.driver.OracleDriver
  • SQLServer: com.microsoft.sqlserver.jdbc.SQLServerDriver
database server This indicates the IP address or the name of the database server.
database name The name of the database

For instance: xstudio_db
connection template Connection template to use the JDBC driver.

WARNING: do not replace ‘database_server‘ and ‘database_name‘ fields in the connection template.
They will be automatically replaced by the system with what you specified in ‘database server‘ and ‘database name‘ fields.

For instance:

  • MySql: jdbc:mysql://database_server:3306/database_name
  • Oracle: jdbc:oracle:thin:@//database_server:1521/database_name
  • SQLServer: jdbc:sqlserver://database_server;databaseName=database_name;
username Username to connect to the database
For instance: xstudio
password Password corresponding to the user account
For instance: xstudiopwd


IMPORTANT: SQLServer database support is included only in XStudio Business and XStudio Enterprise. You'll need to have your license key registered or the system won't let you continue.

IMPORTANT: Oracle database support is included only in XStudio Enterprise. You'll need to have your license key registered or the system won't let you continue.


Email notifications

The following settings are used by the system to send email notifications.


Highslide JS

All the fields value are case-sensitive:


Field Description
smtp host SMTP host that XStudio will use to send emails. Use the same as you’re using usually.
smtp port SMTP port that XStudio will use to send emails.
smtp username Optional, if your SMTP server requires authentication.
Username to authenticate to the server.
smtp password Optional, if your SMTP server requires authentication.
Password to authenticate to the server.
smtp from address Email address that XStudio will use to send emails.
smtp secure connection Defines which security scheme is used to connect to the SMTP server.
3 choices are available:
  • None
  • SSL
  • TLS
Ask your IT if you don't know what these parameters are about.

TIP: Custom notification emails
In XStudio, you can customize the contains of defects notification mails.
To do that, you must edit the following ".xslt" files located in "xstudio install dir/export/xsl/" folder:
  • email_defect_created.xslt: Notification email after a bug is created
  • email_defect_modified.xslt: Notification email after a bug is modified
  • email_defect_reminder.xslt: Notification email as a bug reminder
  • email_session_completed.xslt: Notification email after session has been executed
  • email_testcase_failed.xslt: Notification email when a test case just failed



LDAP/Active Directory

The following settings are used by the system to register users in the central dictionnary in XStudio and the authenticate them directly on the dictionnary server.


Highslide JS

All the fields value are case-sensitive:


Field Description
LDAP Enabled Enabled LDAP connector so that you can register LDAP users in XStudio.
Server URL URL of the LDAP server. It can be an OpenLDAP, Active Directory, OpenId or any LDAP compliant server.
For instance: ldap://192.168.10.116:389
Root path The root path corresponds to the domain you want to search/register LDAP users from.
For instance: dc=example,dc=com
User filter/b> LDAP standard filter to retrieve only users from the server.
For instance: (objectClass=inetOrgPerson) (i.e. OpenLDAP example)
User email attribute Name of the attribute containing the email of the user in the LDAP server.
For instance: mail
Connection username Username to connect to the database and retrieve the list of LDAP users in the dictionnary.
For instance: cn=admin,dc=example,dc=com
Connection password Username to connect to the database and retrieve the list of LDAP users in the dictionnary.
For instance: admin_pwd



Features

The following settings are used to customize the feature set of XStudio.
You can click on the individual help buttons to get more details on each parameter.

Highslide JS

Company logo

You can provide your company's logo so that it is used in all the reports generated. You just need to provide the name of the picture file (gif, jpg or png) in this text field and copy the file to <XStudio install path>/export/resources/images/.
If you're using the web package, you'll need to move the image to resources/images/ within the export.zip archive on the server.

Include specifications in life-cycle

You can disable the Specification tree if you wish. In this case the requirements will be linked directly to the tests.


Display quality column in trees (perf. impact)

Displaying the Quality column in the SUT tree and in the campaign tree is pretty time-consuming. You may prefer to disable this to have the best performances.

Show ids in trees

If this option is selected, all the objects in the trees will have their names prefixed with their Ids.

Spell checker

If this option is selected, the Spell checker will be enabled.
Whenever you edit some text, if you make a typo the faulty portion of text will be highlighted and you'll be prompt with some suggestions.

Test procedure autocompletion (perf. impact)

If this option is selected, when you write the test procedure you will be automatically prompted with some suggestions. This options may be time consuming in terms of startup time if you already loaded the database with thousands of test cases.

Defect submission during manual testing

If this option is activated, you will be able to create bug on the fly while you are executing manual tests with any of the three manual launchers.

Not implemented testcase notification

If this option is activated, if you execute a session including tests that are not ready to be executed they will be nicely skipped and you will be notified about it at the end of the session. Tests not ready to be executed are:
  • Manual tests not marked as "authored"
  • Automated tests not marked as "developed"
If this option is not activated, you will not be notified about the fact some tests were skipped.

Session export for scripting

You can enable the batch export session for scripting feature. When enabled, a new button will appear in the campaign session toolbar. When you will click on this button, a campaign session XML report is automatically generated in the Session export destination folder and (optionally) processed by the custom script located in Session export script path.


Session export destination folder

See Session export for scripting.

Session export script path

See Session export for scripting.

Connectors

Requirements

If not using the integrated Requirement Management module, the following setting will define how to connect to a third-party system.

Integrated requirements

This setting allows using XStudio's integrated requirement management module. The integrated requirement database will be used.
Field Description
requirement system Integrated


Generic requirements

This setting allows interfacing with a generic third-party requirement management system. Specifications or Tests are linked to a virtual external identifier.
Field Description
requirement system Generic


JIRA requirements

This setting allows interfacing with a third-party JIRA issue management system.

Highslide JS

Field Description
requirement system JIRA
username Username of a full-access JIRA account able to see all the requirements you wish to retrieve
password Password corresponding to the JIRA user account
url pattern This indicates the URL to use with your JIRA instance to edit a requirement.

The URL must include the tag 'requirement_id' that will be dynamically replaced by the id of the requirement to be displayed/edited

For instance:

http://192.168.10.22:8080/browse/requirement_id
url new requirement This indicates the URL to use with your JIRA instance to create a new requirement.

The URL can include a tag 'issueType' that will be used as the default type of issue when you create a new requirement
The URL can include the tag 'project_id' that will be used as the default project when you create a new requirement

For instance:

http://192.168.10.22:8080/secure/CreateIssue.jspa?pid=project_id&issuetype=1
url xml-rpc server This indicates the URL of your JIRA's XML-RPC server.

For instance:

http://192.168.10.22:8080/rpc/xmlrpc

More information are available in the install documentation about how to setup the JIRA server to communicate with XStudio
filter projects The list of project names separated by ';' characters

For instance: Project_1;Project_2;Project_3
When left empty, issues from all projects are retrieved.
filter issue types The list of issue types that you wish to retrieve in the tree separated by ';' characters

For instance: 1;2

By default, issue types are:
  • 1 = Bug
  • 2 = Improvement
  • 3 = New Feature
  • 4 = Task
When left empty, issues with any type are retrieved.
filter status The list of status that you wish to filter separated by ';' characters

For instance: Open;Resolved;Closed
When left empty, issues with any status are retrieved.


Bug-tracking

Integrated bug-tracking

This setting allows using XStudio's integrated bug-tracking management module. The integrated bug database will be used.

Field Description
bug-tracking system Integrated


Generic bug-tracking

This setting allows interfacing with a generic third-party bug-tracking system. Failed tests are linked to a virtual external identifier.

Field Description
bug-tracking system Generic


Mantis bug-tracking

This setting allows interfacing with a third-party Mantis bug-tyracking management system.

Field Description
bug-tracking system Mantis
driver jar path This indicates where XStudio can find the JDBC driver to connect to the Mantis database. This field must indicates a relative path from <Install_folder>\bin\jdbc folder to the jar file.

For instance: mysql-connector-java-5.1.12/mysql-connector-java-5.1.12-bin.jar
driver class path Classpath to instanciate the driver from the JAR file.

For instance: com.mysql.jdbc.Driver
database server This indicates the IP address or the name of the Mantis database server.
database name The name of the Mantis database

For instance: bugtracker
connection template Connection template to use the JDBC driver.

WARNING: do not replace ‘database_server‘ and ‘database_name‘ fields in the connection template.
They will be automatically replaced by the system with what you specified in ‘database server‘ and ‘database name‘ fields.

For instance: jdbc:mysql://database_server:3306/database_name
username Username to connect to the Mantis database

For instance: mantis
password Password corresponding to the user account

For instance: mantispwd
url pattern This indicates the URL to use with your Mantis instance to edit a bug.

The URL must include the tag 'bug_id' that will be dynamically replaced by the id of the bug to be displayed/edited

For instance:

http://192.168.10.101/view.php?id=bug_id
url new bug This indicates the URL to use with your Trac instance to create a new bug.

For instance:

http://192.168.10.101/bug_report_page2.php


Bugzilla bug-tracking

This setting allows interfacing with a third-party Bugzilla bug-tyracking management system.

Field Description
bug-tracking system Bugzilla
driver jar path This indicates where XStudio can find the JDBC driver to connect to the Bugzilla database. This field must indicates a relative path from <Install_folder>\bin\jdbc folder to the jar file.

For instance: mysql-connector-java-5.1.12/mysql-connector-java-5.1.12-bin.jar
driver class path Classpath to instanciate the driver from the JAR file.

For instance: com.mysql.jdbc.Driver
database server This indicates the IP address or the name of the Bugzilla database server.
database name The name of the Bugzilla database

For instance: bugtracker
connection template Connection template to use the JDBC driver.

WARNING: do not replace ‘database_server‘ and ‘database_name‘ fields in the connection template.
They will be automatically replaced by the system with what you specified in ‘database server‘ and ‘database name‘ fields.

For instance: jdbc:mysql://database_server:3306/database_name
username Username to connect to the Bugzilla database

For instance: mantis
password Password corresponding to the user account

For instance: mantispwd
url pattern This indicates the URL to use with your Bugzilla instance to edit a bug.

The URL must include the tag 'bug_id' that will be dynamically replaced by the id of the bug to be displayed/edited

For instance:

http://192.168.10.100/show_bug.cgi?id=bug_id
url new bug This indicates the URL to use with your Trac instance to create a new bug.

For instance:

http://192.168.10.100/enter_bug.cgi


Trac bug-tracking

This setting allows interfacing with a third-party Trac issue management system.

Field Description
bug-tracking system Trac
username Username of a full-access Trac account able to see all the bugs you wish to retrieve
password Password corresponding to the Trac user account
url pattern This indicates the URL to use with your Trac instance to edit a bug.

The URL must include the tag 'bug_id' that will be dynamically replaced by the id of the bug to be displayed/edited

For instance:

http://192.168.10.22:8080/browse/bug_id
url new bug This indicates the URL to use with your Trac instance to create a new bug.

The URL can include a tag 'issueType' that will be used as the default type of issue when you create a new bug
The URL can include the tag 'project_id' that will be used as the default project when you create a new bug

For instance:

http://192.168.10.22:8080/secure/CreateIssue.jspa?pid=project_id&issuetype=1
url xml-rpc server This indicates the URL of your Trac's XML-RPC server.

For instance:

http://192.168.10.22:8080/rpc/xmlrpc

More information are available in the install documentation about how to setup the Trac server to communicate with XStudio


JIRA bug-tracking

This setting allows interfacing with a third-party JIRA issue management system.

Field Description
bug-tracking system JIRA
username Username of a full-access JIRA account able to see all the bugs you wish to retrieve
password Password corresponding to the JIRA user account
url pattern This indicates the URL to use with your JIRA instance to edit a bug.

The URL must include the tag 'bug_id' that will be dynamically replaced by the id of the bug to be displayed/edited

For instance:

http://192.168.10.22:8080/browse/bug_id
url new bug This indicates the URL to use with your JIRA instance to create a new bug.

The URL can include a tag 'issueType' that will be used as the default type of issue when you create a new bug
The URL can include the tag 'project_id' that will be used as the default project when you create a new bug

For instance:

http://192.168.10.22:8080/secure/CreateIssue.jspa?pid=project_id&issuetype=1
url xml-rpc server This indicates the URL of your JIRA's XML-RPC server.

For instance:

http://192.168.10.22:8080/rpc/xmlrpc

More information are available in the install documentation about how to setup the JIRA server to communicate with XStudio
filter projects The list of project names separated by ';' characters

For instance: Project_1;Project_2;Project_3
When left empty, issues from all projects are retrieved.
filter issue types The list of issue types that you wish to retrieve in the tree separated by ';' characters

For instance: 1;2

By default, issue types are:
  • 1 = Bug
  • 2 = Improvement
  • 3 = New Feature
  • 4 = Task
When left empty, issues with any type are retrieved.
filter status The list of status that you wish to filter separated by ';' characters

For instance: Open;Resolved;Closed
When left empty, issues with any status are retrieved.


Kalistick

With this plugin you will be able to trace your test activities in Kalistick and import automatically the non-regression campaigns to re-execute. The following settings will define how to interface with kalistick (if relevant).

Field Description
Kalistick integration Checked
Kalistick url start This indicates the URL to inform Kalistick that a new test is about to start.

For instance:

http://192.168.10.230:9096/api/tce/start?code=test_id&label=test_name
Kalistick url stop This indicates the URL to inform Kalistick that a new test is finished.

For instance:

http://192.168.10.230:9096/api/tce/stop?uuid=kalistick_id&successful=test_status&statusInfo=status_info
Kalistick url add cookie This indicates the URL to add a cookie in the browser.

For instance:

http://192.168.10.230:9096/api/tce/addCookie?uuid=kalistick_id


Highslide JS

You can also get more information on how to import Kalistick campaign

Internationalization

A user is given a language (localization) which is used to display the application using user's language but is also associated with a location (internationalization) which is used to know which public holidays and week-ends this user will be associated with.

Each country can be easily configured: public holidays can be added, edited and deleted. In addition, each country is associated to some week-ends settings. Hence, most of the countries in the world are using Saturday and Sunday for the week-ends but some others (such as Israel, Qatar, Algeria etc.) are using Friday and Saturday and again some others (such as Saudi Arabia) Thursday and Friday.

The default settings are supposed to be correct but it's good to let the administrator of the system customizes it if necessary. These settings are accessible through the Settings menu entry.

Highslide JS Highslide JS

Hence, all the calendars are affected by this change as each user may have different week-ends.

Absences are also included in the calendars so you have a complete picture of the projects or the staff workload, status are then easier to figure out.

Highslide JS


Week-ends and holidays are easily identifiable as they are in black and grey
Note that the calendar tree is still expandable as usual. This greatly facilitates the reading i.e. when you want to know the details about why a user is overloaded in a certain time frame.

A legend (including some gradient colors for the workload) has been added to help the reading.