Continuous Integration support (or lack thereof)

[nabijaczleweli]

You could use TravisCI, which is trivial to set up. I think the following .travis.yml would suffice:

sudo: false
language: cpp
compiler:
  - gcc
  - clang

script: make

[Zorgatone]

That would see if it builds, but of course won't be able to run the tests :stuck_out_tongue_closed_eyes:

Still better than nothing, right?

[nabijaczleweli]

You could echo -e "XXXXXXXWSAD WSAD \x1b[A\x1b[B\x1b[C\x1b[D\x1bXXXX" | ./test, in theory, but it hangs on non-blocking input

[Zorgatone]

Anyway you won't "see" the terminal, that's the visual part that would need testing. So this part can't be automated. The build part can at least

[nabijaczleweli]

You can download and pipe the build output through your terminal after the tests, though (as much as non-automated that is)

[Zorgatone]

That's what I meant by non-automated :sweat_smile:

[nabijaczleweli]

You could, also, redirect the output to a file and then compare the output, as horrible to maintain as that might be.

[Zorgatone]

@nabijaczleweli commented on 20 nov 2015, 14:15 CET:

You could, also, redirect the output to a file and then compare the output, as horrible to maintain as that might be.

LOL

[refi64]

@nabijaczleweli Well, you'd be surprised how many people do that!

[nabijaczleweli]

I know, it's just very implementation-dependent, and that's just bad

[nabijaczleweli]

@tapio plz

[nabijaczleweli]

You could, actually, also autoupdate the docs with this