automation

Discussed in microsoft/playwright#11891

Most of the documentation has been rewritten recently. The content minimum content we need is there but there is a lot that can be done to improve it.

If you'd like to contribute to the semantic-release project, helping with the following would be much appreciated:

• Fix typo, misspelling and gramatical mistakes
• Improve language: make short and simpler sentences, improve clarity
• Harmoniz

Support using="-android viewmatcher", value="<JSON>"

appium/appium-espresso-driver#516

like appium/appium#12372

Acceptance Criteria:

• Ruby
• Python
• Java
• C#
• WebdriverIO ?
• wd ?

Is there an existing issue for this?

• I have searched the existing issues

Description

When I click on datasource from the left panel, a message appears saying "No information available". It's no clear what information is missing or whether it's a problem or not. It should either be removed or we should show something e.g. base url of the API here.
<img width="354" alt="Screenshot

Please confirm the following

• I agree to follow this project's code of conduct.
• I have checked the current issues for duplicates.
• I understand that AWX is open source software provided for free and that I might not receive a timely response.

Summary

when us

Description

Occasionally I get the following error when running sub-flows using create_flow_run and wait_for_flow_run

Task "wait_for_flow": Exception encountered during task execution!
Traceback (most recent call last):
  File "/root/miniconda3/lib/python3.8/site-packages/prefect/engine/task_runner.py", line 876, in get_task_run_state
    value = prefect.utilities.executor

Specs

• Leon version: latest
• OS (or browser) version: Fedora 30
• Node.js version: 10.16.3
• Complete "npm run check" output:

➡ Here is the diagnosis about your current setup
✔ Run
✔ Run modules
✔ Reply you by texting
❗ Amazon Polly text-to-speech
❗ Google Cloud text-to-speech
❗ Watson text-to-speech
❗ Offline text-to-speech
❗ Google Cloud speech-to-text
❗ Watson spee

Hi, I came across strange behaviour of RF regarding embedded arguments. I have keyword

Perform ${arg:[^ ]+}
    Log To Console  ${arg}

In other words, the argument cannot contain any space. Then, Perform abcd passes, as it contains no space. Perform ab cd fails with No keyword with name 'Perform ab cd' found, since it does contain a space. So far so good. But when I set the valu