asararatnakar / fabric_v1_chaincode_instructions

How to test Fabric V1.0 based chaincode

How to test hyperledger fabric V1.0 chaincode from CLI

How to test your chaincode from Vagrant :

You wrote some chaincode on Fabric V1.0 and now you wanted to test your chaincode with simple of steps of creating a channel configuration , create channel and join channel ...?

Follow are the instructions:

---

Pre-requisites:

mkdir -p $GOPATH/src/github.com/hyperledger

cd $GOPATH/src/github.com/hyperledger

git clone https://github.com/hyperledger/fabric.git

rm -rf /var/hyperledger/*

Build native binaries

cd fabric/devenv

vagrant up && vagrant ssh

cd $GOPATH/src/github.com/hyperledger/fabric

make peer orderer

NOTE: If required do make clean and build the binaries

---

Vagrant Terminal Tab 1:

Start the Orderer

ORDERER_GENERAL_GENESISPROFILE=SampleSingleMSPSolo orderer

---

Vagrant Terminal Tab 2:

Start the peer

peer node start

---

Vagrant Terminal Tab 3:

This uses chaincode example program example02 Install chaincode on the peer

peer chaincode install -n mycc -v 1.0 -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02

---

Generate channel configuration (transaction)

configtxgen -channelID myc -outputCreateChannelTx myc.tx -profile SampleSingleMSPChannel

---

Create channel

peer channel create -o 127.0.0.1:7050 -c myc -f myc.tx -t 10

---

Join channel

peer channel join -c myc -f myc.block

---

Instantiate chaincode

peer chaincode instantiate -o 127.0.0.1:7050 -C myc -n mycc -v 1.0 -c '{"Args":["init","a", "100", "b","200"]}'

After succesful chaincode instantiation, you would see chaincode container comes up. docker ps

CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS               NAMES
ba2746fd32bf        dev-jdoe-mycc-0    "chaincode -peer.a..."   6 seconds ago       Up 5 seconds                            dev-jdoe-mycc-0

---

Invoke

Issue an invoke to move "10" from "a" to "b":

peer chaincode invoke -o 127.0.0.1:7050 -C myc -n mycc -c '{"Args":["invoke","a","b","10"]}'

Wait a few seconds for the operation to complete

---

Query

Query for the value of "a"

peer chaincode query -n mycc -c '{"Args":["query","a"]}'

---

cleanup

Don't forget to clear ledger after each run!

rm -rf /var/hyperledger/*

And may be chaincode containers(optional)

docker rm -f $(docker ps -aq)

docker rmi -f $(docker images | grep "dev-jdoe" | awk '{print $3}')

---

Troubleshoot

??

---

few more samples:

• commands to create channel and test chaincode on the custom channel Instructions here

• commands to test chaincode upgrade functionality, instructions here

• run chaincode in dev mode, instructions here

• commands for Calling chaincode to chaincode, instructions below

with default channel

with non-default channel

• commands to test chaincode on non-vagrant environment (ubuntu) , details here

• commands to test marbles02 chaincode, Instructions here

fabric_v1_chaincode_instructions's Issues

a typo in how-2-test-cc-non-vagrant.md

Hi! I found a typo in https://github.com/asararatnakar/fabric_v1_Chaincode_instructions/blob/master/how-2-test-cc-non-vagrant.md#terminal-window-tab-2-1

After executing

"CORE_PEER_FILESYSTEMPATH=hyperledger/production ./build/bin/peer node start -o 127.0.0.1:7050"

That terminal does not open stdin/stdout. I think third terminal window is needed.

Thanks

Cannot get string data from another chaincode

Hello,

Example. I have 2 chaincode (A, B)

• chaincode A: generate a password hash (string) using bcrypt
• chaincode B: invoke chaincode A and get the password hash
• Test 1: I call chaincode A and get the password hash likes this: "$2a$10$e9lha95xDRV0EfQQIW9zMecZqspeA5aaI8JUf36vgUmoKXtmzs"
• Test 2: I call chaincode B to get the password hash likes this: "0Y0═�H�=╗╔�H�=╚╔╚B"

Anyone, please could you tell me what happened? How to fix?
Thanks a lot.