Systems | Development | Analytics | API | Testing

Today, we're joined by our expert QA Therapist, Antoine Craske, who's here to diagnose and prescribe solutions for symptoms related to Quality Engineering. Hailing from France and working as a Software Engineer at La Redoute, Antoine brings a wealth of experience to the table. He emphasizes that quality isn't the responsibility of just one person or team; it's a collective company goal. To achieve this, leveraging tools is essential.

High-performing teams don’t have large test suites. They have small, focused test suites. They make the most of their limited resources. Ideally, you would have extensive test suites for maximum coverage. But most teams don’t have the resources needed to maintain that level of tests and evaluate their results properly. @Titus Fortner, Senior Developer Advocate at @Sauce Labs, encourages testers to advocate for themselves and their teams. He says it’s important to call out when the testing managers' requests are unsustainable and instead focus their efforts on what’s most important.

Should you design tests in the same language as the application you’re testing, or should you use the language you’re best at? @Hanson Ho recommends using the language that’s most popular in the application’s platform. This way, you’ll have more help available from the community. If you want more insights like this one, check out Test Case Scenario.