Reminders and Lessons from the CrowdStrike Incident
Last week’s CrowdStrike incident was a stark reminder of the importance of secure software development practices. While the specifics of the global event remain…
QA content on the Revelry Blog: Navigate our lab notes by using the tag system.
Last week’s CrowdStrike incident was a stark reminder of the importance of secure software development practices. While the specifics of the global event remain…
Code audits are critical to preventing unstable code from being shared with the world or shipped to customers (gasp!), and they should be a…
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…
Learn how to avoid common code review pitfalls that engineering managers face.
Hone your team’s code reviews at the Git Pull Request level.
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.
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.