aboutsummaryrefslogtreecommitdiff
path: root/qa/rpc-tests/forknotify.py
AgeCommit message (Collapse)Author
2016-05-15[qa] Remove hardcoded "4 nodes" from test_frameworkMarcoFalke
2016-05-05[qa] Switch to py3MarcoFalke
2016-01-13[qa] Fix pyton syntax in rpc testsMarcoFalke
2015-12-13Bump copyright headers to 2015MarcoFalke
2015-05-18[QA] restructure rpc tests directoryJonas Schnelli
* move non-test classes to subdir `test-framework`
2015-04-01Introduce separate 'generate' RPC callPieter Wuille
2014-11-27Fix python usage for arch's broken maintainersMatt Corallo
2014-10-31tests: fix forknotify.py on windowsCory Fields
Windows interprets 'foo.txt' as a literal filename while "foo.txt" is treated as expected.
2014-10-27Merge pull request #5121Wladimir J. van der Laan
214091d Update license in pull-tester and rpc-tests (Michael Ford)
2014-10-24Extend getchaintips RPC test.Daniel Kraft
Add the capability to simulate network splits to the RPC test framework and use it to do more extensive testing of 'getchaintips'.
2014-10-23Update license in pull-tester and rpc-testsMichael Ford
Add missing copyright/license header where necessary
2014-10-09Trigger -alertnotify if network is upgrading without youGavin Andresen
This adds a -regetest-only undocumented (for regression testing only) command-line option -blockversion=N to set block.nVersion. Adds to the "has the rest of the network upgraded to a block.nVersion we don't understand" code so it calls -alertnotify when 51 of the last 100 blocks are up-version. But it only alerts once, not with every subsequent new, upversion block. And adds a forknotify.py regression test to make sure it works. Tested using forknotify.py: Before adding CAlert::Notify, get: Assertion failed: -alertnotify did not warn of up-version blocks Before adding code to only alert once: Assertion failed: -alertnotify excessive warning of up-version blocks After final code in this pull: Tests successful