Anton Bolotin: Testing with Community: A New Approach to Quality Assurance through Public Testing
summary
A method used at Soramitsu deploys smart contracts to a public testnet for one month, invites the community, and uses GitHub issues plus a Telegram channel to collect feedback. A recent run has about 150 participants producing ~70 reports with 10–15 unique bugs, uncovers unexpected mobile-first usage so the team ships a mobile adaptation, hires one tester from the participants, and pays rewards in tokens or NFTs. The approach reduces QA cost, generates marketing momentum, and produces actionable backlog items.
AI-written summary · about
chapters (16)
- 0:00Testing with community
- 1:08Low-quality releases
- 3:35Public testing and test networks
- 5:01Public testing in blockchain
- 7:10Public testing participants
- 9:00Advantages of public testing
- 12:57Decentralized crypto exchange case
- 17:38Results from public testing
- 19:51Benefits for companies
- 21:38Applying public testing
- 24:15Public testing at JetBrains
- 26:45Public testing for startups
- 28:09Motivating testers
- 29:16Implement public testing
- 30:39Final thoughts on quality
- 31:21Q&A
related talks
45mBuilding Tools to Free up Exploratory Testers
44mExploratory Testing - MobTesting, BugBashing, CrowdTesting, Oh, My!
53mWhat Happens When Everyone is QA? And I Mean Everyone!
40mDigitizing Testers
45mTesting the web without testers — success or failure
01h 21mThe Future of Testing Is Here
32mZero to Test, How to Run Your First Beta Testing Program
25mOn The Shoulders Of Testing Giants