Skip to content

Files

Latest commit

 

History

History
94 lines (75 loc) · 3.75 KB

hyperexecute-cli-faqs.md

File metadata and controls

94 lines (75 loc) · 3.75 KB
id title hide_title sidebar_label description keywords url site_name slug
he-cli-faqs
CLI FAQs
true
CLI FAQs
Explore HyperExecute CLI FAQs Downloading Test Artifacts, MacOS Verification, Test Run Steps & More! Get Quick Answers Here.
LambdaTest Hyperexecute
LambdaTest Hyperexecute help
LambdaTest Hyperexecute documentation
FAQs
LambdaTest
hyperexecute-cli-faqs/
<script type="application/ld+json" dangerouslySetInnerHTML={{ __html: JSON.stringify({ "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.lambdatest.com" },{ "@type": "ListItem", "position": 2, "name": "Support", "item": "https://www.lambdatest.com/support/docs/" },{ "@type": "ListItem", "position": 3, "name": "Integrations", "item": "https://www.lambdatest.com/support/docs/hyperexecute-cli-faqs/" }] }) }} ></script>

HyperExecute CLI FAQs

1. Can HyperExecute CLI download test artifacts generated during execution?

Yes, HyperExecute can download the artifacts generated during the test execution. In addition, HyperExecute has APIs to download artifacts for a particular job.

2. I am not able to open HyperExecute on MacOS because the developer is not verified. What do I do?

<img loading="lazy" src={require('../assets/images/hyperexecute/faq/he-faq-1.png').default} alt="Image" className="doc_img"/>

The binary for Mac is unsigned. You might get a permission denied warning while executing HyperExecute on macOS and linux machines. To allow permissions you can use the following command: chmod u+x ./hyperexecute. Thus, you might see a security popup on whether to allow the execution of the tool or not. You can allow it from your System Preferences → Security & Privacy → General tab.

3. Is there a way where I can follow all of the steps in my test run on HyperExecute?

Every time you run a test via the HyperExecute CLI, a hyperexecute-cli.log file is generated. It is present in the parent directory of your test and contains the details of your entire test run.

This hyperexecute-cli.log file will also help you in debugging any issues with your tests. You can view the file and figure out exactly where your test run failed.

If you want more help with debugging your issues, you can always contact support@lambdatest.com and provide them with this file along with your Job ID.

<img loading="lazy" src={require('../assets/images/hyperexecute/faq/cli-log.png').default} alt="Image" className="doc_img"/>

For more information on the HyperExecute CLI, visit this page.

If you have more questions, then just give us a <span className="doc__lt" onClick={() => window.openLTChatWidget()}>shout and we will answer them for you.