Self-tests for travis.debian.net

[evgeni]

Ohai,

I think it would be nice if we would be able to test ourself on Travis, no?

Greets
Evgeni

[lamby]

Not 100% sure what you mean, sorry; could you clarify?

[evgeni]

If I currently submit a PR, editing script.sh, there is nothing that will actually check that my changes work as intended. My idea was to have a .travis.yaml (similar to the one that gets used in other packages) which creates a minimal package and then executes script.sh on that source, thus building it and ensuring proper function of script.sh

[lamby]

Good point, but without testing all the variations (sid/wheezy/autopkgblah) I fear that a minimal package won't provide that much over a simple smoke tests that I run anyway... ie. it won't really be testing the proper function of script.sh, alas. Besides, most of the changes since the beginning have been for edge-cases or new features which — by definition — would not be caught by such as minimal test. Hm.

[evgeni]

My usecase (in #23, #24, #25) was that I had to:

• have a package/git prepared for using travis.d.n
• have a fork of your repo
• change my package to use my fork instead of yours
• push my changes to my fork
• run build of my package
• repeat the last two steps for every fix I did

that was kinda tiresome, but I really wanted that feature, so I continued :D -- and yes, I broke even simple builds while working on that. (and so did you in #21 :P)
having a test.sh that would execute a sid build on an example package would have helped here
and if we have such a test.sh, we can also run it on travis :)