Closed TethysSvensson closed 8 years ago
Working on this at the moment. The idea is that there'll be a group of binaries hosted on a DigitalOcean droplet, which is running a custom service to allow various peeks/pokes/writes/overflows. We should be able to test everything that qemu-user
can run.
This is in progress here: https://github.com/zachriggle/pwntools-regression/
Should we close this, or keep it open until we have merged the regression testing into the main repo?
I'd leave it open until Travis is actually running those tests
This is complete and actually used via shellcraft via run_assembly()
and similar.
We already have doctests for testing most stand alone features and the repo Gallopsled/pwntools-write-ups tests most larger features (or will eventually). However none of these would every hit every shellcode or every way a shellcode can be used.
It would be awesome to be able to test the shellcodes in a systematic way.
Ideally we would want both functionality testing (e.g. test that findpeersh actually finds the right socket) and strace/similar based testing.