| Rule - 0201 [W]: missing-doc-keyword: Missing documentation in '{{ name }}' keyword | |
| Rule - 0202 [W]: missing-doc-test-case: Missing documentation in '{{ name }}' test case | |
| Rule - 0203 [W]: missing-doc-suite: Missing documentation in suite | |
| Rule - 0204 [W]: missing-doc-resource-file: Missing documentation in resource file | |
| Rule - 0301 [W]: not-allowed-char-in-name: Not allowed character '{{ character }}' found in {{ block_name }} name | |
| Rule - 0302 [W]: wrong-case-in-keyword-name: Keyword name '{{ keyword_name }}' does not follow case convention | |
| Rule - 0303 [E]: keyword-name-is-reserved-word: '{{ keyword_name }}' is a reserved keyword{{ error_msg }} | |
| Rule - 0305 [W]: underscore-in-keyword-name: Underscores in keyword name '{{ keyword_name }}' can be replaced with spaces | |
| Rule - 0306 [W]: setting-name-not-in-title-case: Setting name '{{ setting_name }}' should use title or upper case | |
| Rule - 0307 [W]: section-name-invalid: Section name should be in format '{{ section_title_case }}' or '{{ section_upper_case }}' |
If you have a company-managed OneDrive account like I do, you probably will never need or want to access a personal OneDrive account. It clutters up the Explorer menu and it's likely that you would prefer not to see it.
regedit in the start menu and it should come up (select it)Computer paste the following to the right of it (i.e., don't delete Computer):\HKEY_CLASSES_ROOT\CLSID\{018D5C66-4533-4307-9B53-224DE2ED1FE6}
| { | |
| "Test Suite": { | |
| "prefix": "suite", | |
| "body": [ | |
| "*** Settings ***", | |
| "Documentation ${1:What does this testing suite cover?}\n", | |
| "Library String # just an example", | |
| "Library \\${EXECDIR\\}/path/to/CUSTOM_LIBRARY.py", | |
| "Resource \\${EXECDIR\\}/path/to/NAME_OF_ANOTHER.resource\n", | |
| "Suite Setup SETUP_HERE", |
| { | |
| "version": "0.2.0", | |
| "configurations": [ | |
| { | |
| "name": "Robot Framework: Launch Template", | |
| "type": "robotframework-lsp", | |
| "request": "launch", | |
| "terminal": "integrated", | |
| "env": { | |
| "SOME_KEY": "Some value", |
Typora supports syntax coloring for code fences, and lists those languages on one of its support pages.
However, the list is not alpha sorted, so it's difficult to discover what languages are there unless one tries a ⌘-f/⌃-f to search for it.
I decided to help myself out and sort the list and post it in this Gist.
This should get you up and running with the installation and basic configuration of GNU Nano on both macOS and Windows. In the case of macOS, this will install a newer version of Nano that includes syntax highlighting.
It is assumed you already have Homebrew installed. If not, then Verify or Install Apple's Command-line Tools and then proceed with the installation of Homebrew. 🍺
U+238BU+21E5U+21EAU+21E7U+2303U+2325U+F8FF (in some Apple-provided fonts only)U+2318
This isn't a guide about locking down homebrew so that it can't touch the rest of your system security-wise.
This guide doesn't fix the inherent security issues of a package management system that will literally yell at you if you try to do something about "huh, maybe it's not great my executables are writeable by my account without requiring authorization first".
But it absolutely is a guide about shoving it into its own little corner so that you can take it or leave it as you see fit, instead of just letting the project do what it likes like completely taking over permissions and ownership of a directory that might be in use by other software on your Mac and stomping all over their contents.
By following this guide you will:
sudo to forcefully change permissions of some directory to be owned by your account
I recently answered this question on the Robot Framework forum.
For switching between runtime environments, my go-to is to create YAML files that encapsulate essential differences between environments. If you focus on just the things that change, then your maintenance load will be lower.
I like YAML because you can represent the 3 primitive data types supported:
This is a short tutorial on how to leverage Robot Framework's built-in support for documentation. This documentation can be embedded in test suites, libraries, and other resource files. The markup is fairly simple, and most closely resembles AsciiDoc syntax.
The official documentation explains the use of the Library documentation tool (Libdoc), its correspondent for Test data documentation (Testdoc), as well as the Documentation formatting syntax. Please use these references as the official word on how to