Convert tests to unittest

[christian-intra2net]

Sofar, there was a simple tests.sh script for testing, that required msoffcrypto-tool was already installed.

Converted that script to a python unittest that performs the same action but can run without installing msoffcrypto-tool

Renamed dir tests to test because when building rpms/source tarballs using setup.py, "test" is the hard-coded name where tests are expected. Should be included that way

[christian-intra2net]

I just realized a MANIFEST.in is required to include the test data into the distribution tarball ("python setup.py sdist"). That means that moving "tests" to "test" was unnecessary. I will therefore revert the first commit and instead add the test source code to the MANIFEST

[codecov-io]

Codecov Report

Merging #28 into master will increase coverage by 50.04%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master      #28       +/-   ##
===========================================
+ Coverage   36.68%   86.72%   +50.04%     
===========================================
  Files          13       13               
  Lines        1145     1145               
===========================================
+ Hits          420      993      +573     
+ Misses        725      152      -573

Impacted Files	Coverage Δ
msoffcrypto/method/ecma376_standard.py	98.21% <0%> (+17.85%)	⬆️
msoffcrypto/format/ooxml.py	78.12% <0%> (+31.25%)	⬆️
msoffcrypto/method/ecma376_agile.py	90% <0%> (+36%)	⬆️
msoffcrypto/__init__.py	78.26% <0%> (+39.13%)	⬆️
msoffcrypto/format/xls97.py	87.5% <0%> (+48.12%)	⬆️
msoffcrypto/format/doc97.py	88.69% <0%> (+58.26%)	⬆️
msoffcrypto/method/rc4_cryptoapi.py	95.23% <0%> (+61.9%)	⬆️
msoffcrypto/format/ppt97.py	98.86% <0%> (+70.45%)	⬆️
msoffcrypto/format/common.py	100% <0%> (+77.77%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8689b89...f20cfad. Read the comment docs.

[nolze]

Amazing! Thank you so much.

While the library usage of msoffcrpyo-tool is now nicely covered by your new tests, I intended to test the CLI usage of the tool using tests.sh.

That is, ideally there should be:

1. a few illustrative unit tests with doctest (w.r.t. internal and library usage),
2. comprehensive unit/integration tests for all sample documents with unittest (w.r.t. library usage, your contribution to the latter here),
3. integration tests for all or some documents with a shell script (w.r.t. CLI usage).

So, my suggestion is to merge your PR preserving tests.sh. Concerning your point, I think that changing msoffcrypto-tool in tests.sh to python -m msoffcrypto we will no longer need to install it prior to testing.

[christian-intra2net]

Glad you like it :-)
I did think about creating a unittest that just runs tests.sh line by line using subprocess.check_output. Then decided that the way I implemented is easier and does almost the same.
But you're the boss, I will modify this branch

[nolze]

Merged! I'll release a new version with this update soon.

[christian-intra2net]

Cool :-) Thanks