My experience testing WEB3.0
This year 2022, I began my “Solopreneur” journey. It’s just a fancy word because it takes lots of courage and madness to leave the concept of being an “employee”, working for fancy companies, getting timely paycheck
and that too after a little more than a decade working with them.
I had to give that intro, because that is the reason why, how I got to work on web3 in the first place. You see, these days, I advise/ consult / freelance startups depending on their requirements and my areas of expertise:
Testing, Automation, Solutions engineering and few more.
Well, what can I say, I always wore multiple hats.
Now, moving onto sharing my “Testing” experience with WEB3.0
- Everything is new, until it’s not
As kids, we didn’t know what a web was, then we weren’t aware of Web2 until we deemed a Web3 and called the previous version 2.0.
So, there is literally nothing to scare about.
2. Nothing should change in the User Experience
O dear good Lord, why do I love technology :D
because by creating a new web, we don’t want the user to feel any different.
This has both pros and cons in case of a new technology, especially something as ambiguous as WEB3
The user shouldn’t feel they migrated to a new web version, which makes it suspicious for certain tech-savvy folks, that was there even a change in the first place, because nothing “FEELS” different.
3. Learning never ends
Incase, you are new to the whole gamut of blockchain, Cryptocurrencies, NFT; you will have to learn it. And there is ample amount of content on it.
I got lucky, because back in 2015–2018, I was working with the Biggest American (or world) bank
and Bank’s are the first to try a new technology. So, I knew Blockchain long back. What I didn’t know is how much variation and creativity they brought into this space.
So, I learnt about new networks, wallets and currencies, to show off a few: Ethereum, Binance, Tron, Metamask, Coinbase etc etc (the list is a little too much)
4. Manual first
With anything new, comes the biggest challenge of painstakingly going through an MVP or model again and over again to see if it’s making sense or very simply if it’s working.
This point is deliberately put for people who think everything can be automated; well yes But not until you are sure about it.
IMHO, every new product is an automation of what we did manually for years
and to make it manual today, you needed to understand everything about that flow manually first to automate it later ;)
5. User acceptance testing / BETA testing
Continuing on my previous point, I’m a big believer that every tester is the first USER ADVOCATE.
So, rather than fighting with them, try to understand why your UI is not understandable to the tester or why your functionality doesn’t make sense to them.
Now, coming to a word of advice to my lovely testers.
I hope you understood my above point, because it means there is a big responsibility on your shoulders and the solution for it is simple, which I call:
“Sticking to your basic”
For example: the easy of flow, the linking between webpages, the placement of a button, the security of an application, the color combination used on the UI are differentiable by a colourblind or not, etc etc etc.
I think you were expecting too high fundo jargons on this writeup.
but you see, I like to Keep IT simple always.
and that’s the most difficult to do but I hope it was understandable for you, as that was the whole point.
And these 5 principles can be used to test NOT just WEB3 but anything at all.
So, you’re welcome, I just briefly condensed for you, my secret sauce of Testing