Header

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Introduction: Execution profiles allow you to set up and manage configurations for executing test suites. With these profiles, you can standardize the execution settings for different types of tests. This guide simplifies how to work with these profiles.

 

Prerequisites:

·       Access to the test suite you intend to run.

·       Familiarity with the platform you're testing (web, mobile).

 

Process Flow:

 

Understanding Execution Profiles

·       Use Case: Imagine you're testing a mobile application. Depending on the platform (iOS or Android) and the device's specifications, you might need different settings. Execution profiles help you manage these settings efficiently.

·       An execution profile contains configuration settings for running test suites.

·       Each web/mobile project has a default profile named the "System Execution Profile". Its execution mode is set to local (unchangeable), but you can switch the browser (default is Chrome).

·       Desktop projects don't support the Execution Profile feature.

Adding an Execution Profile

·       Use Case: Suppose you're introducing testing on a new browser or a new version of an existing browser. To accommodate this, you'd want to create a new execution profile.

·       You can create various profiles with unique settings.

·       Select 'Execute' from the Expand Menu.

·       Go to the 'Execution Profile' tab.

·       Click 'Add'.

·       Name your profile.

·       Set up the configuration. (Refer to the System Execution Profile Settings guide for details.)

·       In the profile list, the "Usage Count" shows which users chose the profile for their test suites.

Setting the Default Execution Profile

·       Use Case: Over time, you've noticed that 80% of your testing happens on a specific browser and platform combination. To streamline the process, you decide to set this combination as the default execution profile.

·       You can designate any profile as the default.

·       Choose 'Execute' from the Expand Menu.

·       Access the 'Execution Profile' tab.

·       Check the box under the 'Default' column for the desired profile.

·       Click 'Save'.

Editing an Execution Profile

·       Use Case: With the latest software updates, some of the settings in your execution profile need adjustments. Instead of creating a new profile, you decide to update the existing one.

·       Modify an existing profile's settings by:

·       Navigating to 'Execute' from the Expand Menu.

·       Entering the 'Execution Profile' tab.

·       Clicking 'Edit' for the chosen profile.

·       Adjusting the settings. For details, see the System Execution Profile Settings guide.

Deleting Execution Profiles

·       Use Case: Some old browsers are no longer supported by your application. The execution profiles associated with these browsers are now redundant and need removal.

·       You can't remove a profile linked to a test suite or set as the default. First, assign another profile as the default.

·       Head to 'Execute' from the Expand Menu.

·       Enter the 'Execution Profile' tab.

·       Check the boxes for the profiles you wish to delete.

·       Hit 'Remove'.

Exporting an Execution Profile

·       Use Case: You have remote teams that work offline. To ensure they use the same testing settings, you decide to export and share the execution profile with them.

·       Export profiles to use them for offline suite executions.

·       Go to 'Execute' from the Expand Menu.

·       Visit the 'Execution Profile' tab.

·       Click 'Export' for the desired profile.

·       Choose where to save the profile.

·       It gets saved as a JSON file.

 

Conclusion: Execution profiles are essential tools for maintaining consistency and efficiency in your testing process. By mastering their creation and management, you ensure your software is tested under the right conditions every time.

  • No labels