The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
I conducted comprehensive QA testing on Fuji.Trade, focusing on critical user journeys including wallet connectivity, trading workflows, onboarding, and overall user experience.
During testing, I identified multiple functional and usability issues that could impact user confidence and platform reliability. Each issue was documented with clear reproduction steps, expected behavior, actual behavior, severity, and supporting evidence to help streamline developer investigation and resolution.
This project highlights my ability to identify high-impact issues in Web3 applications while improving usability, reducing friction, and supporting more reliable product releases.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
I want to share an internal tool we use at Ander.Agency to QA our websites.
It’s great for collaborating with the team, clients, and even AI!
You can connect to it via MCP and ask Claude to manage and resolve all the reported comments for you.
It’s honestly mind-blowing. Trust me!
https://getpulpo.dev/
Nice tool it looks practical ❤️❤️
Issues caught before a customer ever saw them.
Every one flagged and fixed quietly, before it became a support ticket.
→ Want this for your systems? Let's talk.
Seeing the silent flagging step saves support time and keeps the user experience smooth.
A redesigned website can look right while pagination, canonicals or indexing rules have changed underneath. Those details need acceptance tests before launch.
For each page type, define:
What crawlers should be able to reach.
Which URLs should be eligible for indexing.
What links, content and metadata the page should return.
Who checks the implementation and what counts as a pass.
One example: if you rely on a page’s noindex directive, blocking that page in robots.txt prevents Google from reading it.
I put together a practical guide to turning technical SEO requirements into a specification developers and QA can actually use.
Projects and client work: NikoCodes
