Dave Hibberd <hi...@debian.org> writes: > > Spent an hour or so trying to do some autotools magic to get compilation to a > stage where it won't compile as `ronn` is required.
the previous version did not use autotools, so that is at least part of the mystery solved. The autopkgtests were not updated when the upstream build system was. > In my opinion, adding lots > of dependencies to entirely rebuild the application so we can "test" it seems > way beyond the scope of any testing. > We can also see the tests run during build [1]. Is there value in repeating > them? It is a common practice to make sure the installed version is actually installed properly > Running prove appears easier on the face of it, but I ran into a wall there > too: all the tests as shipped seem to be hardcoded to `.././vcsh` or > `./vcsh`, > not calling the shipped binary. Is that normal? yes, for build time tests > Copying them to d/tests and updating d/tests/control has so far not proved > fruitful for me either, missing files errors and other things. This is probably the path I would try. You could replace some tests as long as you end up testing roughly the same functionality. > Any hints or tips, can I even drop the whole d/tests folder to avoid having > tests happen to clear the bug? It's not usually acceptable to drop autopkgtests in order to avoid failures.
