`cargo test` failed due to difference in command output on windows environment

[StoneDot]

On the Windows environment, the cargo test command fails because of snapshot test failure;

Testing tests\cmd\bwrite.md:4 ... failed
Exit: success

---- expected: stdout
++++ actual:   stdout
   1      - dy-bwrite 0.2.1
        1 + dy[EXE]-bwrite 0.2.1
   2    2 | Put or Delete multiple items at one time, up to 25 requests. [API: BatchWriteItem]
   3    3 | 
   4    4 | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_BatchWriteItem.html
   5    5 | 
   6    6 | USAGE:
   7      -     dy bwrite [OPTIONS] --input <input>
        7 +     dy[EXE] bwrite [OPTIONS] --input <input>
   8    8 | 
   9    9 | FLAGS:
  10   10 |     -h, --help       
  11   11 |             Prints help information
  12   12 | 
          ⋮
  26   26 |             --region option in both top-level and subcommand-level
  27   27 |     -t, --table <table>      
  28   28 |             Target table of the operation. You can use --table option in both top-level and subcommand-level. You can
  29   29 |             store table schema locally by executing `$ dy use`, after that you need not to specify --table on every
  30   30 |             command
stderr:

We should consider a way to absorb this type of difference.

[StoneDot]

175 solved this issue.