[
https://issues.apache.org/jira/browse/IGNITE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350200#comment-14350200
]
Vasilisa Sidorova commented on IGNITE-185:
------------------------------------------
Ubuntu 14.04/Windows7 Ignate Fabric Only Build #119 for ignite-185 branch (ver.
1.0.0-RC2-SNAPSHOT#20150305-sha1:d8ee19a5):
Now all works fine: verify for several types of file (created from different
editors with different encodings) except encoding UTF-16.
You can see the results for that files in the attachment
"runVisorcmdWithUTF16FileResults". Input files "withExit_akelpad_UTF16" and
"withoutExit_UTF16.txt" are also attached.
I'm not sure should it be fixed - it seem like very rare user's scenario.
> Batch mode for Visorcmd
> -----------------------
>
> Key: IGNITE-185
> URL: https://issues.apache.org/jira/browse/IGNITE-185
> Project: Ignite
> Issue Type: Task
> Components: UI
> Affects Versions: sprint-1
> Reporter: Alexey Kuznetsov
> Assignee: Vasilisa Sidorova
> Fix For: sprint-2
>
> Attachments: runVisorcmdWithFileResults, withExit
>
>
> Batch mode for visorcmd allow to read commands from test file (one command
> per line), perform them, send output to STDOUT/STDERR and exit if end of text
> file has been reached.
> e.g. ./bin/ggvisorcmd -b path_to_batch_file
> For this case the output of visorcmd will be stored into the file and test
> scripts can compare content of this file against expected result.
> Expected troubles for implementing is requests of confirmation/parameters for
> some commands (e.g. "kill" - confirm to kill, "open" - set number of config
> file). But can be resolved by following ways:
> next line after such command contains text for request, e.g.
> open
> 14
> kill
> y
> after command inside brackets we put text for request
> open {14}
> kill
> {y}
> do not ask confirmation if visorcmd started in batch mode (but how to resolve
> commands like "open"?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
