Agents Administration - Tests
 

Default Parameters for BitBuktIssueTest

A user with a valid account on the Bitbucket cloud can create bug reports, feature requests and project management tasks by simply creating issues in the Bitbucket repositories. When you add a repository to Bitbucket Cloud, you also get an issue tracker. This is the place where the issues are stored to track the status of your project's feature requests, bug reports and other project management tasks. By analyzing the history of issues provided by the issue tracker, the user can instantly know the tasks that were performed frequently, the count of open/closed/resolved issues, the list of invalid/duplicate issues, etc. To help the users in this regard, this test monitors the repositories in the target account, and for each repository, reports the number of different issues in the issue tracker over the time.

This page depicts the default parameters that need to be configured for the BitBuktIssueTest.

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • Specify the user name and password assigned to the Bitbucket account to be monitored in the USERNAME and PASSWORD text boxes.

  • Confirm the password by retyping it in the CONFIRM PASSWORD text box.

  • Provide a comma-separated list of repository names that you do not want to monitor in the EXCLUDED REPOSITORIES text box. For instance, to exclude repositories with names that contain ‘ver1’ and ‘ver2’ from monitoring, your specification should be: *ver1*,*ver2*

  • By default, SHOW CLOSED ISSUES DD flag is set to Yes, indicating that by default, the test generates detailed measures for Closed issues measure. If you do not want the test to generate and store detailed measures for closed issues, set this flag to No.

  • By default, SHOW RESOLVED ISSUES DD flag is set to Yes, indicating that by default, the test generates detailed measures for Resolved issues measure. If you do not want the test to generate and store detailed measures for closed issues, set this flag to No.

  • By default, SHOW WONTFIX ISSUES DD flag is set to Yes, indicating that by default, the test generates detailed measures for Wontfix issues measure. If you do not want the test to generate and store detailed measures for closed issues, set this flag to No.

  • By default, SHOW ONHOLD ISSUES DD flag is set to Yes, indicating that by default, the test generates detailed measures for Onhold issues measure. If you do not want the test to generate and store detailed measures for closed issues, set this flag to No.

  • By default, SHOW INVALID ISSUES DD flag is set to Yes, indicating that by default, the test generates detailed measures for Invalid issues measure. If you do not want the test to generate and store detailed measures for closed issues, set this flag to No.

  • By default, SHOW DUPLICATE ISSUES DD flag is set to Yes, indicating that by default, the test generates detailed measures for Duplicate issues measure. If you do not want the test to generate and store detailed measures for closed issues, set this flag to No.

  • The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.

  • Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.