QA Software Testing Company

Does Your QA Software Testing Company Do Both?

That’s not a typo in the headline. I’ll repeat. Does your QA software testing company do both?

Both? Both what?

Why, both QA (Quality Assurance) and Software Testing, of course.

QA, Quality Assurance, is a goal and process.

Software Testing is an activity, usually inside the QA process.

Is This Difference Between QA And Software Testing Important?

It depends on what you have and what is important to you, of course.

If you already have a rock-solid QA process for your software quality, then software testing help may be all you need.

After all, your rock-solid QA process should inform you exactly when (and how much) you need software testing versus when you need test strategy and planning.

Your rock-solid QA process already has a SMART Goal that drives your software QA and testing team to the right activities at the right time with the right effort to achieve your goal, right?

But, if you don’t already have a rock-solid QA process, then you may need a little bit more than just software testing. A qualified QA software testing company, LIKE TESTCo, can (and should) help you with this as a natural part of their work with you.

Why Would You Even Need a QA Process?

There are three important reasons to consider building a QA process, even a small one, before you start software testing.

  1. You can’t test everything
  2. Testing can be expensive
  3. You can’t “undo” disappointed customers

As you can see, you can’t win in this situation unless you have unlimited time, money and fresh customers.

How can you win against these three big constraints?

Build a simple QA Process with a SMART Goal, clear strategy, and simple plan to achieve your goal.

Unless you already have a QA Process, goals, strategy and plan, you should seek a QA software testing company that does BOTH – QA and Testing.

Note: a QA software testing company CAN’T help you with this unless they assign a QA Manager to your project and they collect the information needed to build a SMART QA Goal. Testers, no matter how experienced, just don’t have the skills and training to build effective QA Goals or QA Processes.  TESTCo provides a QA Manager, at no additional charge, on every software testing project.

How Much QA Process Do You Need?

We think you should have the “Goldilocks” QA Process – not too much, not too little, just enough to achieve your business and quality goals with minimal risk.

Too much QA process will slow down your software development and release process and you’ll struggle to hit your release date targets.

Too little QA process and your customer service phone lines will light up like a Christmas tree.

A “just right” QA process should produce software that meets your business and quality goals and makes your team feel proud of their accomplishments.

Knowing Your Goal

How much is “just right”? That depends on your goals and constraints. If your goal is for ZERO defects, you should know that your budget is going to need to be *very* large. This type of quality is usually reserved for nuclear power plants and military software.

If you don’t have a quality goal and just need to get it “tested” then you won’t need much budget or time. But, your customers will probably experience significant bugs and delete your mobile application based on their poor experience. This type of quality is typically used by businesses testing a market or idea rather than penetrating and competing in that market. New customers are expensive to acquire and bad mobile applications or buggy web apps are one of the easiest ways to drive them away.

If you *do* have a quality goal, then the right amount of QA process is exactly the minimum needed to achieve your goal. This usually means investing in building test cases during your specification phase, designing and building test frameworks during your build phase, quickly executing test cases and reporting defects as soon as possible after it is built (real-time functional testing), and then a brief functional and cross-device regression testing after all the fixes are completed and prior to roll out.

Reaching For The Right Assistance

Helping you design, experiment and build your QA process is something that an experienced QA Software Testing Company can help you with. A mobile software development company can help you build your development process, but they seldom do well helping you design and build a software QA process.

Why? Software developers CREATE and BUILD software to add FEATURES. Test Engineers TEST and attempt to DESTROY software to find DEFECTS in the FEATURES. Test Engineers typically have the same university-level education and training as software developers, but have chosen a different path for their career. Additionally, QA Managers have a library of QA processes and strategies so an effective strategy and process that meets your specific needs is quick and easy to find, evaluate, and implement.

How Can You Know Which Vendor Has Which Capabilities?

That’s easy – here are three questions you can ask that will quickly and easily let you find out if the QA software testing company you’re talking to has both Quality Assurance and Software Testing experience you need.

  1. How do you establish and achieve quality goals for your clients? What is a recent example? QA Goals should be SMART Goals and have a clear plan for achievement. QA Goals should also have clear constraints – especially in Budget and Time – no project runs forever for free! Lastly, QA Goals should have clear Business Value – they achieve something useful that moves the entire business forward in achieving its’ goals.
  2. What variety and type of QA strategies do you consider when evaluating a client’s needs? What is your “go-to” strategy? There is always more than one way to achieve a goal – these are strategies and help you quickly determine if your plans can work to achieve the goal within the constraints. Sadly, one of the most popular QA Strategies is “test everything” and that seldom works. It feels good because you can see and measure a lot of activity but it almost never provides the detail and coverage most modern technology applications need. In some cases, it can actually be counter productive and delay a release! A smart QA Strategy should be proven effective and simple enough for stakeholders to understand and support.
  3. How do you document, update and communicate your test plans and percentage of goal completion? What is your goal completion percentage for your clients? Documentation of technology projects can be cumbersome but accurate documentation, reporting and measurement of QA and Testing is critically important. Poorly documented defects are literally worthless if they require developer time to diagnose and recreate the defect. Test plans are mathematical equations for demonstrating test coverage and completion across a technology project. They must be updated real-time to provide the real value a testing team needs to achieve their goal and the quality goal of the technology project. Goal completion is a critical value measure for outsourced software testing providers. Without measuring Goal Completion, your outsourced software testing partner is doing the work but failing to deliver the true business value.

Asking these questions can help you avoid the painful lessons of working with an outsourced software testing provider.

Can Location Choices For A QA Software Testing Company Be Helpful Or Harmful?

Having a QA Software Testing company near you can be helpful – especially of you have hardware closely connected to your project. Technology projects are rapidly evolving to include the Internet of Things.

QA Software Testing companies span the world and you have many choices about where you want your software testing & QA services located. There are two primary considerations when considering where to locate your QA software testing services.

Timezone Considerations

If your project is rapidly evolving and the stories/requirements very fluid, then selecting a QA Software Testing Company in the same or very similar Timezone will probably work in your favor. This will help you avoid some of the communications challenges that occur when a team is working at the opposite end of your clock. If your project is relatively stable, then selecting a QA Software Testing Company in an opposite Timezone will work in your favor. This will allow your QA and Testing team the opportunity to complete their work prior to your local team arriving at work. Fresh code at night and fresh bugs in the morning!

Time zone considerations will largely depend on the needs of your business. Generally, teams with the same time zones are more standardized and work together more efficiently. This is the more popular way to work and you don’t have to accommodate other teams that work during strange hours. If your team is focused on a continuous delivery model, having different time zones can be an advantage. This is because one team can work on the project in the morning and at night the other team picks up where they left off. This allows projects to be done around the clock and can be very advantageous. Take a look at the nature of your projects and you can decide whether it’s better to share the same time zones or not.

Intellectual Property Considerations

If your company or project has new and highly valuable intellectual property in your software project, then it makes a lot of sense to avoid locating you QA Software Testing Company in a country that does not have reliable and effective IP protection laws. If you’re building a cutting edge artificial intelligence system then locating your QA Software Testing Company in another country with strong IP protection is almost a basic requirement. If you’re building a marketing mobile app, then you probably don’t have much IP to protect (in your app) and the risk of IP theft is very low and the country where you locate your QA Software Testing Company is not nearly as important.

IP considerations for your mobile app might seem tedious and unnecessary at first, but the long tail consequences are enormous. Without proper IP considerations, your business intelligence is liable to be stolen at virtually any time. Locating your business in a country with strong IP laws protects your data, branding and everything else related to your mobile app. Aspects of your mobile app like logos, patents, trademarks, etc. are protected under countries with strong IP laws. This protects you from having copycats steal your entire business model, name and brand.

The Nexus Of QA Software Testing

TESTCo is ideally located in Austin, TX, with offices in Mexico and Ukraine. This allows us to work in almost any time zone you prefer. Our offices in Mexico and Ukraine allow TESTCo to work on your project without any state-sanctioned IP risk.

Our physical locations enable your mobile app to have both quality assurance and software testing. With TESTCo you can customize your QA and testing process. You’ll be given a QA manager that will help you design SMART QA goals for your mobile app and guide you along your entire QA process. In addition, you’ll also be provided with test engineers that will identify and solve defects within your application. The several locations of TESTCo allows you to choose a location that accommodates your time zone and IP preferences. With the talented QA staff and multiple available locations, your application will have the human and technological bandwidth needed to succeed.

A QA Software Testing Company Should Give You a “Certainty of Success”

This is both a set of facts and feelings that your outsourced software testing company can deliver the value and services you need to achieve your business and software quality goals.

Seeking a software testing company that does both QA and testing will be the most cost-effective solution for your business. This prevents you from incurring additional costs associated with each service and the final invoice amount would be much larger. Also, choosing two different companies to do these services can cause a disconnect; some parts of QA and testing overlap and having one provider for both is the most optimal solution. This creates a seamless integration for both of these services and you’ll get access to all the talented staff that work on QA and testing.

When consulting with a vendor, asking the right questions provided above will enable you to see the important details in both their QA and testing processes. If your QA and testing provider can’t answer those specific questions, you should seek a different provider. A competent QA or testing provider will be able to answer all the pertinent questions related to your project and provide some consultation to help you choose the best path forward.

At TESTCo, every team consists of a Test Engineer and QA Manager to make sure you get the Quality Assurance you want and the software testing you need. It makes a difference. Just see what our clients have to say.

Give us a call at 888-254-9709, or request a call back with the form on this page if you want to explore this further with me.

Make Engineering Fun Again. Improve The Human Stack With The Right QA Service.

In This Post

I’ve worked with software engineers, usually the head of engineering, my entire career. First, as a product manager, and since 2002, as Founder/CEO of a QA service outsourcing company. In that time I’ve gained deep respect for the people who carry the burden of bringing a vision to life in a manner that makes money for their organization. I know what thrills engineers. I know what aggravates the heck out of them.

Engineering Managers are architects and builders. They pull together the people, processes and technology required to build the machine that makes the software that powers the business. It’s a very big job. And it’s a whole lotta fun when the right Technical Stack and Human Stack are in place.

It’s a genuine joy when the process is flowing from specs and stories through code and integration into and out of testing.

It’s not any fun when the right tools or people are missing. That’s when the wheels of the Dev machine get wobbly. That’s when release dates are missed. That’s when irate customers complain about buggy software, apps or websites.

There’s a constant pressure to release robust products faster, and to turn out upgrades more frequently. This pressure eventually stresses the machine and it cracks at the weakest point. Where’s that?

Nine out of ten times the weakness is in the QA team. That’s where the bottlenecks and miscues tend to occur. This is when my phone rings and when I have another conversation with a stressed out engineering manager.

Let me get one thing straight here. I’m not talking about just providing your company with more testers. While having more QA bandwidth may solve some of the QA service issues, I know from experience that the core problem in QA isn’t numbers. It’s intelligence and drive.

You see, most testers are just looking for gigs until something better comes along. They might even be developers who can’t cut it in the big leagues. At TESTCo, I hire only software test engineers. These are people who live to develop and execute strategically-sound test plans.  They not only find bugs efficiently they know how to offer feedback that actually improves the entire Dev process.

What if your software engineers had perfect stories with validation test cases as inputs to work from and then had immediate validation as soon as they finished?

What would your software process, throughput and quality look like if your Test Engineers were on the same “wavelength” as your Engineers. Powerful potential, right?

Inside TESTCo

TESTCo stresses using software test engineers instead of the normal testers on many QA teams. Choosing a test engineer over a normal tester can decide the success or failure of a given QA service project. Although some of their responsibilities overlap, the test engineer and tester play different roles within a QA team.

First, there are several key differences between a tester and a test engineer. A tester can run test cases and just tell whether the software worked or not. In contrast, a test engineer can find the root cause of why software failed and craft a strategy to fix the root issue. A test engineer helps prevent bugs in the development process and is responsible for improving the overall development process of the QA team. The tester focuses more on running test cases and finding bugs before releasing the product to consumers. The test engineer’s ability to fundamentally understand and problem-solve is what differentiates them from a tester. 

The Test Engineer Advantage

A test engineer can learn your application, write test cases and organize the test cases into suites and consequently run them to write defect reports. These defect reports can be sent to your development team and they can fix the defects mentioned. A tester can’t do any of these tasks and can eventually undermine the efforts of your team; the tester can only run tests and tell you which ones passed or failed. The tester’s responsibility is to follow the given protocols and guidelines provided by the QA team. If there was something wrong in the development process, the tester could not recognize or fix the issue. 

Rounding Out the QA Service Team with Extraordinary QA Managers

At TESTCo we provide a QA Manager for every project at no additional charge. What this does for you, the engineering manager, is two things.

First, our QA Managers are simply the best at identifying the right goals and priorities to pursue considering the constraints of the situation. Even if you have a terrific QA Manager already, our team adds serious brain power and objectivity. The test plans we create are designed to deliver real business value every day. Can you say that about your current test plans?

Second,  you’ll never have to ask, “Where are we with the test plan?” This is because our QA Managers provide crystal-clear reports twice every day. You’re never waiting on QA for feedback. Equally important, you don’t have to be awake in the middle of the night to communicate with a TESTCo QA Manager. They’re located in the Central time zone and speak fluent English. You’ll understand each other perfectly.

The Many Roles of Your QA Manager at TESTCo

In addition to setting goals and reporting, a TESTCo QA manager plays many crucial roles in your QA service team. The QA manager is focused on building the most productive, high-performing QA team. Members of the QA team are often focused on the technical aspects like processes, automation and tools; the QA manager helps the members of the team see how their efforts are aligned with business objectives, product development and more. By connecting the individual responsibilities of members of the QA team with primary business objectives, the QA team will be in synergy with driving business results. 

QA Manager as Quarterback

The QA manager is also a key indicator of how well run a QA service team is. The QA manager provides direction, counseling and mentoring to the members of a QA team. This allows the individual talents of the QA team to be maximized which directly improves the success of the QA team as a whole. 

The QA managers at TESTCo are very skilled and have a track record of building successful QA teams. The QA managers are able to manage and direct QA teams towards the needs of the customers. The QA manager program at TESTCo hires and retains the best QA managers that lead the test engineer teams. Every project, regardless of size, accompanies a qualified QA manager that leads a team to execute on goals set out by customers. QA managers at TESTCo have at least 5 years of experience and one year of experience working with TESTCo. If you’d like to find out more about our QA managers, click here

Experience the Difference at 30% – 50% Less

I describe TESTCo as a boutique software QA service company. We’re not a big test factory. We’re certainly not a bunch of strangers messing with your code. We are big enough, nimble enough, and smart enough to meet whatever testing demands a small or mid-sized company can throw at us.

This includes being able to jump on a single project within a day, or handle all of your QA through many release cycles. (We are the exclusive QA service resource for many of our clients).

Below are reviews of our services written by Engineering Managers like you who trust us and benefit from delivered promises at 30% – 50% less than the cost of internal QA resources.



Strengthen the Development Machine With A Single Call

After a few minutes on the phone with me and one of my QA Managers you’ll notice the TESTCo difference. I bet you'll see that plugging TESTCo's QA service into your team will result in faster cycle times and more thrilled customers.

Oh, and you’ll see there’s a very good possibility that your job will start being fun again.

Click the green button on the page to schedule a conversation with me. I’m looking forward to speaking with you.