"Our test suite passed," the developer announced. The business analyst looked at the console output - pages of cryptic assertions, stack traces, and technical jargon. "Great," she replied. "But what did it actually test?" The developer scrolled through the logs, searching for something human-readable. Nothing.
We've all seen it happen. The developers on the team excitedly discuss the latest framework they're implementing, while the test automation engineers quietly stick to the same Selenium scripts they've been maintaining for years. It's a strange disconnect – the very people who should be at the forefront of technological validation often trail behind when it comes to evolving their own toolset.
Test code often plays second fiddle to production code. Yet, the quality of our tests directly affects the reliability and maintainability of our entire codebase. In a previous article, we explored the importance of code quality and the aspect of designing and establishing a clean, reusable architecture. Now, we turn our attention to an equally critical aspect: monitoring test code quality, especially when working with less experienced teams.
In the domain of software testing, the dialogue between API and UI testing methodologies remains pivotal. The white paper from Karate Labs, "Navigating the Brave New World of API Testing", champions API testing as a superior alternative to UI testing, positing it as a solution to several common testing challenges. However, this perspective, while valuable, warrants a critique to ensure a balanced understanding of the testing landscape.
Self-managed execution is essential for any test automation platform, forming not only the foundation of intelligent test management, but also dramatically decreasing human intervention in your CI/CD pipeline. Manual execution decreases testing efficiency, especially when working with a complex test or in a testing environment with multiple integrations and end points.
In REST API systems, security and authorization are essential for mitigating risks and vulnerabilities. This article aims to explore effective testing methods for these critical components within the REST API architecture.
Exavalu's Guidewire QA delivery, business analysis, project management, and architecture expertise joins CenterTest test automation, so carriers get custom automation solutions staffed to each engagement.
MutualCore's executive-level leadership perspective, IT transformation experience, and consultative advisory join CenterTest test automation for Canadian property and casualty carriers
Kimputing is attending Guidewire Connections 2026 in Las Vegas, October 26 to 29. Book time with the CenterTest team before the event.
Guidewire test automation,
