Skip to main content

Default test suites

Use CI Management to define the default test suites for test frameworks. These parameters are passed to builds that you can run in TeamCity. You can define test suites for gUnit Server Tests or gUnit Smoke Tests.

Note:

Access to this application is managed by Guidewire Hub. For details, see Access Cloud Platform apps and services.

Access CI Management​

To access CI Management from Guidewire Home:

  1. Select a star system.

  2. From Apps , select CI Management or select it from your pinned apps.

Configure a default test suite​

To define the default test suites:

  1. Go to the testing framework for which you want to set the parameters.

    You can define test suites for gUnit Server Tests or gUnit Smoke Tests.

  2. Select + Add.

  3. In Application, select InsuranceSuite application for which you want to run the test.

  4. Enter a suite name.

    Note:

    The name must be fully-qualified and must include the Gosu class name and package where the suite resides. For example, gw.suites.PCExampleSmokeSuite.

  5. In Branch inclusion rules, add a list of branches or branch patterns for which the specified suite should be included in the test builds.

    Add each rule in a new line. You can use the * wildcard.

  6. In Branch exclusion rules, add a list of branches or branch patterns for which the specified suite should be excluded from running in the test builds.

    Add each rule in a new line. You can use the * wildcard.

  7. Select Add.

Note:

For Branch inclusion rules and Branch exclusion rules, you can use the * wildcard as zero or more characters. For example:

  • * as all branches.
  • release/* as branches that are starting with release/.
  • *-test as branches that are ending with -test.

Verify in TeamCity​

You can now go to TeamCity and verify the setup:

  1. Go to TeamCity → {project} → {application} → {test_framework}.

  2. Go to the modified build and select Run.

    TeamCity will run the build.

  3. In the Build Log tab, check the progression of the TeamCity build.

    In the Select test suites step, you can see which suites are being run and for which branches.

Note:

It might take a few minutes for the changes to be applied to the build.

Run compile for no matching suites​

By default, the compilation of an InsuranceSuite application is always executed. This rule applies even when no test suites match a branch on which the tests are executed. To change compilation settings:

  1. Go to the testing framework for which you want to change the compilation setting.

  2. From Run compile for no matching suites, select the checkbox next to the InsuranceSuite application that you want to compile without matching test suites.

    To disable compilation when no test suites are matching, clear the checkbox next to the InsuranceSuite application.

Run compile for no matching suites in the testing framework table.

Verify in TeamCity​

You can now go to TeamCity and verify the setup:

  1. Go to TeamCity → {project} → {application} → {test_framework}.

  2. Go to the modified build and select the ellipsis next to the Run button.

  3. Open the Parameters tab.

  4. Check if run_compile_on_empty_suite_list is selected.

Edit a default test suite​

To edit a default test suite:

  1. In the table, find the test suite that you want to edit.

  2. Select Edit .

  3. Change Branch inclusion rules and Branch exclusion rules as needed.

  4. Select Save.

Delete a default test suite​

To delete a default test suite:

  1. In the table, find the test suite that you want to delete.

  2. Select Delete .

  3. Select Delete.