As experts of their domains, it’s easy to see why SMEs are constantly pigeonholed into testing their respective areas of expertise. Consequently, it’s no surprise that they often feel like they’re the only people capable of testing it—something that, with a little bit of documentation, couldn’t be further from the truth.
When it comes to software development projects, test automation (Oracle OATS, HP UFT/QTP, etc.) is oftentimes seen as a luxury—nothing more than a speedy improvement over the status quo. But while this is somewhat true, test automation offers so much more than speed: it allows you to execute essential stress tests that would otherwise be impossible to afford.
Following a recent roundtable, Jeff Van Fleet, Lighthouse President and CEO, has one question on his mind: is the software community sharing its knowledge?
As winter’s embrace loosens, Jeff Van Fleet, Lighthouse’s President and CEO, is talking renewal. Just as the Earth renews itself come springtime, we must do the same thing intellectually.
Whether it’s lowering costs, improving quality, accelerating time-to-market, or increasing test capacity, lots of people think test automation is the answer to all of their problems. And while it most certainly can be, it’s not a magic bullet, either. But provided you’re smart, you’ll see an ROI in next to no time. Here are some tips to help you get there.
With the start of the New Year fresh in our minds, most of us are trying to better ourselves in some way or another. But Jeff Van Fleet, Lighthouse’s President and CEO, wants to know: are we neglecting other important things at that expense?
What happens when you acquire a multimillion-dollar company and you can’t automatically invoice their customers? That’s the situation a recent client of ours was facing when they couldn’t integrate their newly-acquired company into their Oracle EBS system. How did our expertise help ensure a smooth transition?
When it comes to software testing and QA, a lot of companies are reactive—achieving quality almost entirely through the individual heroics of their own testing team. But, while this approach may be effective, is it really sustainable in the long run? Moreover, how can a proactive approach mitigate those inherent risks?
It’s a new year—that means new objectives, new budgets, and new projects. If you’re like most QA departments, chances are you’re looking into test automation. But while the value to your department is obvious, how do you state the best financial case to secure upper management’s buy-in?
Every year, people use the start of the new year as a chance to better themselves. But while we’re always striving to do so at home, why aren’t we also bettering ourselves in the workplace? And since so much of our time there is spent on computers, improving software quality is just the place to start.
