ambassador

senior_ambassador

head_ambassador

I find the (easily discoverable) documentation on howto write tests quite light. Very little info in the readme and also no links into deeper docs. I also don't see any tutorial to get started or a reference. 

What I would love to see in docs:

- Basic tutorial: Write your first test and get it merged.
- Some more tutorials for more complex usecases - showcasing capabilities.
- Good reference docs for the rest.

[@eskimor](12pRzYaysQz6Tr1e78sRmu9FGB8gu8yTek9x6xwVFFAwXTM8-collectives) 

Thanks for the feedbacks. Will add more docs explaining those.

I personally don't like over-document things because the docs become liability for maintenance. Instead, I prefer for the code to be self-explanatory at the first place and only make necessary document. Therefore, I need feedbacks on what's missing or what need extra explanation. Because obviously I understand all the code I wrote but harder for me to see if they are also easily understandable by others.

Voting nay on the lack of feedback from other fellows. Although my vote will not change the result anyway.

Payment of $30k USD as per this proposal: https://collectives.subsquare.io/posts/18

AssetSpendApproved

Paid

fellows

Ecosystem Test Environment: Milestones 6-7

members

proficient_members

architects

architects_adept

grand_architects

masters

masters_constant

grand_masters

retain_at_i_dan

retain_at_ii_dan

retain_at_iii_dan

retain_at_iv_dan

retain_at_v_dan

retain_at_vi_dan

promote_to_i_dan

promote_to_ii_dan

promote_to_iii_dan

promote_to_iv_dan

promote_to_v_dan

promote_to_vi_dan

fast_promote_to_i_dan

fast_promote_to_ii_dan

fast_promote_to_iii_dan

#5·Ecosystem Test Environment: Milestones 6-7