Community TESTNET update 19th October 2018
After HF20 stabilizing, many from the community members started working towards implementing a testing procedure (@yuriks2000, @bobinson, @yehey, @reggaemuffin, @gtg, @holger80, @ayogom, @quochuy & many more). We are loosely connected via a discord group and various activities are taken up. I was trying to make Tinman based transaction generation better and also test new commits. Test results for v0.20.6rc1 which will be eventually the next release of the STEEM code base is in the last phase.
This update mainly mentions the small inputs to Tinman.
What is Tinman ?
Tinman is a setup scripts used to take snapshot of the mainnet, generate transactions etc for TESTing purposes. The code is actively maintained by @inertia and others from Steemit.
what is involved in this update
A small set of changes which will implement PEP-8 coding style to the Tinman codebase and the resulting PR.
Testing
Transactions are submitted using:
( echo '["set_secret", {"secret":"xyz-"}]' ; tinman txgen -c txgen.conf ) | tinman keysub | tinman submit -t https://testnet.steemitdev.com --signer sign_transaction -f fail.json
what is next ?
I have used codeclimate to generate quick statistics. These are more or less just indicators as opposed the rules to be followed.
.
.
Also an attempt to run code quality testing is done. A snapshot is given below and will publish more details when some of the issues in the Gitlab based pipeline is sorted out.
Series Backlinks
- @yuriks2000 : Gamify Steemit's future Soft/Hard Forks testing - The SteemCommunity Organization
- Witness update : progress on testing, environment setup
- Community TESTNET update 17.20.2018
If you like what I do and write, please consider voting me as a witness :-)
Vote for bobinson as STEEM witness
You can do so by clicking the steemconnect.com link above & enter your private key when asked for.
Alternatively, you can visit https://steemit.com/~witnesses & place your vote.
Thanks for using utopian-io tags and for the work on tinman, bobinson. PEP8 is definitely as a must for Python projects. It's good to see an effort to fix that issue.
However, looks like the contribution is not merged yet and under discussions as I can see from the pull request, and we have a policy on that:
@emrebeyler - thanks for the response. The PR is not yet merged and I will be creating an issue in github as per the suggestions and trying to get this merged.
Thank you for your review, @emrebeyler!
So far this week you've reviewed 6 contributions. Keep up the good work!
@emrebeyler I am following this up here : https://github.com/steemit/tinman/issues/171
Your inputs will be helpful
This post has been rewarded with 100% upvote from @indiaunited-bot community account. We are happy to have you as one of the valuable member of the community.
If you would like to delegate to @IndiaUnited you can do so by clicking on the following links: 5SP, 10SP, 15SP, 20SP 25SP, 50SP, 100SP, 250SP. Be sure to leave at least 50SP undelegated on your account.
Please contribute to the community by upvoting this comment and posts made by @indiaunited.
I'm already united in that HFT community, I'm here to help in whatever way I can, let's move forward.