Add RPC-based tests

[zachriggle]

(Note: Duplicate of #170 with the PR coming from my fork)

Allow testing Pwndbg itself by embedding an XMLRPC server inside the GDB instance, which exposes both the gdb and pwndbg modules, as well as eval.

Since the default XMLRPC behavior is terrible and doesn't know how to marshall any of the following:

• bytearray object
• bytes object
• str or unicode with embedded \x00

We hack both the Marshaller and Unmarshaller to support a new datatype.

[disconnect3d]

Do I understand correctly that the idea behind this is to be able to launch unit tests over easily testable functions (the ones that doesn't need running program under the hood)? As I guess we won't want to mock everything around (pwndbg.proc.*, getting memory and stuff).

Do we really need it so complicated? I mean, we probably could have something like:

• launch gdb
• send a pi import pwndbg.tests; pwndbg.tests.run()
• gather results

At least for the functions that doesn't need a process under the hood (well we could mock stuff but it might be painful/hard?).

We could also start with having some end to end tests that would be produced manually, launched with predefined environment (envvars, config, theme) and just checked for this exact output for given list of commands.
E2E tests could also hook some interesting functions - the ones that instead of printing return specific values (e.g. list of Page objects etc).

[zachriggle]

Won’t work. GDB exits with code zero even if Python throws an exception. Hacking around this is more work than just exposing the Pwndbg module over RPC to allow “import pwndbg” outside of GDBpython.

…

On Sat, Nov 25, 2017 at 7:32 AM Disconnect3d ***@***.***> wrote: Do I understand correctly that the idea behind this is to be able to launch unit tests over some fancy functions? Do we really need it so complicated? I mean, we probably could have something like: - launch gdb - send a pi import pwndbg.tests; pwndbg.tests.run() - gather results — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#254 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAG0GHw3i_h7y5cVD1q9rEF8E0dlgUsMks5s6DMmgaJpZM4NMEVC> .

[disconnect3d]

@zachriggle still how are we going to test commands that use gdb api? By mocking it?
This won't us check easily whether pwndbg works fine with particular gdb version.

[zachriggle]

Nope, by actually running GDB and exposing it (also) over XMLRPC.

…

On Sun, Nov 26, 2017 at 8:06 AM Disconnect3d ***@***.***> wrote: @zachriggle <https://github.com/zachriggle> still how are we going to test commands that use gdb api? By mocking it? This won't us check whether pwndbg works fine with particular gdb version. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#254 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAG0GPHeCyQfWl9rGnlFfo-p3FXEgb1Kks5s6YyKgaJpZM4NMEVC> .

[disconnect3d]

Guess this can be closed due to #375 ?