Conversation
2b7b8cd to
ea7620d
Compare
|
I managed to install bats but the git tags of the vimpager repository are not available on travis and they are needed to get the correct version output. @rkitover any ideas? |
Add a comment to the top of vimpager and vimcat with the current release version, and use it in --version output when git describe has failed.
|
@lucc sorry things have been difficult here, but I'm slowly getting back into things. Does the above commit help you? |
Adjust valid version glob pattern from `[0-9]*` to `[0-9].`, this makes sure that git describe picked up an actual tag.
|
@lucc made a minor adjustment to make sure a tag is picked up above. |
|
@rkitover I don't really like the solution. If we really need to supply a fallback version number I would suggest something like 5438492. (But the makefile is not yet updated with that commit.) In my opinion it would be better to solve this issue on Travis. Like this we introduce additional code paths just for the test. That means we don't test the normal code paths at all. |
|
Also: The first question we should answer here is if we want to use bats and keep these tests? Otherwise we have to decide a new test framework and re-implement these tests. |
|
@lucc check this out: https://travis-ci.org/rkitover/vimpager/builds/138622907 so all you need to do is stick re: 5438492
re: this PR I haven't had a chance to look at the code yet, BATS is what I wanted to use, so that's good, I'll try to read the commits later today. I'm dealing with an eye infection, back and knee pain and lots of other horrible shit right now. |
4b3714f to
dd83f2b
Compare
|
I think I fixed the travis build. The core problem was that Please do not merge yet, I am still cleaning up the git history and testing more stuff. |
8bfcdba to
50f8c2e
Compare
d210bc3 to
87d4810
Compare
|
@rkitover The history is still not clean but that is only because there is a question that came up: The file We could either replace the call to What do you think? Are the new version of lintian or the override needed for some other reason? Other than that and adding however many tests this PR is done (from my point of view). |
|
I also pushed https://github.com/rkitover/vimpager/tree/test2 . I will open a PR for that as soon as this one is merged, as it is a child of this one. But you can already have a look. |
742e8eb to
b383415
Compare
Add support for `make install-deb CLEAN_BUILD_DEPS=0` to not run `apt-get autoremove` so that build dependencies are not removed.
|
@lucc the reason for If the new lintian is complaining that the standards version is too old, we should update the standards version in debian/ . If there are incompatibilies with the latest standards version then I will fix them. Also why am I not seeing this issue on master? I added support for not removing build deps in sudo make install-deb CLEAN_BUILD_DEPS=0 DEB_BUILD_OPTIONS=nocheckthen you can run |
- Move `make install-deb` to the script step as it runs the tests. - Install uuencode (package sharutils) explicitly as it is needed during testing. Formally it was implicitly installed by `make install-deb`. - Install bats manually as there is no package for it on trusty. - Remove bats building directory as it is reported by lintian. - Fetch git tags as they are needed to run the tests. - Run `make all`. - Add a modeline.
|
Thanks for the info. I added that and do now consider ths PR done. Feel free to merge if you don't have further comments. |
|
@lucc finally read the actual tests, awesome stuff! Merging. |
Replace script -q -e -c invocation in bats tests with the run_cmd helper which uses a more portable invocation of script(1) which works on OS X, Ubuntu and OpenBSD.
|
@lucc I made some changes to call script(1) in a more portable way. Tests now pass on OS X, Ubuntu, OpenBSD and FreeBSD. |
|
Nice, I opend #196 as a followup. |
This is an attempt to finish #180.
When reviewing #193 it suddenly came to me that
scriptcould be used to capture the help and version output at least. Like this:script -c './vimpager -h' -e -q. This pattern is used with the bats test framework.The decision between bats and roundup is rather arbitrary. I went ahead and used bats because roundup is not available in the Arch repos and that is what I use vor development. If that is unadaptable I can also convert these tests to another test suite.
PS: I don't really understand why travis fails to install bats. Can we somehow force the build to restart without pushing to this branch?