Testing NFT Smart Contracts: Common Edge Cases You're Missing
Discover crucial edge cases in NFT smart contract testing that are often overlooked, with practical examples and solutions for robust contract security.
I'm helping web3 projects build better products through test automation and architecture strategies.
Discover crucial edge cases in NFT smart contract testing that are often overlooked, with practical examples and solutions for robust contract security.
Learn how to create realistic test data for DeFi projects, moving beyond basic ERC20 mocks to simulate complex financial scenarios and edge cases.
Discover how we slashed gas costs by 40% using smart contract testing techniques. Learn practical tips for optimizing your own Web3 projects.
Learn how to effectively test smart contract upgrades with a comprehensive strategy, including practical examples and best practices for Web3 developers.
Learn how to set up automated testing for your smart contracts, ensuring security and reliability in your blockchain projects.
Dive deep into the real costs of Web3 testing, including hidden expenses and budget-saving strategies for blockchain projects.
Learn how to effectively integrate and test smart contracts with frontend applications in Web3 projects. Discover best practices, common pitfalls, and practical solutions.
Discover crucial differences between Web2 and Web3 testing approaches, with practical examples and solutions for common challenges.
Load testing is a well-known technique of software testing to make sure, that system we’re working on, behaves in a way, we’d like to.
While starting to work with end-to-end tests, one of the first questions is where to store them. Alongside source code or in separate repository? Two solutions, both slightly different. Each of the approaches has their pros and cons – but which to choose?
The beginning of automated tests in a project is easy and difficult at the same time. You can start smoothly, using base architecture, simple tests, etc - and it's gonna work! But... With growing architecture, solutions you'll take could be very hard to develop in the future. That's why, you should consider a few things, before the start. I want to show you the problems and solutions do they…
With growing test architecture, we are facing various problems. Execution time, flakiness, duplicate test cases etc. Tests are becoming hard to manage and we may start to feel like writing and maintaining them is meaningless.
Have you ever think about steps in the testing journey? Manual tester, QA, QA Engineer, Test Developer, SDET, TestOps? There are many ways you can develop in. But today, I want to stick with one - QA Engineer.
Building a product, we face the moment that we need more types of tests. Screenshot, UI, API, or Performance? There are many of them and every one is designed for other purposes.
Using CSS selectors to get elements in end-to-end tests is the most common way (besides xpath), but it can also be tricky and hard to maintain. One day everything could work fine and another a CSS class could be renamed. Styles could change without touching the business flow and then we could have a problem - we'll need to maintain the tests. Of course, the developers could do those changes for…
With growing test architecture, we are facing various problems. Execution time, flakiness, duplicate test cases etc. Tests are becoming hard to manage and we may start to feel like writing and maintaining them is meaningless.
Recently I wrote a post about my first steps with test automation. I tried to answer questions related to the topic and guide you where and what to search for. Now, I want to expand on it with technical steps
Starting your test automation journey isn't always as smooth as it should be. You may have a lot of questions like
Recently I had the pleasure of interviewing candidates for my QA team. Sometimes, they were hard. You may ask why so I'll try to explain. I hope that in the future we can teach and prepare wanna-be test engineers to pass every interview they want to:)
Some time ago I read a book - The Power of Habits, written by Charles Duhigg. I wanted to learn, how to manage my habits and the most - how to get rid of the bad ones. The author of this book tries to prove, that everything which we're doing can change. Just by changing our doing path. This can change our whole life.movement to my initiatives?
Getting variables using destructuring makes our life a bit easier. It looks nicer than the normal way and makes code reading easier.
Some time ago I hit an article, that Github added a special type of repository, the ones you see above (we'll make it better), where we can write something about us. I think, that's a great idea to show, what exactly I'm doing, and maybe... it could give me some movement to my initiatives?
Yesterday I didn't know how to manage an income. I thought it's very complex to build a financial cushion, manage two accounts, invest money or just simply not live beyond the state.