10 Commits (fa524d9ddbad0a03f9eb974100fb3b6001045645)

Author	SHA1	Message	Date
MarcoFalke	7777994846	[qa] Fix pyton syntax in rpc tests	9 years ago
MarcoFalke	fa24439ff3	Bump copyright headers to 2015	9 years ago
Jonas Schnelli	64937fe51a	[QA] restructure rpc tests directory ... * move non-test classes to subdir `test-framework`	10 years ago
Pieter Wuille	6b04508e37	Introduce separate 'generate' RPC call	10 years ago
Matt Corallo	e3f315a0a5	Fix python usage for arch's broken maintainers	10 years ago
Cory Fields	5122ea7190	tests: fix forknotify.py on windows ... Windows interprets 'foo.txt' as a literal filename while "foo.txt" is treated as expected.	10 years ago
Wladimir J. van der Laan	b6c99efe9c	Merge pull request #5121 ... 214091d Update license in pull-tester and rpc-tests (Michael Ford)	10 years ago
Daniel Kraft	dcb98466b4	Extend getchaintips RPC test. ... Add the capability to simulate network splits to the RPC test framework and use it to do more extensive testing of 'getchaintips'.	10 years ago
Michael Ford	214091d584	Update license in pull-tester and rpc-tests ... Add missing copyright/license header where necessary	10 years ago
Gavin Andresen	dbca89b74b	Trigger -alertnotify if network is upgrading without you ... 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	10 years ago