At the moment commands are extracted from directory names during tests. It works nice when the command does not have any 'special' characters in it. But some commands do have 'special' characters. For example, command :put [:resolve ...] on mikrotik_routeros. On LInux it's ok but Windows won't even allow to make a directory/file with such characters in the name.
Even if we are going to use only Linux, it's still broken here cause glob treats square brackets specially.
Maybe it makes sense to add a new file with the *.cmd extension (similar to current *.raw, *.yml) with the test command in it. Or another way to use tests for commands with 'special' characters.
At the moment commands are extracted from directory names during tests. It works nice when the command does not have any 'special' characters in it. But some commands do have 'special' characters. For example, command
:put [:resolve ...]onmikrotik_routeros. On LInux it's ok but Windows won't even allow to make a directory/file with such characters in the name.Even if we are going to use only Linux, it's still broken here cause
globtreats square brackets specially.Maybe it makes sense to add a new file with the
*.cmdextension (similar to current*.raw,*.yml) with the test command in it. Or another way to use tests for commands with 'special' characters.