When developers think of testing, the knee-jerk reaction is often a push for 100% code coverage. But is coverage alone the best metric? Testing is complex and nuanced, with real-world trade-offs. Here’s how we approach testing with purpose, flexibility, and confidence.| Flagrant
Test environments that are 10x cheaper and 10x faster than RDS clones – compare various ways to clone databases in AWS, including RDS clones, Aurora thin clones, and DLE clones|
Comprehensive Testing Covers Code AND Data|
Functional testing and integration testing are critical in verifying software functionality. Learn here about functional test vs integration test.| QA Touch
Integration testing checks for bugs, errors, or issues in the interaction between components. Learn more about integration testing here.| QA Touch
The simplest way to integration test your stored procedures is with jOOQ and testcontainers| Java, SQL and jOOQ.
Using H2 as a test database vs integration testing directly on your production RDBMS| Java, SQL and jOOQ.
Contract testing is a technique to calm the chaos caused by sprawling, complex microservices & APIs. Here's how to use it alongside integration testing.| Pactflow Contract Testing Platform