It was late 2005. I was preparing for my new job at Qentinel, a small software quality assurance shop. My future team members were each presenting those big, important, and exciting things they thought I should know before I officially start as the CEO of Qentinel in January 2006.
All articles from author
Test architecture means the way you put together all those things you need in testing. Depending on what you test, where, and how, the test architecture may be simple or complex, ad-hoc or well-thought. Most often than not, test architectures are not thought of, they just emerge.
Qentinel Pace is Qentinel’s cloud-based test automation platform. It was built on three premises: scale, speed, and transparency. Because the scale of testing keeps growing test automation platforms must scale, too: from a single developer to a large organization, from small test volumes to huge volumes – and back. Because the software release times are shrinking, testing must be fast: time must not be wasted on patching test environments or maintaining cumbersome test cases. Because both speed and quality are important, decisions about releasing software or changing something in the software process must be fast and fact-based.
Speed is essential in today’s business. Some people even say speed equals to life, or at least to being alive.
Almost all software executives I speak with are struggling with speed. Everyone feels the pressure to deliver more value in a shorter time and faster cycle.