scottz64 / obcsdk

opensource blockchain software development kit, GO code and tests for hyperledger fabric

obcsdk

opensource blockchain software development kit, GO code and tests for hyperledger fabric

A test framework for testing Blockchain with GoSDK (written in Go Language). Tests on this master branch correlate to v0.5 branch code in hyperledger/fabric.

##Obtain the GoSDK and test programs: Clone to the src directory where GO is installed (use either $GOROOT/src or $GOPATH/src).

$ cd $GOPATH/src
$ git clone https://github.com/scottz64/obcsdk.git

Enclosed local_fabric bash scripts will create docker containers to run the peers. For more information, [read these instructions] (https://github.com/rameshthoomu/fabric1/blob/tools/localpeersetup/local_Readme.md) to setup a peer network.

##How to execute the programs:

• If you wish to connect to an existing network, change the credentials in NetworkCredentials.json as needed.
• Helpful shell scripts are located in the obcsdk/automation directory:

	../automation/go_build_all.sh           - execute this from any of the test directories, to build all the *.go tests there
	../automation/go_record.sh <tests.go>   - execute this from any of the test directories, to run go tests and record stdout logs in GO_TEST* files in the current working directory.

• LOGFILES for all Peers are saved in the automation directory. Run go_record.sh (or local_fabric.sh) without parameters to get help with the options.
• Go to the test directories and execute the tests. Good luck!

	$  #  Examples how you can preload some of the environment vars, for local or for HSBN/Z network testing:
	$  .   ../automation/ENVVARS_LOCAL
	$  .   ../automation/ENVVARS_Z
	$  export COMMIT=<commit>

	$ cd obcsdk/chcotest
	$ go run BasicFuncNewNetwork.go
	 
	Run Consensus Acceptance Tests and two long-run tests:
	$ cd obcsdk/CAT
	$ go run testtemplate.go
	$ ../automation/go_record.sh CAT*go
	$ ../automation/go_record.sh CRT_501_StopAndRestartRandom_10Hrs.go
	$ ../automation/go_record.sh CRT_502_StopAndRestart1or2_10Hrs.go
	 
	Run other tests being developed in chco2test directory:
	$ cd obcsdk/chco2test
	$ go run IQ.go
	 
	Run various tests being developed in chcotest directory:
	$ cd obcsdk/chcotest
	$ go run ConsensusBasic.go
	 
	Run ledger stress tests: first start up a network, and connect your tests to it by
	configuring obcsdk/util/NetworkCredentials.json
	$ cd obcsdk/CAT
	$ go run testtemplate.go
	$ cd obcsdk/ledgerstresstest
	$ NETWORK=LOCAL go run LST_2Client2Peer.go

	Run COMMIT=821a3c7, the v0.6 Sep 7th build, in local environment with one of these commands:
	$ local_fabric_gerrit.sh -c 821a3c7 -n 4 -f 1 -l error -m pbft -b 2 -s
	$ export COMMIT=821a3c7; export REPOSITORY_SOURCE=GERRIT; go_record.sh ../CAT/testtemplate.go ../chcotest/BasicFuncNewNetwork.go

###Running tests on Z network requires some tweaking to make things run.

• Put the IP address info of the peers into the util/NetworkCredentials.json; use script update_z.py to help generate that file for BlueMix networks.
• Set environment variable NET_COMM_PROTOCOL to use HTTPS instead of default HTTP; required for Ledger Stress Tests on Z network, and may also be useful when running other tests in other networks that could use HTTPS,
• Define its own usernames/passwords (may need to edit threadutil/threadutil.go)
• (Ledger Stress Tests only): Set environment variable NETWORK to Z when using the Z network and its usernames/passwords
• (Ledger Stress Tests only): set the correct chaincode name in lstutil/util.go to change it from "mycc" (special version of example02 that increases the ledger) to whatever is deployed on the actual Z network you are using. Before running any tests, rebuild: "cd ledgerstresstest; ../automation/go_build_all.sh"

	For example:

	$ cd ../CAT; NET_COMM_PROTOCOL=HTTPS go run CAT_101*.go

	To run tests with example02 in BlueMix network on v05 (COMMIT=3e0e80a) or v6 (COMMIT=821a3c7), download the ServiceCredentials from BlueMix and run script update_z.py to generate networkcredentials file for the Z or Starter or HSBN network; then try one of:

	$ ./update_z.py -b -f <service_credentials_file>
	$ cp networkcredentials ../util/NetworkCredentials.json
	$ export NET_COMM_PROTOCOL=HTTPS; export NETWORK=Z
	$     export COMMIT=821a3c7; export REPOSITORY_SOURCE=GERRIT
	   OR
	$     export COMMIT=3e0e80a; export REPOSITORY_SOURCE=GITHUB
	$ go run ../chcotest/BasicFuncExistingNetwork.go;
	$ go_record.sh ../CAT/testtemplate.go

	To run ledger stress tests with a different chaincode named mycc, a modified version of example02, in BlueMix network on v05 or v06:
	$ cd ../ledgerstresstest
	$ export NETWORK=Z ; export NET_COMM_PROTOCOL=HTTPS
	$ go run BasicFuncExistingNetworkLST.go
	$ go run LST_1Client1Peer.go