For BitShuffle to be of maximum utility, it should run on a wide variety of platforms, including MS Windows. While it should work, we should have some basic smoke testing for Windows to ensure it continues to do so.
It is not necessary to run through every test case, just enough to demonstrate that it can run without crashing and do a basic encode/decode test.
The specific feature that should be tested are:
Run and display the version with --version without crashing.
Encode a file from --input, writing the encoded data to a temp file with --output; run another BitShuffle instance and have it do the reverse.
Encode a file from --input, pipe to another instance, decode, and write out with `--output``.
Encode a file from standard in, pipe to another instance, decode, and write to standard out.
I have some experience with doing CI on Windows systems, so I will handle this one myself.
I will probably use AppVeyor unless someone has a different suggestion?
charlesdaniels
commented
6 years ago
For BitShuffle to be of maximum utility, it should run on a wide variety of platforms, including MS Windows. While it should work, we should have some basic smoke testing for Windows to ensure it continues to do so.
It is not necessary to run through every test case, just enough to demonstrate that it can run without crashing and do a basic encode/decode test.
The specific feature that should be tested are:
--versionwithout crashing.--input, writing the encoded data to a temp file with--output; run another BitShuffle instance and have it do the reverse.--input, pipe to another instance, decode, and write out with `--output``.I have some experience with doing CI on Windows systems, so I will handle this one myself.
I will probably use AppVeyor unless someone has a different suggestion?