Removed LevelDB changes

Syntax Highlighting
willcl-ark · May 1, 2014 · d3081fa · d3081fa
1 parent 4a102fa
commit d3081fa
Show file tree

Hide file tree

Showing 2 changed files with 20 additions and 13 deletions.
diff --git a/qa/rpc-tests/README.md b/qa/rpc-tests/README.md
@@ -1,22 +1,26 @@
 Regression tests of RPC interface
 =================================
 
-python-bitcoinrpc: git subtree of https://github.com/jgarzik/python-bitcoinrpc
+### [python-bitcoinrpc](https://github.com/jgarzik/python-bitcoinrpc)
+Git subtree of [https://github.com/jgarzik/python-bitcoinrpc](https://github.com/jgarzik/python-bitcoinrpc).
 Changes to python-bitcoinrpc should be made upstream, and then
-pulled here using git subtree
+pulled here using git subtree.
 
-skeleton.py : Copy this to create new regression tests.
+### [skeleton.py](skeleton.py)
+Copy this to create new regression tests.
 
-listtransactions.py : Tests for the listtransactions RPC call
+### [listtransactions.py](listtransactions.py)
+Tests for the listtransactions RPC call.
 
-util.py : generally useful functions
+### [util.py](util.sh)
+Generally useful functions.
 
 Bash-based tests, to be ported to Python:
 -----------------------------------------
-wallet.sh : Exercise wallet send/receive code.
-walletbackup.sh : Exercise wallet backup / dump / import
-txnmall.sh : Test proper accounting of malleable transactions
-conflictedbalance.sh : More testing of malleable transaction handling
+- wallet.sh : Exercise wallet send/receive code.
+- walletbackup.sh : Exercise wallet backup / dump / import
+- txnmall.sh : Test proper accounting of malleable transactions
+- conflictedbalance.sh : More testing of malleable transaction handling
 
 Notes
 =====
@@ -32,5 +36,8 @@ test state.
 
 If you get into a bad state, you should be able
 to recover with:
-  rm -rf cache
-  killall bitcoind
+
+```bash
+rm -rf cache
+killall bitcoind
+```
diff --git a/src/test/README → src/test/README.md b/src/test/README → src/test/README.md
@@ -1,3 +1,4 @@
+# Notes
 The sources in this directory are unit test cases.  Boost includes a
 unit testing framework, and since bitcoin already uses boost, it makes
 sense to simply use this framework rather than require developers to
@@ -17,5 +18,4 @@ uint256_tests.cpp.
 
 For further reading, I found the following website to be helpful in
 explaining how the boost unit test framework works:
-
-http://www.alittlemadness.com/2009/03/31/c-unit-testing-with-boosttest/
+[http://www.alittlemadness.com/2009/03/31/c-unit-testing-with-boosttest/](http://www.alittlemadness.com/2009/03/31/c-unit-testing-with-boosttest/).