In god we trust - The rest we test

  Let me share a little story with you. I once visited a customer who was really excited about their automation efforts. “Oh, we have several 10X tests!” they said. Naturally, I was curious and asked, “How do you run them?” Without missing a beat, they pointed to a dusty old computer sitting in the corner of the office. I paused for a second, wondering if I’d heard them right. A computer in the corner? Yep, turns out that’s where they were “running” their tests. If that’s not a sign that your automation might not be as automated as you think, I don’t know what is. So, how do you know if your test automation is actually working for you, or if it’s still stuck in the past, like that poor computer in the corner? Here are some signs that your automation might need a serious upgrade: 1. Pressing ‘Play’ is Still Part of the Process We all love the idea of automation running on its own, but if your tests still require someone to manually click “Play” to start them, then that’s a red flag...

    Introduction As automation in testing continues to grow, ensuring the security of sensitive data is more important than ever. While we work to make our tests efficient and scalable, secrets management often takes a backseat. However, mishandling secrets in test automation can lead to significant security risks. In this post, we’ll discuss the importance of secrets management, the challenges faced, and best practices to protect sensitive data in your automation tests. Why Secrets Management Matters in Test Automation In any software development pipeline, secret management refers to securely handling sensitive data like API keys, database credentials, and certificates. Automation tests often require such secrets to simulate real-world scenarios, such as accessing databases or APIs. Unfortunately, secrets often end up in places they shouldn’t—like hardcoded in source code, configuration files, or logs—leading to potential vulnerabilities. If secrets are exposed during testing...