offshore software testing

Is Offshore Software Testing Such A Good Idea

Software still needs to be tested, even if you haven’t hired an offshore software testing service. So, what can be done? Learn what NOT To do when it comes to testing internally

  • Have the engineers test their own work. This is expensive (software developers are usually paid more than testers), and only marginally effective because developers tend to make a LOT of assumptions about what needs to be tested in the code they’ve written. Lastly, they are much better at building something than breaking something – which is where great Software Test Engineers excel.
  • Assign “other” people to test it. The “other” people are usually people within the company in customer service or marketing. This is less expensive (though we certainly work hard to ensure that offshore software testing isn’t cost-prohibitive), but it’s the least effective method because they aren’t trained testers who understand how/what to test and what to do when they find a defect. In addition, productivity and other opportunities are lost when they are pulled away from their regular work to test software.
  • Have the end users test it. This approach appears to be the least expensive but is actually the most expensive. End users that will eventually use the software to accomplish their work often experience frustration and loss of confidence in the application when they are put in this position.
  • Do nothing and hope for the best. You wouldn’t be reading this if you really thought this was an option – after all, that’s why you’re even considering offshore software testing.
  • Automate it! This is the holy grail of software testing. It involves writing a program to test a program – a very complex process that requires up-front investment and is really only valuable when you have a LOT of tests to run, very frequently, and in a very short period of time. See how On Demand (versus strictly Offshore Software Testing) can help with software automation projects.  Learn if your Agile development is wasting money on automation by checking out our reports.

But if none of these are options are ideal, especially if you find yourself reading this AFTER you’ve started a software project, you may think it’s too late to consider offshore software testing services.  But it’s not.  TESTCo can help get your software projects back on track faster than you thought possible!

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.

QA as a Service | QAaaS

QA-As-A-Service, The Missing Link For Product Managers

In This Post

QA-as-a-Service for Product Owners is more than software testing. QAaaS provides fast and easy development testing plus your business goals delivered on time and with eliminated or reduced risks.

QAaaS is a flexible way to bridge the gap between freshly coded features and your customers’ needs and desires. QAaaS is capable of testing a wide range of software systems, platforms, and applications in real-world environments and using real-world user and test cases. It uses agile and flexible processes across the entire software development life cycle from Alpha and Beta phases, through production. It is highly focused on needs and encompasses large-scale system testing as necessary.

TESTCo was founded in 2002 to serve the unique requirements of Software Product Managers. Our QA Managers and Test Engineers know the services and procedures needed to support every aspect of Quality Assurance as a Service.

You can take advantage of this experience right now, just by downloading the Product Manager’s Check List for QA.

Quality as a Service Check List

Find and Eliminate Risks Before They Become a Problem

Risk remediation is a biggie. Product Managers (and their bosses) don’t like surprises. Therefore, our QA-as-a-service reduces surprises by cutting risk. Here’s how:

  • We simplify complexity so that everyone can understand it.
  • We measure real progress towards goals and release dates.
  • We trap and control blocking issues before they stop your project.

A good example is regression testing: Nobody wants to wait through a long regression testing cycle, but releasing without one is very risky. We recommend fast regression testing through release, so there aren’t big surprises on the eve of the target release date. 

Regression testing allows you to:

  • Prevent functionality crashes: When new features are added to a product or platform, several difficulties can arise due to misalignment between the new features and old features. With regression testing, functionality crashes that can be detrimental to your product are prevented
  • Detect all bugs and defects: Regression testing also identifies all bugs and defects before they make an impact on the product deployment. These harmful bugs can be prevented, assessed and fixed before deployment. This leads to less time and money on efforts related to resolving bugs; this directly reduces the time to market for the product.
  • Continuous integration: If you have a platform or product that needs continuous integration, regression testing is vital. Performing regression tests after incorporating new code ensures that any new changes don’t affect the current performance of a product. As a product has more code integrated over time, regression tests become more beneficial.

What Concerns Product Managers

Product Managers care about more than “testing,” and some haven’t had the opportunity yet to see how the advantages of a QAaaS company can help them achieve their customer goals.

Here’s what concerns Product Managers.

  • “Oh, we should have caught that in grooming.”
  • “Our stories (storyboards) are missing something but I’m not sure what.”
  • “What are the real acceptance criteria?”
  • “QA is just an expense or tax that we want to minimize.”
  • “We’re not sure what DONE really means yet.”
  • “We need more QA, not just testing.”
  • “Are we testing the user experience enough?”

Additional concerns for product managers include doing enough customer validation to ensure the product being built is truly useful and can be validated by the customer. Customer validation drives product and platform success because it provides valuable insights before launch. Without customer validation, it’s easy to overlook features and other requirements that the customer wants.

In addition to customer validation, tracking KPIs is crucial. Tracking KPIs allows product managers to assess if new features or changes have improved or weakened any aspects of the product. Tracking KPIs exposes strengths and weakness while setting expectations and improving overall management. KPIs are some of the few ways product managers can quantify progress, so tracking it is extremely beneficial.

Lastly, it’s important to ensure that QA has all the possible use cases and protocols to verify no additional bugs are introduced. With this, QA is well-equipped with a plan of action to handle any difficulties that emerge like bugs.

When QA as a Service is Missing

Each of these Product Managers was missing something (or someone) in the QA function that if present could have had a very positive impact on the product’s goals. QAaaS provides everything you need to bridge the gap and ensure your product delight your customers.

Some problems that can arise from lack of QA include bugs and “fire” based problems. These problems can be detrimental because it can halt a customer from using a product or platform. By using QA, any bugs can be detected before they cause significant issues to a product.

QA can also be more value-oriented. It’s known that QA can detect bugs and perform similar tasks, but QA can power work in solutions architecture. This can turn QA into a deploy able utility for sales teams and customers. This helps shift QA past being a part of the product definition phase to being more utilizing in other aspects of the business. This in turn makes QA directly generate value independently (from a non-functional requirement to a functional requirement).

A Product Manager’s Dream Come True

QA-as-a-service comes through in our complete understanding of software company priorities, goals, and constraints. By gathering information upfront, we form and make recommendations, test plans, and feedback targeted to the client’s needs. Product Managers get their products delivered faster, cheaper, and better.

With TESTCo, project managers can easily communicate with QA teams. In the case of an urgent bug that stops the platform, project managers can let QA teams know exactly what problems they are experienced and the QA team will focus on fixing the bug until the platform works properly. QA teams can start addressing the specific bug at hand within a matter of hours after contact.


Testing What Users Really Want

There is much more to accurately and effectively testing a software project than just running the tests! Our Product Manager clients consistently tell us that their top priority is a valuable user experience. Yes, this does require testing to make sure nothing goes wrong – the app doesn’t crash and it provides useful information. But, there’s another aspect to user testing that’s frequently overlooked. User Value Testing – does the software project truly deliver on the promise and prompt them to return for more? TESTCo provides this as a regular part of our strategy.


Easy and Painless

TESTCo never outsources software QA testing work. Keeping the job in-house makes reaching the results both easy and painless.

Projects Delivered on Time

Test plans are accurate, followed with care and precision, and projects are delivered on time. Sprint Goals, exit criteria, and key performance indicators are clear to prevent the team’s attention and efforts from wandering. Everyone knows when they are “done” because that point is clearly defined.

Faster Development Cycles

The developers are fast when they have two things: crystal-clear stories and requirements, along with inline and real-time validation. TESTCo Test Engineers test and validate work as soon as it is completed, based on the stories and requirements.

Achieve Business Goals

Our QA-as-a-Service is designed to support the business goals of the product. You can expect us to ask what the goals are before we start. QA helps Product Managers meet the expectations of the business and their customers. QA drives the testing before the processes start and are ready when you are. 

Find and Eliminate Risks Before They Become a Problem

Risk remediation is a biggie. Product Managers (and their bosses) don’t like surprises. Therefore, our QA-as-a-service reduces surprises by cutting risk. Here’s how:

  1. We simplify complexity so that everyone can understand it. 
  2. We measure real progress towards goals and release dates.
  3. We trap and control blocking issues before they stop your project. 

A good example is regression testing: Nobody wants to wait through a long regression testing cycle, but releasing without one is very risky. We recommend fast regression testing through release, so there aren’t big surprises on the eve of the target release date.  

When the Phone Rings

When a problem occurs, or the situation gets tense and time is rapidly sliding by, Product Managers give us a call to line up a Test Engineer/QA Manager team to step in and help get the hot-spot cooled off. They appreciate TESTCo’s ability to staff a Test Engineer and QA Manager for as little as a day and as quickly as tomorrow. 

Why let those problems linger?  And least you think our being extra valuable to Product Managers means a higher price tag, you can relax. We offer comprehensive solutions that increase ROI. 

How QAaaS Can Fit into Your Team

Your goals are our goals! Bringing an outsourced team into your software project team can be a big challenge. At TESTCo, our goal is to fit seamlessly into your team and processes without any disruptions. Our scoping process helps us uncover all the information we need to build a strategy to work with your team without disruptions! At a minimum, you’ll hear from us twice daily. But, if your team has stand up meetings, our Test Engineers and QA Managers sure like to be included.

Must-Haves To Elevate QA’s Contribution

When QA managers have access to accurate information and general business objectives, they are in a better position to provide value. Some of the ways to improve QA’s contribution to your business includes:

  • An understandable report with the exact features completed and tested every day. It’s important to emphasize that the features must be completed and tested twice daily.
  • A detailed understanding of your business and technical goals; this should include the current daily status of your sprint and your specific priorities in your business
  • A good foundation of regression testing along with measurement of coverage. This should be old-fashioned test cases built over time and then consequently run as a final regression prior to release. This will prevent surprise defects after launch.
  • Weekly product quality meetings with project QA manager: During these meetings, software development, quality measures and processes will be reviewed. This will prevent missing estimates and buggy code.
  • Daily software testing by a test engineer.

Maximizing Your QA Manager

Having great communication with the QA manager is vital because they are deeply ingrained into the projects and testing teams. QA managers play different roles and can serve many functions for your business. Incorporating your QA manager in decision-making when it comes to QA teams, hiring, etc. can be very beneficial due to their insights. Some avenues of maximizing your QA manager include:

  • Project leadership: QA managers can help you understand risk areas, identify goals and give you an estimate of what a QA team can produce for your business. The QA manager is involved in almost all projects, so they are the best resource for project leadership. QA managers are knowledgeable on client fears, risk areas and any technical concerns that come with certain projects. By utilizing the QA manager for input on projects, you’ll always have a good idea how a project is going and what are some potential difficulties that can arise.
  • Education: QA managers are a great resource when educating engineers, testers and any other members of the QA team. QA managers know what skills and knowledge the QA team has and how new training can be incorporated into the team while performing normal day to day functions for clients. Consulting with QA managers prior to any education or training programs for your business is crucial. Their insight can provide you the most cost-effective ways to educate your staff
  • Recruiting: Additionally, QA managers can help recruit talented engineers to reach your business objectives. QA managers are the best resource at assessing talent for your QA team. They know the specific tasks that are demanded from the QA team on a day to day basis; this is very beneficial in interviews because the QA manager can assess talent on the spot. Assessing talent is not only limited to technical skills, aspects like culture-fit and soft skills are important to finding the best fit. The QA manager also knows where to find the best talent for your QA team locally and remotely; this can include professional organizations, schools, etc.

How might we help you deliver your software faster, better and cheaper? I’d love to hear from you. Give me a call at 888-254.9709, or request a call back using the green button on this page.


Thanks to Richard Howes for contributing to this post - JCH

Software Application Testing Company Three Questions

Software Application Testing Company Three Questions

There are just three things to think about before contacting a software application testing company. Yep, just three little questions to ask yourself once your software is “almost” ready and it’s time to have a professional take a look to make sure there aren’t any nasty little surprises left in there.

Trust me on this–if you know the answers to these three questions, I can promise that you’ll find the perfect software application testing company for your unique needs.  I promise!

On the other hand, if you don’t know the answers to these three questions, the best any application testing company is going to do is *guess* or *assume*.

I’m pretty confident you don’t want the company you’re seeking help from to *guess* or *assume*, do you?

Answer These Questions Before Contacting Any Software Application Testing Company

1 – What are your goals for this project?

Specifically, the list of things you want done (and NOT done) and the list of things you want to see so you can be confident the goal has been achieved. Nothing complicated – even some jots on a napkin will help. What’s MOST important here is that you’ve thought about it enough to be clear about what you do and don’t want.

Why? Software quality means different things to different people. Google is OK with some defects in their software (permanent Beta) while high-end jewelry stores are not willing to tolerate even a slightly-less-than-perfect image.  Either approach is effective but only in the context of your specific needs and goals. If you know (or have at least thought through) where you stand on your goals, the application testing company you’re talking to can do a much better job of understanding and meeting your specific needs and goals!

2 – What is your budget for this project?

Yeah, the budget question….and budget is more than just dollars! Possibly more important is TIME. When do you need it to be done? You probably already know this but it’s important enough to make sure. Take a minute and confirm the dollar budget you have to spend and the date by when you need to launch the application.

Why is this important to know and SHARE? Very simply, it helps the application testing company you’re talking with do a better job of understanding and proposing a solution that meets your unique needs. If you withhold this important information under the guise of an outdated and ineffective vendor negotiation model, you’ll get quotes and proposals that are more guesses than fact. What you get is a best-guess for a solution where critical facts are missing. Further, if you award the project based on this approach, you’re merely awarding the “best guesser”.  That’s probably not what you were seeking when you went looking for a software application testing company. The good ones don’t *guess”.

3 – How will you chose the best vendor for you and your project?

Some folks have a need for speed and others have a need for deep attention to detail. Some want a very close relationship between developers and test engineers and others don’t want their developers bothered. Some people want lots of transparency in the process and some people just want the defect reports. Decide which methods and priorities best meet your needs.

Why? If you share your selection criteria with the application testing companies you’re talking to, they can customize their proposals to highlight their differences and how those differences can be valuable to YOU. If you don’t, everyone is back to guessing and that’s not going to improve your certainty of success. In some cases, time can be saved when a firm quickly determines they are NOT the best fit for your project. Wouldn’t it be better to acknowledge that and get out of the way instead of endlessly pestering you for another sales call?

A good software application testing company, like TESTCo,  is not in the guessing business. We’re in the facts and confidence business. Please help us help you achieve your goals and dreams. Think through the three questions the best you can, then give us a call.

 

Website Testing Services

Website Testing Services for the Average Bear

When it comes to website testing services, you might not be smarter than the average bear. Or, you might not know if you are.

That’s OK, I can help you sort through some of the techno-babble about getting some help with website testing so you can quickly become smarter than the average bear.

You see, when it comes to software testing, hunting, farming, being a Dad, or training a dog I am smarter than the average bear.

If you ask me about psychology, event management or finance then I’m definitely not smarter than the average bear. Best we stick to the subject of website and web app testing right now, okay?

Cutting Through the Clutter of Website Testing Services

As I scanned internet articles to see what was being written on the subject, I noticed a few things that could be confusing or misleading to the average bear.

Let me sort through those things now to help you find an outsourced website testing company that work best for your unique need and business goals.

Set the Right Goal

First, set a goal. Know what you want.  A SMART goal  is great – even if you don’t know all of it.

But, you may not have a “goal” and that’s OK, too. Use these simple questions to figure out what you really want from your website testing services.

  1. Do I want website testing because it’s something I “should” do or because I’m concerned about the cost of losing customers and prospects to bugs and glitches? This answer will help you (and us) understand why you want website testing services.
  2. What does it cost me to get a new prospect to visit my website or eCommerce store? What is the lifetime value of one of my customers? This answer will help you understand the risk of loss from bugs and glitches that website testing can help you prevent.
  3. Do I have time before I need to release my website to fix the bugs and glitches that the website testing finds? This answer will help you understand if you will get real value from your website testing work.

There are not any right or wrong answers to these questions. The answers are important but the thinking and reasoning you do while answering those questions will shed light on what you really want and we can easily help you turn that into a website testing services goal.

Here’s why knowing your goal is important. Testing is an activity – and it can be performed for as long as you want it performed – regardless and without respect to your goal.  You’re probably more interested in the outcomes of testing – defects, bugs, test plans, test cases, etc – than just knowing someone is testing it. If you know your goal before you start looking for help with website testing services, you’ll get the outcomes you’re looking for. Otherwise, you’ll definitely get some “testing” but you won’t know if it is helping you achieve what you actually want.

Don’t Be Over-Sold by Tool Vendors

Second, Tools! (Hat tip to Tim the Toolman, who always got excited about tools and machines.

Almost everything I read on the internet about website testing services seems to be about how a great tool can solve your problem.

Yeah, like having a hammer get’s you a birdhouse. Not so much. Tools are only as good as the person using them. So, this begs two questions.

  1. How long will it take to learn how to use the tool?  They seem easy in the demo but have you actually tried using it?  It may not be as easy as you think.
  2. Even if you know how to use the tool, will you know where to use it most effectively? Just because you can easily and quickly run a bunch of tests, how will you know they are the right tests applied to the right place in your website?

Humans are more important than tools. Tools help humans be more useful.

The Human Element in Website Testing Services

Third, Testers! Now we’re getting to the heart of the matter.

I’ve learned that there is a difference between a Tester and a Test Engineer. We don’t hire testers and you should look very carefully before you hire them yourself.

Here’s why.

Testers do very well when they are told what to do. They don’t do so well when given a testing problem to solve.  They just don’t have the mindset, education and ongoing training to come up with good alternatives or judgment to select the best course of action.

Test Engineers are seekers, finders, and solvers of quality problems. They have university level degrees in math, engineering, and computer science and are actively engaged in ongoing training in quality assurance and control. Sure, they cost a little more – so does a nice car – for a great reason. They both deliver more value per dollar than a less expensive choice – like a tester.

Name Dropping in the Buzzword Jungle

Fourth, Buzzwords like AI, Services, Technology, Systems, Industry, Functional, Performance, Security, Usability can lure you into a trap. Remember, you’re hiring website testing services, not a copywriter.

When it comes to website testing services, having deep knowledge and experience in some set of buzzwords is far less valuable than having seen and completed hundreds of website testing projects.

TESTCo is focused solely on providing the best website testing services for your business. The buzzwords used to sell you on testing services won’t help fix bugs in your code or ensure your application works well when it’s released. We have decades of experience when it comes to solving testing problems that are similar to yours. Instead of writing about buzzwords to entice you to select TESTCo for services, we are focused on providing real testimonials and consultations so you can see our services firsthand.

If you’re looking for a match between your situation and what the website testing services company can provide, look to the references and testimonials and give them about 10 times the weight you’d give to their buzzwords matching your buzzwords. Even better, reach out and talk to the reference/testimonial yourself!

Trust Your Brand to a Crowd of Strangers? Really?

Fifth, there’s the whole crowdsourcing thing.

Sure, some things might be better, faster and cheaper when crowdsourced. But, when what you’re interested in crosses the line from “opinion” to “expert advice”, you’re probably going to get better and more valuable results from an expert rather than “the crowd”.

I know (and so do our clients) that a dedicated QA Team with a QA Manager and a Test Engineer, even for a tiny project of a day or so, can deliver a far more valuable set of results than a semi-random group of internet users.

Crowdsourcing your brand can lead to unpleasant outcomes.

Customer Churn: The entire focus of testing is to make sure that your product is as smooth as possible when it’s released. Relying on crowdsourcing can lead to significant customer churn due to unresolved bugs. All of the marketing efforts it took to make users choose your product will be wasted if there are bugs whenever your release a new version of your product.

Technical issues: Crowdsourced testers are compensated if they find bugs or issues within your application. Generally, most testers are not as qualified as test engineers and cannot deduce the core root issues within your application. Hiring crowdsourced testers may lead to you overlooking the fundamental issues that are causing bugs. This will continue repeatedly until the core issues are resolved.

Confidentiality: One of the biggest drawbacks of crowdsourcing your testing is the breach and lack of confidentiality. When you crowdsource your testing, there’s no incentive for testers to be loyal to your brand. This can lead to the leakage of sensitive business information and other trade secrets. A competitor can offer one of your crowdsourced testers money in exchange for critical information. This can lead to the demise of your business.

Automate All the Things!

Lastly, there’s automation. Automation really means using test automation, AI or Machine Learning software to perform a task. If you believe what you read, then literally everything can be automated – especially “low skill” activities like data scrubbing, sending emails and software testing.

There are 2 challenges to successfully automating anything with these tools.

  1. Automation Tools don’t run themselves. Someone has to instruct or configure the tools. Even then, an incorrect or old instruction can cause a bucket load of False Positives. This might cause you to spend more time diagnosing and fixing your automation tool than just performing the task with a human in the first place. If you’re going to use Test Automation, you might want to consider that you’re writing more software to test your current software. Who’s going to watch the watcher?
  2. Website Testing is a “low skill” activity. I beg to disagree with this idea. Yes, Testers, doing what they are told and manually running a known set of regression tests for the 32nd time is a low skill activity that should be automated. But, that’s not a common problem and probably not your problem. Most website testing challenges aren’t known and aren’t covered by a test case that you know about ahead of time. Most of the defects discovered during website testing aren’t covered by a test case. Testers will seldom find these defects because they aren’t obvious. Test Engineers, however, will definitely find them! Quality and Test Engineering are definitely not “low skill” activities.

Automated testing provides several hurdles for business prior to even getting testing started.

Initial cost: The initial cost of using automated testing is very high. For automated testing to work properly for your products, it will have to be configured and tailored to your business operations. This configuration along with the staff needed to make this happen often costs more than the budget for testing. In large corporations this may be cost-effective, but for the average business this is very detrimental.

Maintenance: Automated testing isn’t a one-time service, it requires continuous upgrades and maintenance just like many parts of your business. The key difference in maintaining automated testing is that it will likely require additional personnel on top of your current payroll. The hardware, software and staff needed to maintain automated systems will easily add five figures to your current payroll each month.

Expertise: In-house automated testing will require the additional staff you hire to have technical backgrounds. Basic programming skills and knowledge will be required because scripts will need to be completely understood. The tools that are used for automated testing may have their own defects, so staff must be able to resolve that as well.

So, before you drink the flavored punch that say’s “automate all the things”, double check your goals and constraints. You might not have the time and budget to “automate all the things” and you probably won’t be happy with your first set of outcomes, either.

The Things You Really Want

What you really want with website testing services is confidence and speed. You’re at the end of a long journey building a new website and you’re not in the mood for a long, drawn out, testing phase just when you’re ready to launch you new “look”.

You’re probably not sure but suspect that there might be a few bugs or defects in your website. You’ve done your testing but still aren’t sure. You want to know that your website will be flawless for everyone that visits.

You’re also probably tired from all the hard work and concentration that it’s taken to get your website to this stage. You’re ready to be done and you’re not in the mood for a bunch of back-and-forth with a website testing company that just doesn’t understand where you are and what you want.

When we talk with you about your project, we’ll get a keen understanding of your risks and concerns and build a plan and proposal to complete our work quickly and efficiently so that you can move your website project forward and claim your new customers and prospects.

At TESTCo, we believe in honoring promises. We take the time to make sure our testing work focuses on and delivers the value you need to achieve your business goals. Here’s a page about our website and web app testing services.

We want to help you achieve your business and technology goals.

offshore software testing

Offshore Software Testing: What, How and Why

Offshore software testing is on the verge of being “commoditized”. If you subscribe to this notion and are not a software QA expert, you may be making a costly mistake.

The Maturity of Offshore Software Testing

Offshore software testing – where software testing services (and many others from manufacturing to IT support to legal work) are delivered from another country and possibly another timezone – is at least 30 years old. There is very little that is “new” in the pursuit of better labor and lower costs.  In fact, some aspects of offshore services have seen a “recall” to the home shores in the recent years as cultural challenges reduce labor quality and prices increase in other countries as the standard of living rises. Almost everyone has a personal horror story about an aspect of offshoring. The relentless pursuit of lower costs has now met and must confront the quality and value of the services received.  In most, cases, the value received no longer justifies the cost paid. But, there are still nuggets of gold to be found – if you know how to find them!

What is Offshore Software Testing?

The “What” of offshore software testing – writing, running and reporting software tests – is a simple one. The desired outcome from software testing is a positive or negative indication on a test case. Almost anyone can be trained to do all or some portion of this work. In most cases, the goal of the work is some volume of activity and outcomes – test case and test run coverage are commonly used metrics for this activity.

“No Defects Found” Does not Mean that Your Software is Good Enough for Your Customers

The problem with using “What” as your primary criteria for offshore software testing is that it relies on a false assumption that some “number of defects found” based on “test cases run” results in high quality software. This is not always the case and the fundamental difference between software testing and software quality! It is almost impossible to write and run test cases for every possible combination of features within your software application. Just because no defects were found does not mean that your software is good enough for your customers!

How is Offshore Software Testing Done?

The “How” of software testing covers methods, standards, tools and procedures used to perform the writing, running and reporting of software tests (the “What”). When software testing work is performed, how it is performed, who will perform the testing and where it is performed – all influence the value of the outcomes. There is a big difference between a newbie running a set of tests someone else created during a normal workday and an experienced Test Engineer building and executing a manual functional test plan over the weekend.

Both produce standard software testing outcomes (the “What”). One is more valuable if you are in a situation where money is more important than time. The other is more valuable if time is more important than money. Clearly understanding this is critical to making a wise choice for an offshore software testing partner.

Sure, methods, standard, tools and procedures are useful – we use them frequently at TESTCo. But, using methods or procedures as a primary selection criteria has a big potential flaw – not all methods or procedures are implemented the same and your definition of “Agile” may not be the same as someone else’s. Putting an offshore software testing partner’s Agile Software Testing method into your Agile Software Development Team’s process may or may not work!

Why Use Offshore Software Testing

There are two good reasons to considering using offshore software testing.

One reason is to pay as little as possible for a commodity service that you need. We don’t subscribe to this notion for several reasons.

  • The lowest cost seldom equates to best value – this results in an expense rather than an investment.
  • The talent required to deliver lowest cost service is typically not experienced and trained in software testing – you can do better.
  • Low cost talent delivering commoditized services does not allow us to deliver the Real Value Every Day that we are committed to.

We optimize for talent first and cost second so that we can offer very talented software test engineers coupled with QA managers at a reasonable price.

The second reason is to honor your promise to deliver software that your customers love and depend on.

We believe that all software has an inherent promise to the customer of distinct value – increased revenue, cost savings or enjoyment in exchange for some amount of money.  Bold promises are needed to attract and retain customers in today’s crowded marketplace.  Bold promises require investment and talent.  Weak promises don’t require much and seldom survive very long.  Building great software requires unique talent – analysts, developers and quality assurance.  Scrimp on any of those three aspects and your delivery on your promise will suffer.

The TESTCo Difference

At TESTCo, we believe talented software test engineers trump software testers at least 2 to 1, if not more. We only test software and we only hire experienced software test engineers.  If you are struggling to release quality software that your customers appreciate and depend on, we have the people that can help you honor your promise to your customers.

If you think you need help with offshore software testing, we’d enjoy the opportunity to learn more about your needs and explain how TESTCo can help you honor your promises to your customers. A quick 30 minute phone call is usually more than enough to learn about your situation and answer all of your questions about how TESTCo can be your offshore software testing partner.

Outsource Quality Assurance

Outsource Quality Assurance? When is the Right Time?

In This Post

 

There will be a time when you wonder, “When should I outsource quality assurance for my software, websites, or mobile aps?” It’s a great question as there are times when outsourcing QA makes good sense and there are times when it doesn’t. Let’s look at a couple problems where outsourced quality assurance may or may not help you.

Running Late. Is Now the Time for Outsource Quality Assurance?

You’re running late on delivering your project and testing is always the last gate to clear.

You’re responsible for the quality of your software. When there are problems, it’s *your* phone that rings. You have a bunch of new features and several bug fixes that are almost ready for release. You just need to get the new features tested (again) and a full regression test suite run to make sure those old bugs got fixed and that there aren’t any new ones. It’s just you and one tester and the pressure is mounting to get the new software released to your customers.

Do you …

A – do the best you can with what you have?

B – ask for help from your peers?

C – seek help from quality assurance outsourcing?

If you do the best you can with what you have – you and your tester – you’ll make progress but probably can’t make any promises about the actual quality of the release. Everyone will just have to hope for the best and take what they get. Yeah, your phone is probably going to ring …

If you ask for help from your peers – the programmers and folks in marketing – you’ll probably get help. But, will that *help* really help? Yeah, you’ll get some tests run, but it probably won’t be a coordinated and planned strategy for software quality. It will be a bunch of testing and while it’s better than just doing the best you can, you’ll still be left with hope and getting whatever you get. And yeah, your phone’s probably going to ring if you use this approach, too.

I’m Unprepared! What Do I Need to Get Started?

You want help with your outsourced software testing but are worried you’re not prepared enough. Test Cases, Test Plan, Test Datasets, Testing Sandbox – the list can appear to be endless and daunting.

All you really need to get started with TESTCo for your outsourced software testing is a goal and a strong desire to be helped. We WILL need a goal for your project but if you’re not really clear on what it might be, no worries, we’ll be happy to help you set a powerful goal for your testing project.

And, no need to worry about missing test plans, datasets or a sandbox. We come with a full toolbox of everything we could possibly need to successfully complete your project.  And Test Cases? No Problem – we’ve got you covered there too. We can help you build everything you need to achieve your goals in this sprint and the next sprints as well.

And, lastly, in some cases, depending on your goal and constraints, you might not need everything you think you need. Many times, project speed is more important than the re-usability of testware so it might not make sense to build a lot of testing assets when you just need the confidence that your project is high quality and you need it Real Fast.

Being prepared is mostly having a clear picture of your goals and constraints for the project. We’ll help you fill in everything you need to achieve your goals within your constraints.

Reaching Out

If you seek help from TESTCo, a long-standing quality assurance outsourcing company, you’ll get a thorough strategy, proposal and plan within a day and we can start working for you in as little as a single day. We’ll run your test strategy and plan and report twice daily so you’ll always know where things stand and exactly how good your software is. Call me anytime to talk about how we can help you! 888-254-9709