tahoe-lafs/integration
meejah a0fc80d544 Use "python -m allmydata.scripts.runner" instead of tahoe.exe
On windows, it seems that the generated tahoe.exe (which comes
via entry_points=) doesn't deal with signals nicely. I'm not
sure if this is a pip bug (or just "one of those Windows things")
but running with python -m allows us to kill our subprocesses.
2016-09-26 13:33:45 -07:00
..
conftest.py Use "python -m allmydata.scripts.runner" instead of tahoe.exe 2016-09-26 13:33:45 -07:00
README Move check_magicfolder_smoke.py to proper integration tests 2016-08-30 20:47:47 -06:00
test_aaa_aardvark.py Move check_magicfolder_smoke.py to proper integration tests 2016-08-30 20:47:47 -06:00
test_smoke.py Move check_magicfolder_smoke.py to proper integration tests 2016-08-30 20:47:47 -06:00
util.py Move check_magicfolder_smoke.py to proper integration tests 2016-08-30 20:47:47 -06:00

Install:

   pip install -e .[test]

run:

   py.test -s -v integration/

If you want to keep the created temp-dir around:

   py.test --keep-tempdir -v integration/

The fixtures also set up a "flogtool gather" process and dump all the
logs from all the running processes (introducer, 5 storage nodes,
alice, bob) to a tempfile.