disable cram tests on Windows

[guillermooo]

Disable tests that always fail on Windows.

I've included a very basic implementation of skipIf for older versions of Python so that the tests at least can run. Let me know if you think it's good enough.

[arcivanov]

This is a mock test that doesn't execute anything. No reason to disable those tests.

[arcivanov]

I'm confused. The cram tests do not actually invoke cram - all of the calls are mocked out. Why are we trying to exclude them, again?

[guillermooo]

@arcivanov IIRC they were causing errors on Windows for some reason. I'm not very familiar with the pybuilder codebase, though, so I'll doublecheck the output.

[esc]

Getting things to run on appveyor might shed some more light on this?

[AlexeySanko]

Hi, guys.

When I were .... young I tried to create developing PyBuilder process available for Windows. After a huge of ...... experience I installed VirtualBox with Ubuntu. :)))

1. So cram unittests fail because Windows has other paths format. So you can find addopted unittest file there
   Of course this file could be used only for comparison (!!!)

2. Cram could work on Windows. But You need modify local cram:
   a) take windows addopted cram sources
   So I created corresponding pull request for cram, but now I'm not sure that it's good idea :)
   b) compile cram.exe file and place it to bin (Scripts) folder. I used tool called PyInstaller
   Do not forget do change cram test - Windows cmd.exe utility has specific header. :)))

As you can see into my branch for Windows we need to do a lot of changes into unitests. And into integration tests (I didn't do it). And create separated tests for Unix and Windows (for coverage). And support all this stuff after that. In result I'm not sure that it's good idea.

[arcivanov]

Fixed in and obsoleted by #648