At Revelry, we believe in sharing and learning from one another (beliefs that are rooted in our Core Values). Among the many things we do…
Testing content on the Revelry Blog: Navigate our lab notes by using the tag system.
Most software teams have left behind the Waterfall(1) methodology in favor of approaches that move faster and flex more to accommodate changes and maximize the…
Lately I’ve been exploring various automated testing techniques, and it’s about time I got to property-based testing, also known simply as property testing. I…
Whether it’s a feature, a bug, or a regression, it’s all work. It all has the same level of prioritization before we add in the business context. This is how we decide what gets worked first.
Mutation testing involves running your test suite many times, modifying the application code in different ways to see if the tests catch the change.
You’ve tested. You’ve deployed. Your work is out in the wild. Then – WHAT IS THAT on your bug report? Oh… You have users on Internet Explorer. Jason shares how to test using Windows Virtual Machine on the MacBook.
A great way to save hours of time is to always keep cross-browser best practices in mind throughout the process of developing a new site.
If you write tests after you wrote the code, it’s hard to be 100% the tests are legit… If they wouldn’t have failed without the code you just wrote, they’re basically useless.
If your contract revolves around time as a key mechanic, you’ll find yourself waiting for extended periods of time or frequently missing important time windows as you switch back and forth from code editor to wallet.
You might want to avoid Jest if you don’t need its features, don’t like its conventions, or if Jest is incompatible with your other tools. If you choose not to use Jest, you can use Jasmine directly instead.