aboutsummaryrefslogtreecommitdiffstats
path: root/tests/transaction_test.go
Commit message (Collapse)AuthorAgeFilesLines
* tests: updated homestead testsJeffrey Wilcke2016-02-181-1/+23
|
* all: fix license headers one more timeFelix Lange2015-07-241-1/+1
| | | | I forgot to update one instance of "go-ethereum" in commit 3f047be5a.
* all: update license headers to distiguish GPL/LGPLFelix Lange2015-07-231-4/+4
| | | | | All code outside of cmd/ is licensed as LGPL. The headers now reflect this by calling the whole work "the go-ethereum library".
* all: update license informationFelix Lange2015-07-071-0/+16
|
* Add --skip option to CLITaylor Gerring2015-06-191-3/+3
| | | | | Disassociates hardcoded tests to skip when running via CLI. Tests still skipped when running `go test`
* More consistent test interfaces + test skippingTaylor Gerring2015-06-191-22/+3
|
* Cleanup/reorgTaylor Gerring2015-06-191-2/+0
|
* Fix pathsTaylor Gerring2015-06-191-3/+6
|
* Add bcTotalDifficultyTest and unskip now working tx testsGustav Simonsson2015-05-071-5/+1
|
* Exclude TransactionWithSvalue0 as it expects invalid s value to be validGustav Simonsson2015-04-231-0/+1
|
* Explicitly skip TransactionTests/tt10mbDataField.jsonGustav Simonsson2015-04-231-5/+2
|
* Fixes for TransactionTestsGustav Simonsson2015-04-161-11/+18
| | | | | | | | | * Include tests which now has consistent HEX encodings * Comment out two failing tests: " "TransactionWithHihghNonce" due to wrong nonce size "TransactionWithSvalueHigh" due to wrong ECDSA s range * Cleanup conversion functions and fix expected encodings for tests validation fields
* Enable more tx tests by expecting most common encoding of valuesGustav Simonsson2015-04-101-9/+2
|
* Remove unneeded map assignments for working tx RLP testsGustav Simonsson2015-04-101-7/+0
|
* Add TransactionTests wrapped as Go testsGustav Simonsson2015-04-101-0/+58
* Add initial go wrapping for TransactionTests with some tests disabled in lieu of consistent HEX encodings and a few other pending bugfixes * TODO: Consider better way of perhaps modelling each test in the JSON files as a single Go test, instead of one Go test per JSON file