Versions Compared

Old Version 29

changes.mady.by.user ravi.chandran

Saved on

compared with

New Version Current

changes.mady.by.user ravi.chandran

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Expand
titleHow to Enable Higher Concurrency for Web-Based Dashboards and Reports (For MySQL only)?

In order to access Web-based dashboards seamlessly, you must set these configuration settings for MySQL server.

  • On Windows these settings can be configured in the C:\Program Files\MySQL\MySQL Server 5.7\my-default.ini
  • On Linux these settings can be configured in the $MYSQL_HOME/my.cnf

Set the following parameters in the file mentioned above:

  • innodb_buffer_pool_size=64M
  • query_cache_size=128M

...

Expand
titleHow to Find UDID?

In order to get started with application testing with mobile devices using Qualitia, users need to specify the Android or iOS device ID into Configuration Settings.

Anchor
HowToFindUDID
HowToFindUDID

Expand
titleIdentifying UDID of iOS devices:

Each iOS device has a Unique Device Identifier (UDID), that helps automation engines to identify the specific device from the group of devices. The ID is the combination of letters and numbers that is specific to the device.

You can identify UDID from Simulator window or using the terminal.

To find the UDID of iOS device from the Simulator window:

  1. Open the Simulator window.
  2. On the Hardware menu, select Device and then point to Manage Devices.
  3. Select the device in the left pane.
    Device Information is displayed in the right pane.
    Value displayed against Identifier is the UDID.
  4. Qualitia users can add this identifier in the UDID field when 13568200

To find the UDID of iOS device using terminal:

  1. Lunch terminal.
  2. Execute command, instruments -s devices.
    The list of devices are displayed.
  3. Take the value for the desired device and add it in the UDID field when 13568200.


Expand
titleIdentifying UDID of Android device:

UDID of Android device is nothing but the device name.

To identify the device name:

  1. Launch the command prompt.
  2. Execute command, adb devices -l.
    This will list all the devices connected to the computer with device details.
    You can use the device name listed here when 13568200.


...

Expand
titleWhy the Real Time Reporting Portal is not Showing some Suite Executions?

You would not be able to view some suite executions due to the following reasons:

  • You might have applied some filter options as per which the suite exceptions are displayed.
  • Dry run executions are not displayed.
    • You might

    Why the Real-Time Reporting Portal is not showing some suite execution reports?

    The following reasons due to which some suite executions are not displayed:

    • The user might have applied filter options.
    • The user does not have access to the
      • project for which the executions were runYou
    • associated project. 
    • Before executing the test suite, the user did not select
      • the Enable Real
    • the EnableReal-Time Reporting
      • as
    •  as True in the associated execution profile.
      • For more details, refer to 
    • After the test suite execution, the user has an option to import the locally saved report.
    • The system where the execution is running
      • ,
    • has a connection to QAS server.
    • If
      • executing
    • it is an offline package execution, the user has configured in the offline package is a valid QAS user and assigned to the project
    • The
      • execution is not
    • portal does not support test cases executed through TFS Azure DevOps or HP ALM.
      • No disk space available in
    • The portal does not show Dry run executions
    • Qualitia server folder does not have sufficient space. If you want to remove some reports, refer to https://qualitia.atlassian.net/wiki/spaces/QAS8/pages/1450967246/Purging+Data+from+the+Server+Administration+Portal