937.458.0055

software testing

As a leader in charge of a departmental or project budget, there is a term to be familiar with that may have slipped through the cracks. As software development projects continue moving forward and evolving, what are the hidden costs? What is Technical Debt? Technical debt is the term given to leftover costs associated to [...]

{ 0 comments }

The software development project has come so far, and everyone can see that the end is near. Likely, you’re doing Agile development and have been doing in-sprint testing along the way.  Maybe you’re pretty sophisticated and have been doing test automation along the way.  But, whether Agile or Waterfall, you likely want to do a [...]

{ 0 comments }

For software development projects large and small, there are several advantages to having a dedicated Quality Assurance (QA) team when it comes to testing.  Many project managers attempt to cut costs by having all team members engaged in the testing process to keep things in-house. Sometimes it works well, but after experiencing the contrast of [...]

{ 0 comments }

Once upon a time, software development teams waited until the end of the development cycle to fully test the finished product. This practice had a team of manual testers follow scripts, or they removed SMEs from their day jobs and monopolized their time for 4-6 weeks while they tested the functionality of the software.  Of [...]

{ 0 comments }

It’s October, and odds are your department is waist-deep in building next year’s budget. But while budgeting can be a monotonous, Herculean task, it also can be a transformational one: with a new budget on the horizon, now’s the time to improve your testing team by investing in large-scale, quality-focused initiatives.

{ 0 comments }

We talk a lot about software testing methodologies around here.  And for good reason—they’re a primary component of a consistent and efficient testing and QA organization.  But what is a methodology built upon?  At Lighthouse, it comes down to 3 things: People, Process, and Tools.

{ 0 comments }

Software is never 100% defect free, so how far should responsible testers go before wading into the murky seas of cost overruns and diminishing returns—and what methods should they use to draw the line?

{ 0 comments }

Everyone fails at one point or another, but what sets the truly great apart is how they learn from it and improve. In the IT world, almost everyone’s dealt with software project failures; but identifying their root causes can be difficult, making improvement impossible—at least until now, that is.

{ 1 comment }

In today’s world, software testing is increasingly seen as a commodity. But as companies’ reputations become increasingly dependent on their digital presence, is poor quality really acceptable anymore? And if so, isn’t it worth finding a high-quality outsourcing partner to protect it?

{ 0 comments }

If there’s one common concern our clients share, it’s their initial worry that we’re not familiar enough with their customized software systems to test them effectively.  That’s why we go to such great lengths to ensure our testers are effortlessly adaptable to all sorts of digital terrain.

{ 0 comments }
PMIASQIEEESoftware Engineering InstituteInternational Software Testing Qualifications Board