Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2024.1

...

  1. Select the desired suite and click Add Property on the tool bar.

  2. In the Add Global wizard, choose Global Property > Database Account and click Finish. A Properties node opens and the Database Account panel displays in the right side of the GUI.
  3. Specify the settings in the Database Account panel as follows:
    1. If you want to change the default name, enter the new name in the Name field.
    2. Click Add Property to All (if you don’t, the global properties you add will be ignored by the tools in the suite) and choose an option from the corresponding dropdown:

      • Use Shared Property Only: when selected, the corresponding tools in the suite will be able to only use the global property you added.

      • Use Local and Shared Properties: when selected from the drop-down list, the corresponding tools in the Action suite will be able to use the global property you added and any properties configured within the individual tool itself.

    3. Configure the rest of the Database Account settings as needed.
      • If the account settings are stored in a file, enable File and specify the path to that file.
        • To refresh/reload the file (for example, if you edited it externally), click Refresh Configuration Settings.
      • If you want to specify the settings in this panel, enable Local and specify the driver settings. See 

        Database Configuration Parameters in SOAtest or Database Configuration Parameters in Virtualize for additional information

        • To export these values to a file, click Export Configuration Settings. Once the values are exported to a file, you can import the file through the File > Input File control (described above). This way, you won’t have to reenter the same values if you want to add this same account to a different suite. 

          Note that exported properties files contain the following properties:

          • driver
          • url
          • username
          • password
          • close.connection

          For example:

          version=1
          driver=org.hsqldb.jdbcDriver
          url=jdbc:hsqldb:hsql://localhost/parabank username=sa
          password=dGVzdA==
          close.connection=true

           

Global Authentications

You can add authentication methods to your test suite so they can be shared among your tests without needing to define authentication settings for each test. A default authentication method can be set for the test suite that will be automatically applied to every test, though individual tests can be configured to use alternative authentication methods, as needed. Multiple authentication methods can be created for the test suite, but only one can be set as the default.

...