Zephyr Cloud and Server
This guide shows you how to use Provar’s integration with Zephyr Cloud and Zephyr Server to:
- Connect to your Zephyr Cloud and Zephyr Server instances
- Upload and download tests to and from Zephyr
- Create Test Plans to run your test against Zephyr
- Execute your Test Plan
Note: Zephyr’s Enterprise Edition is not currently supported.
Prerequisites
The ZAPI plug-in for Zephyr needs to be installed into your JIRA instance. This is required for both Zephyr Cloud and Zephyr Server.
Connecting to Zephyr Cloud
Step 1: Make a note of your JIRA API token.
If you don’t already have a JIRA API token, see Appendix A: Creating a JIRA API token. Make a note of the API token value.
Step 2: Make a note of your Zephyr key.
If you don’t already have a ZAPI Key, see Appendix B: Creating a ZAPI key. Make a note of the Name, Access Key, and Secret Key.
Step 3: Create a Zephyr Cloud connection in Provar.
In Provar Desktop, switch to the Test Settings view and open the Connections sub-tab. Click the plus sign icon in the view’s toolbar to create a new connection.
This opens the Add a New Connection dialog.
Give the connection a name (e.g., Zephyr), then choose Zephyr Integration in the Connection Type drop-down field and Zephyr Cloud in the following drop-down field.
Step 4: Fill in the connection details.
Fill in the rest of the fields in the form using the values you gathered in Steps 1 & 2 above.
The Project Key is the prefix of all of your tests in Zephyr. For example, if your tests start with TEST- (e.g., TEST-0001), your Project Key is TEST. Change the JIRA endpoint to match your JIRA Cloud instance’s web address. The JIRA username is usually your email address. The Zephyr username is the name from the ZAPI System Key (see Step 2 above).
Step 5: Test the connection.
Use the Test Connection button to check that Provar can connect to your Zephyr Cloud instance.
Connecting to Zephyr Server
Step 1: Create a Zephyr Server connection in Provar.
In Provar Desktop, switch to the Test Settings view and open the Connections sub-tab. Click the plus sign icon in the view’s toolbar to create a new connection.
This opens the Add a New Connection dialog.
Give the connection a name (e.g., Zephyr), then choose Zephyr Integration in the Connection Type dropdown and Zephyr Server in the following dropdown.
Step 2: Fill in the Connection Details.
Fill in the rest of the fields in the form.
The project key is the prefix of all of your tests in Zephyr. For example, if your tests start with TEST- (e.g., TEST-0001), then your project key is TEST. Change the JIRA endpoint to match your JIRA server instance network address. The JIRA username is usually your email address.
Step 3: Test the connection.
Use the Test Connection button to check that Provar can connect to your Zephyr Cloud instance.
Uploading tests to Zephyr
This allows you to add test cases from Provar into Zephyr. You can also upload Zephyr tests with changes you’ve made to your Provar test cases.
Step 1: Open the Upload to Zephyr Cloud dialog.
From Provar’s Navigator view, right-click on the Tests folder and choose Upload to Zephyr.
Step 2: Choose the test cases to be uploaded.
Check the checkbox next to the test cases you want to upload, then click Upload.
Tips
You can use the filter field and checkboxes at the top of the dialog to find the test cases you want to upload.
- If you’re not seeing a test case you expect to be there, try clicking on the All Files checkbox.
- Clicking a folder’s checkbox will check or uncheck all of its child items
- The Zephyr Test column shows the existing Zephyr test that will be updated. You can use the link hyperlinks in the Actions column to update a different test.
Downloading tests into Provar
This allows you to add Zephyr tests to Provar. You can also update Provar test cases with changes you’ve made to your Zephyr tests.
Step 1: Open the Download to Zephyr Cloud dialog.
From Provar’s Navigator view, right-click on the Tests folder and choose Download to Zephyr.
Step 2: Choose the tests to be downloaded or uploaded.
Check the checkbox next to the Zephyr tests you want to download, and then click Download.
Tips
You can use the filter field and checkboxes at the top of the dialog to find the tests you want to download
- If you’re not seeing a test you expect to be there, try clicking the All Files checkbox.
- The Provar Test Case column shows the existing Provar test case that will be updated. You can use the link hyperlinks in the Actions column to update a different test case.
Create a Test Plan
Test Plans allow you to run your Provar test cases with features including Pie charts, PDF reports and/or Notification emails. You can also add Zephyr reporting to your Test Plans.
Step 1: Create a new Test Plan.
Click the drop-down arrow next to the New Test item in Provar desktop’s main toolbar and choose the New Test Plan option.
This opens the New Provar Test Plan wizard.
Fill in the Test Plan name and ensure that Zephyr Cloud or Zephyr Server is selected under Reporting before clicking Finish.
Step 2: Configure the Test Plan.
The New Test Plan wizard automatically opens the Test Plan for editing. If not, open it by double-clicking it in the Navigator view within the plans folder.
Configure the Test Plan by filling in the Zephyr version and Test Cycle you want your test cases reported into. You can also specify a folder. In the Navigator view, drag and drop the test cases you’d like to execute from the tests folder into the Test Plan.
Tips
- The version needs to exist in Zephyr.
- Provar will create missing Test Cycles and folders if the appropriate Create missing checkboxes are checked.
- Add Zephyr reporting to your existing Test Plans via the plus sign icon in the editor’s toolbar.
- The Enable Zephyr Cloud/Server reporting checkbox allows you to disable Zephyr reporting without removing its settings from the Test Plan.
Add a plan folder
You can further organize the test cases you execute by adding plan folders to your Test Plan.
Step 1: Create a new plan folder.
In the Navigator view, right-click on your Test Plan and choose New and then Provar Test Plan Folder.
This opens the New Plan Folder wizard. Fill in the plan folder name and click Finish.
Step 2: Configure the plan folder.
The New Plan Folder wizard automatically opens the plan folder for editing. If not, open it by double-clicking it in the Navigator view under the plans folder.
You can then configure the Zephyr settings for the plan folder by, for example, specifying a Zephyr folder. In the Navigator view, drag and drop the test cases you’d like to execute from the test folder into the plan folder.
Tips
- You can create as many levels of plan folders as you like. They can be nested inside each other.
- Any settings you leave blank will be inherited from any parent plan folder and/or the Test Plan.
Running the Test Plan
Step 1: Start the test run.
In the Navigator view, right-click the Test Plan (or one of its plan folders or test instances) and choose Run Test(s).
- The Test Plan (or plan folder or test instance) will start running in the Test Runner view.
- At the end of each test execution, the results will be reported into Zephyr against the version, Test Cycle, and folders specified in the Test Plan.
Appendix A: Creating a JIRA API token
Log on to your JIRA Cloud instance, click on your Profile, and choose Account Settings.
Choose Security from the menu on the left and then Create and Manage API tokens as shown.
Use the Create API Token button on the API tokens screen to create a new one and make a note of its value.
Appendix B: Creating a ZAPI key
Log on to JIRA Cloud and open JIRA settings from the menu pane on the left.
Choose System and then ZAPI. It is at the bottom of the System menu pane.
You will now be on the ZAPI Key Administration page, from where you can create a new System Key or copy the details of an existing one. Take note of the Name, Access Key, and Secret Key of the entry you want Provar to connect through.
- Provar Automation
- System Requirements
- Browser and Driver Recommendations
- Installing Provar Automation
- Updating Provar Automation
- Licensing Provar
- Granting Org Permissions to Provar Automation
- Optimizing Org and Connection Metadata Processing in Provar
- Using Provar Automation
- Understanding Provar’s Use of AI Service for Test Automation
- Provar Automation
- Creating a New Test Project
- Import Test Project from a File
- Import Test Project from a Remote Repository
- Import Test Project from Local Repository
- Commit a Local Test Project to Source Control
- Salesforce API Testing
- Behavior-Driven Development
- Consolidating Multiple Test Execution Reports
- Creating Test Cases
- Custom Table Mapping
- Functions
- Debugging Tests
- Defining a Namespace Prefix on a Connection
- Defining Proxy Settings
- Environment Management
- Exporting Test Cases into a PDF
- Exporting Test Projects
- Japanese Language Support
- Override Auto-Retry for Test Step
- Customize Browser Driver Location
- Mapping and Executing the Lightning Article Editor in Provar
- Managing Test Steps
- Namespace Org Testing
- NitroX
- Provar Test Builder
- ProvarDX
- Refresh and Recompile
- Reintroduction of CLI License Check
- Reload Org Cache
- Reporting
- Running Tests
- Searching Provar with Find Usages
- Secrets Management and Encryption
- Setup and Teardown Test Cases
- Tags and Service Level Agreements (SLAs)
- Test Cycles
- Test Data Generation
- Test Plans
- Testing Browser – Chrome Headless
- Testing Browser Options
- Tooltip Testing
- Using the Test Palette
- Using Custom APIs
- Callable Tests
- Data-Driven Testing
- Page Objects
- Block Locator Strategies
- Introduction to XPaths
- Creating an XPath
- JavaScript Locator Support
- Label Locator Strategies
- Maintaining Page Objects
- Mapping Non-Salesforce fields
- Page Object Operations
- ProvarX™
- Refresh and Reselect Field Locators in Test Builder
- Using Java Method Annotations for Custom Objects
- Applications Testing
- Database Testing
- Document Testing
- Email Testing
- Email Testing in Automation
- Email Testing Examples
- Gmail Connection in Automation with App Password
- App Configuration for Microsoft Connection in MS Portal for OAuth 2.0
- OAuth 2.0 Microsoft Exchange Email Connection
- Support for Existing MS OAuth Email Connection
- OAuth 2.0 MS Graph Email Connection
- Create a Connection for Office 365 GCC High
- Mobile Testing
- OrchestraCMS Testing
- Salesforce CPQ Testing
- ServiceMax Testing
- Skuid Testing
- Vlocity API Testing
- Webservices Testing
- Provar Manager
- How to Use Provar Manager
- Provar Manager Setup
- Provar Manager Integrations
- Release Management
- Test Management
- Test Operations
- Provar Manager and Provar Automation
- Setting Up a Connection to Provar Manager
- Object Mapping Between Automation and Manager
- How to Upload Test Plans, Test Plan Folders, Test Plan Instances, and Test Cases
- Provar Manager Filters
- Uploading Callable Test Cases in Provar Manager
- Uploading Test Steps in Provar Manager
- How to Know if a File in Automation is Linked in Test Manager
- Test Execution Reporting
- Metadata Coverage with Manager
- Provar Grid
- DevOps
- Introduction to Provar DevOps
- Introduction to Test Scheduling
- Apache Ant
- Configuration for Sending Emails via the Automation Command Line Interface
- Continuous Integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Automation secrets password in Microsoft Azure Pipelines
- Parallel Execution in Microsoft Azure Pipelines using Multiple build.xml Files
- Parallel Execution in Microsoft Azure Pipelines using Targets
- Parallel execution in Microsoft Azure Pipelines using Test Plans
- Bitbucket Pipelines
- CircleCI
- Copado
- Docker
- Flosum
- Gearset
- GitHub Actions
- Integrating GitHub Actions CI to Run Automation CI Task
- Remote Trigger in GitHub Actions
- Parameterization using Environment Variables in GitHub Actions
- Parallel Execution in GitHub Actions using Multiple build.xml Files
- Parallel Execution in GitHub Actions using Targets
- Parallel Execution in GitHub Actions using Test Plan
- Parallel Execution in GitHub Actions using Job Matrix
- GitLab Continuous Integration
- Travis CI
- Jenkins
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Version Control
- Salesforce Testing
- Recommended Practices
- Salesforce Connection Best Practices
- Improve Your Metadata Performance
- Java 21 Upgrade
- Testing Best Practices
- Automation Planning
- Supported Testing Phases
- Provar Naming Standards
- Test Case Design
- Create records via API
- Avoid using static values
- Abort Unused Test Sessions/Runs
- Avoid Metadata performance issues
- Increase auto-retry waits for steps using a global variable
- Create different page objects for different pages
- The Best Ways to Change Callable Test Case Locations
- Working with the .testProject file and .secrets file
- Best practices for the .provarCaches folder
- Best practices for .pageObject files
- Troubleshooting
- How to Use Keytool Command for Importing Certificates
- Installing Provar After Upgrading to macOS Catalina
- Browsers
- Configurations and Permissions
- Add Permissions to Edit Provar.ini File
- Configure Provar UI in High Resolution
- Enable Prompt to Choose Workspace
- Increase System Memory for Provar
- Refresh Org Cache Manually
- Show Hidden Provar Files on Mac
- Java Version Mismatch Error
- Unable to test cases, test suites, etc… from the Test Project Navigation sidebar
- Connections
- DevOps
- Error Messages
- Provar Manager 3.0 Install Error Resolution
- Provar Manager Test Case Upload Resolution
- Administrator has Blocked Access to Client
- JavascriptException: Javascript Error
- macOS Big Sur Upgrade
- Resolving Failed to Create ChromeDriver Error
- Resolving Jenkins License Missing Error
- Resolving Metadata Timeout Errors
- Test Execution Fails – Firefox Not Installed
- Selenium 4 Upgrade
- Licensing, Installation and Firewalls
- Memory
- Test Builder and Test Cases
- Release Notes