Software Test Engineer

Software Test Engineer or Software Tester

There’s a big difference between a software tester and a Software Test Engineer. The choice you make can be critical to the success of your software development project.

Testers run test cases and give you a thumbs up or down as to whether the software worked. That’s fine and works fine in some cases (perhaps 10% of real world software development scenarios).

Test Engineers, on the other hand, plan, design and conduct relevant test cases while showing you exactly what is broken and why.

Sometimes testers are a good fit for your needs, and sometimes they’re not.

And here’s a little known fact. Testers can inadvertently kill a project because of their limited capabilities.

Eventually you will need to make this important distinction. The following discussion will help you make the right choice.

A Recipe for Success – Move Beyond ‘What’ and Understand ‘Why’

When you don’t want any analysis with your testing, testers are fine. If you use testers only, however, your development engineers will eventually have to spend extra time to backtrack and figure out why the test failed.

With basic testers, the “why” and “how” pieces are missing – and that adds to your workload and the workload of your developers. Someone on your team has to figure out all of the details and then circle back to the testing team once adjustments are made to the code.

When you want to move beyond a simple pass/fail paradigm – and really improve the quality of your software, you need to enlist the help of Software Test Engineers. Test Engineers help you understand the problem and work through it more efficiently. They save you and your developers hundreds of man-hours of guesswork and trial and error exercises.

Don’t be Deceived by Titles

A lot of companies think they’ve hired Software Test Engineers when, in fact, they’re using testers. To make sure you know which one you’ve hired, ask yourself some questions:

Do your Test Engineers bring analysis and interpretation to the table? No? Then they’re testers.

Do they deliver defect reports plus enough information to actually fix the problem on the spot? No?.. again, testers.

With a Test Engineer, you can answer these questions in the affirmative.

Test Engineers help you understand what went wrong and how to fix it. That’s just not in the tester DNA – they’re a simple binary filter for pass/fail.

TestersTest Engineers
Run test cases and tell you which ones don’t pass.Learn your application, find gaps in the requirements, design the coverage needed per your quality goal, write test cases, organize them into suites and then run them so they can write defect reports that your developers can immediately take action on.
Tell you when your test cases don’t work anymore.Keep their test case suites updated to match the application’s changing functionality.
Testers run as many test cases as they can to get test coverage.Compare their test case suite to their functionality matrix to make sure that the right areas of the application are being tested at the right time – and then measure how much coverage they have.

How to Eliminate Delays, Worry and Project Failure

As you can see, there’s a big difference between these two different roles, and it has a huge impact on how quickly you can get your software released.

If you haven’t guessed already, TESTCo uses Software Test Engineers exclusively. We’re committed to doing a highly-professional, thorough, time-saving, money-saving job when it comes to your software testing.

The way to accomplish this is to build the right team from the beginning, eliminate guesswork and fix it right the first time.

There’s no need to put up with service that delivers anything less. Don’t make the mistake of hiring testers and then putting up with them. All you’ll do is complain, move on to other testers, hope for improvement and then make the same mistakes.

What you deserve is optimized software development and quality… as soon as possible.

A Software Test Engineer allows you to deliver on that promise. Just check out what our clients have to say about it.

Experience the Difference a Software Test Engineer can Make

We’re happy to speak with you about your testing project for software, mobile app, or website. TESTCo is flexible enough to handle small on-demand projects, and on-going QA outsourcing initiatives.

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 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.

Web Application Quality Assurance

Four Perspectives, One Recommendation for Web Application Quality Assurance

Building an excellent web application is hard, especially if your web application quality assurance isn’t what it should be.

But, you can make it easier if you do a little thinking and preparation about QA prior to starting your web application project.

Your quality assurance and testing methods will determine how efficiently you and your team deliver your web application project and achieve your goals. That’s right. QA is often the critical factor even though it is typically the last or next-to-last phase of a web application project.

The Payoff for Success and the Cost of Failure

You might be wondering, “Is web application QA worth it?” This is a great question, particularly in light of the limited budgets that we all have for our projects. Your web application project is probably important to you and your business. You probably expect to grow your business with this project, right? You’re making an investment in your business and you expect a return, right? This is the Payoff of Success for you!

But, your web application project could fail, too. You probably won’t see a complete and total crash of your server. In fact, it’s what you WON’T SEE that will hurt you.

The payoff for success for using web application QA can be very lasting. This is because web application QA will save you money in the short and long term due to the reduced development costs and the growth it provides.

  • Reduced costs: This might seem counter-intuitive because paying for QA services seems to add to your costs. In order to fully understand how QA reduces cost, you must understand the steps within software development where you can be charged. Web application QA identifies and eliminates bugs within your application. Just by taking care of bugs early on, QA starts saving money for your application immediately. With fewer bugs and catching all the other problems early on, the costs for development initially can be greatly reduced.
  • Growth: One of the most important aspects of growth is reducing customer churn. With web applications, customers can leave your app for many reasons. Bugs, slow performance and other user related issues are some of the primary reasons that customers abandon apps. QA can test your application at all stages of development to ensure the least likelihood of customer attrition and churn. With QA, your application will retain more customers because it will not have bugs and it will perform much better.

What are your biggest risks without web application QA? In most cases, losing current customers is your biggest risk and not converting new prospects is your second biggest risk. What you probably WON’T SEE is current customer or new prospects that experience a “bug” in your web application. Not a big BUG, but just enough to cause them to feel uncertain or frustrated. They either COULD NOT do what they wanted or they were SURPRISED and CONFUSED when the see an unexpected error message.

This can have several multi-layered consequences that can damage your business. The customers that had difficulties with using your application because of a bug can generate bad marketing for your application. This bad publicity with your application can damage your brand significantly. What do these customers and prospects do when this happens? They LEAVE your web application and your business suffers from that loss.

Web application quality assurance can help you find and correct these before your customers and prospects get a nasty surprise.

And, It’s Easier than You Think

How hard is adding web application QA to my project? Adding  testing and quality assurance to your web application project is much easier than you think – even if you’re nearing the end of your project.

Here’s how TESTCo makes it really easy:

  1. Contact us via our webform and we’ll get in touch within 1 business day – sometimes within a few minutes!
  2. Schedule a 30 minute phone call with us so we can answer your questions and learn a little more about your project.
  3. If you like what you hear as we answer your questions, then schedule a 90 minute scoping with us where you “Show and Tell” us about your project. We also have a list of questions we’ll ask so we can prepare a custom proposal for your project.
  4. Within a day or so, you’ll receive our proposal that contains several strategies that we’ve evaluated and a recommended strategy, plan and estimate for your project.
  5. Tell us when you want to start!

Your investment of a couple hours could turn into a game changer in the quality of your web application project. We ALWAYS find defects.

Consider These Four Perspectives to Dramatically Improve Your Success

  1. Technical Accuracy – is your web application built on a technology stack that is mature and aligned with your project goals? What risks does my technical stack add or remove from my web application? Or is it based on your lead developer’s most current fascination with a new technology? Proven technology stacks that are purposely built to match your project’s goals can eliminate up to 50% of your web application quality assurance time.
  2. Functional Accuracy – are your requirements and specifications documented and stable? Word-of-mouth testing (where your developers tell your testers what needs to be tested) is a terrible strategy and almost always results in post-launch defects. Usually big ones! Documenting your requirements and specifications provide a road map for your web application quality assurance team to build accurate and meaningful test cases that reflect exactly what you web application does.
  3. User Accuracy – what do your users expect when using your web application? Are they Mobile First or are the desk-bound Knowledge Workers? Do they already know everything they need to successfully use your web application? What kind of prompts, help, support or training might they need? Can those basic user needs to eliminated through features in your web application? What browsers and operating systems do they use? Knowing how your users will use your web application can reduce your web application quality assurance time by as much as 25% by eliminating unnecessary scenarios.
  4. The Cost and Certainty of Success – You want to achieve your goal. You’ve invested time, money and a little bit of yourself in the pursuit of your goal. You’re close and now you want or need some testing to finish and launch your software. Web application quality assurance reduces the risk of failing to achieve your goal. Do you know what you’ve invested, thus far, to achieve your goal? Does each unique user represent a potential sale? Would a defect prevent that potential sale? You don’t “have” to test your software if you’re OK with the potential cost or revenue loss of a defect. And, you (or we, or anyone really) won’t catch and prevent every defect. How many defects can you afford before you fail to achieve your goal?

The first three perspectives focus on the technical side of making your application work. The technical accuracy perspective focuses on ensuring that the fundamental tech stack of your application is right. This is vital because without the right stack, the rest of the application will crumble. The functional accuracy perspective focuses on strategies and actions of your QA team to make sure the application is flawless post-launch. User accuracy focuses on enhancing the user experience and solving other user-based issues, while the fourth perspective focuses on the business and objectives of the project.

These four lenses examine your approach to QA and your application from a holistic perspective. Each perspective addresses a business or technical need that are required to be solved prior to application launch. By viewing this from all of these angles, you will have an answer to any issues that arise during testing and development. These are important questions to pose to any QA provided and your internal team. If they cannot figure out specific questions like why your application is using a specific technology stack or what can your users expect when using your application, this can lead to more fundamental and root issues with your application. The questions provided should be explored periodically throughout the testing and development stages until the application is thoroughly refined and ready for the market

A Recommendation from Me to You about Web Application Quality Assurance

Get talented help! – You wouldn’t ask an inexperienced designer to build your UI/UX, would you? You wouldn’t hire a HTML coder to build your web application engine, would you? Of course not!

We recommend that you hire the best software testing talent you can find. Be aware that there is a difference between testers and Test Engineers.

If you’re in the middle of a web application project and need quality assurance help, we can help with on-demand testing.

We’ve saved more than one development project at the last hour.

If you’re just starting or just thinking about your next web application project, give us a call. We’re happy to share what we know so your QA plan will contribute to the success of the project.

Website Testing Service

DIY Website Testing


 

You have a website – an important website –it represents your company (or is your company), and you want to make certain it works properly. You know the site should be tested, but should you consider a website testing service, or gather a few employees, friends and relatives together for an afternoon of testing while munching on pizza? One option costs money, the other doesn’t (okay, you have to spring for a few pizzas).

You might ask yourself, what do other companies do? The sad truth is that too many businesses either don’t test their websites or just do it poorly.

They pay for it on the back end — high bounce rates, abandoned shopping carts, customer complaints and not enough lead forms or converted sales.

Some folks just semi-test it on their own computer/phone and call it done. Who needs outsourced website testing services, right?

While that’s  better than nothing, it leaves you wide open for delivering a user experience that hurts your business. Let me make it simpler and easier for you with this report.

What follows is great advice for setting up a test plan for your website. I’ve even included a link to a free report, “Website Testing Cheat Sheet”.

What Does It Take To Test A Website Yourself? The DIY Method.

First, you’ll need a Goal, a Strategy, and a Plan.

Sure, you can just sit down and start testing but you probably won’t get what you want. Why? Because you’re just performing semi-random testing to see if you can find some “bugs”. Sure, that’s helpful but not very economical or efficient. Additionally, if you aren’t careful with documenting and reporting the “bug” you find during your website testing, you won’t be able to determine if and/or when that “bug” was fixed.

Set The Goal For Your Website Testing Project

Zero defects? Works okay for 90% of users/visitors? No critical defects but some annoyances are okay? You’re about to spend your time or money in a business activity, so you DO want a return or positive outcome for your time and money, right?

If you know what your quality goal is, then you can easily determine how much time and money it’s wise to spend in achieving that goal so that it does produce the outcome or return that you desire.

This holds true for doing it yourself or using a website testing service. Knowing your goal helps you determine the best budget for your website testing project and achieving your quality and business goals.

Make The Goal Realistic

Your quality goal for your website testing project needs to be realistic and relative to your budget for time and money. If you have little time and little money, you won’t be able to achieve a stringent quality goal. A “Zero Defects” quality goal for your website testing project can be expensive and time consuming to achieve. This type of goal is worthwhile for moon landings and space shuttle docking but doesn’t always make sense for a website.

A better goal for your website testing project may be “Works on 90% of known customer browsers and devices”. With this type of goal, you can easily calculate the number and variety of web browsers and devices that need to be tested within a small website testing project budget.

Now That You Have Your Goal, What Is Your Strategy?

A Quality or Testing Strategy is a collection of Assets (people, resources, time, money, etc.), each with a unique Advantage that can be used or perform a certain Action to achieve your goal.

One strategy is DIY Website Testing – Use your time (Asset) where you are experienced with your application (Advantage) and is already paid for (Advantage) to run ad-hoc tests (Action).

Another strategy is Outsourced Website Testing Services – Use trained professionals that you pay (Asset) who have and use an industry standard testing strategy (Advantage) to build and run a regression testing suite (Action).

These are two very simple examples among countless quality and testing strategies. The best strategy is the one that achieves your quality goal for the lowest cost with the highest outcome or return.

It might help to think of strategies as various ways to optimize Faster, Better and Cheaper!

Every strategy needs a plan to coordinate the Actions of the Assets with Advantages (Strategy) that you’ve selected.

Is It The Plan Or The Planning?

Plans are important for every website testing project. But, at TESTCo, we’ve learned that the planning is much more valuable than the plan. Why? Most plans blow up within the first 10-20% of the time allotted. The requirements might or might not change but some of your assumptions are almost guaranteed to be wrong or change. The environment or situation around you is the most common change that impacts a plan for website testing projects. Someone always seems to need something sooner than they thought previously. Or, your best and most important technical person goes on an unexpected vacation. What happens to the plan when something changes or goes wrong?

You replan–and quickly!

But, the second (and third and fourth, sometimes) time you replan, you’re smarter and more effective in your planning. Why? Because you’ve already thought through most of the requirements and assumptions and you’re simply factoring in changes. You get a little smarter and a little better every time you need to replan. And, almost every replan provides better outcomes and greater accuracy.

At TESTCo, our website testing service plans tend to be very accurate, but only because we’ve done so many of them and already have backup plans and test engineers ready to go if (and when) a change happens.

So, Why Plan (or Replan) If It’s Going To Blow Up Anyway?

Great question – because your project and team need your leadership and management. They (maybe just you sometimes) need and want to be told what to do to achieve the goal they’ve agreed is important. They need to know you have some level of confidence and certainty in the project and your plan is a primary component to communicate your confidence.

Website testing services appears to be quite simple. But, with mobile devices and browsers changing and upgrading frequently, a plan to achieve your specific goals will always your best friend.

Planning is even more powerful. A plan just communicates the timeline and the outcome. The process of planning involves (or should involve) almost everyone on the team. Planning provides the opportunity to raise, discuss and resolve issues and doubts about achieving the goal. Talking and discussing how you will achieve a goal will almost always trump a Gantt chart or project plan. Sure, you need the plan but the gold is mined in the plannING!

So, go ahead and replan that rascal if your current plan isn’t on track!

A Quick Checklist To Cover the Basics Of Website Testing

Does it work properly?

  • Does every input form correctly save the data and send the appropriate emails?
  • Does every link go to the right place?
  • Does every page and form work properly, even when you use the Back button on the browser?

Does it display properly?

  • Does every page load quickly and fully?
  • Does every graphic render fully and completely?
  • Does every animation display properly?

OK, that’s it.  Congrats, you’re done.

Oh, Wait a Minute. What About Mobile?

Which browser did you use when you tested?

And that browser was running on which operating system?

Oh, you used your phone…great!

OK, which mobile browser did you use?

And what type of mobile device do you have? Apple or Android?

And what operating system version does it have?

Wait! Why are you asking me all these questions??????

Well, here’s a dirty secret about websites and today’s web browsers on desktop and mobile devices.

They’re all different and they all have different “issues” with how they try to display your web designer’s newest and coolest graphics and display treatments.

What does that even mean???

It means that your website may look perfect on a Mac with Safari but render terribly on an Android phone or iPad running the previous operating system.

There are literally hundreds of different possible combinations.

Selecting The Right Browsers And Devices To Test

There are two references to consider when deciding which browsers and devices to test in your website testing project.

  1. Browser and mobile device market share information is frequently published on the web.  Find the most recent research report (I won’t link here because they change frequently, just Google it) and note the most common browsers and devices.
  2. Check your website server logs (or a web analytics application) and find the one that tells you which operating systems and browsers your visitors are using.  No need to test for browsers that aren’t popular and aren’t visiting your site.

Match list #1 against list #2 and pick the combinations that are most popular in the market and most used by your website visitors.

Now, you have your list of devices and browsers (we call them flavors).

You should probably have about 6-12 flavors.

Now, you simply run the same tests on this list of browsers and devices that you ran on your own browser. You can begin to understand why hiring an outsourced website testing service makes sense in a lot of cases.

But I Don’t Have All Those Flavors!

What, you don’t have all those devices and computers on which to test?

Not a problem, there are a bunch of “Cross Browser Testing” tools available. They are very handy and while most use emulators instead of the real devices, you will be able to see and correct most of the defects that occur on the actual devices.

Now you’re ready to test your website.

How Long Will It Take? Counting The Hours.

How much time will you need to complete your website testing project?

The math is easy.

Count or estimate the number of pages and forms on your website.

On average, it takes about five minutes to fully evaluate and test a single web page on a single device.

Now, multiply number of pages and forms by five minutes and then divide by 12 to get the number of hours it should take to test your website with EACH flavor.

Then, multiply those hours by the number of flavors you want to test.

Now, you have a good rough estimate of the amount of time you’re going to be spending at night or on the weekend testing your website.

A Small Note On Regression Testing And What It Means

Regression testing means “testing it again” after fixes have been completed from the bugs you found during your last round of testing.

Yes, you will find defects when you test – almost every time. If you don’t find any defects, you should be very suspicious about the quality of the testing.

After you find the defects, your developer or software engineers will read your defect (write it very carefully and thoroughly so they can quickly reproduce it and then fix it) and make changes to prevent that defect from happening.

This will need to be rested to confirm that it has been fixed. This is called validation testing – you are validating that the defect you found has been accurately fixed.

There is also the possibility (or even probability) that your developer or software engineers accidentally caused another defect somewhere else when they were fixing the defect you found. Make sense? They fixed something but that fix caused another defect.

You need to find these and chasing them down can be maddening sometimes. This is called regression testing – testing again to make sure nothing else was broken during the latest round of fixes.

And, theoretically, you can keep doing this until you have Zero Defects. But, you should consider that performing regression testing until you achieve Zero Defects will probably be very expensive. Think ahead and plan for at least one round of regression testing (they do tend to go faster than your first round of testing) and possibly two rounds depending on the number and severity of the defects you find in each round of testing.

That’s Too Long!

Yeah, I’m sorry.  I knew you’d probably be surprised when you actually did the detailed math for testing and regression testing.

Website testing is relatively simple but it’s not easy. There’s a LOT of ground to cover, a lot of repetition and it requires an intense attention to detail – especially when you’re looking at the same pages over and over, just on slightly different devices.

If you have a small(ish) website and/or you aren’t very busy, you can certainly do this yourself.

Be careful, though, and make sure you’re paying close attention as you do it – website errors can be sneaky and hard to notice. Maybe get a pot of coffee ready?

Rather than consume more caffeine, seriously consider outsourcing your website testing project to a website testing service that can run the necessary tests while you and your team focus on other priorities that build and grow your business.

The Ultimate Question – Can I Afford A Website Testing Service?

Building a website or a business is partly the process of making wise investments – particularly with your scarcest two resources – time and money.

Just within your website project, you have to decide several times whether you’re going to invest AT ALL or if you’re going to spend your scarce time and/or money.

If you don’t have a solid goal for your business or website project, your decision on whether to invest is going to be hard. After all, how can you decide how much to invest if you don’t know what you really want?

But, let’s say you do have a goal for your website. Let’s say it’s to increase your sales by $50k/month within six months. That’s a solid and worthy goal!

And, let’s say you spent around $10k with a website design agency to get your website built to achieve your goal.

You’re small and that was a big chunk of money to spend but you knew you couldn’t do all the research, design and coding yourself. Sure, you can roll a little HTML/CSS but a modern production/commerce ready website is beyond just HTML/CSS. You made the smart call and got expert help.

And, they’ve completed their work and your website is new and shiny. You can clearly see that your investment of $10k for a monthly return of $50k in the near future is going to be achieved. You’re excited!

Your website design agency says they tested it and it looks good to you. You’re ready to launch it.

But wait – how well did they test it?

You’re not sure so you decide to spend an evening testing it yourself.  Just to see.

And, yup, there it is – a small error on your order screen when someone clicks the dreaded “Back” button. Yeah, they’re going to do this no matter how many times you tell them not to.

Now, you’re a little concerned. If there’s that bug that they didn’t catch, might there be others?

You’re going to invest another $10k in advertising and promotion when you launch your website. That’s another $10k investment but it’s needed to get the word out so you can achieve your goal.

You can’t afford to have any website errors after you’ve spent $20k on building and promoting it.

Should you spend more time or money testing?

Let’s Do The Math

If you do it yourself, it will cost your direct time and it will also cost lost opportunities that you could have been pursuing while you spent time testing your website.

And, you’re a business owner or manager and you’re not an experienced website tester. You’re going to be only marginally efficient and partially productive simply because you don’t really know what you’re doing!

So, if your average annual earnings are near $75k and you’re only half as productive as a trained Test Engineer, your cost to test your website is nearly $75/hr and it’s going to take you twice as long to finish. And that doesn’t even count the other business opportunities (and problems, we have those, too) that you missed while you were trying to get your website tested.

Roughly speaking, it will take  about six days to thoroughly test your website for full functionality and across all the browsers and mobile devices that your users have.

The math says $75/hr x (6 days @ 8 hrs/day) = $3,600.

If you asked TESTCo to scope this project our proposal would be closer to three days (because we do this all the time and know what we’re doing) and the cost would be closer to $56/hr x (3 days @ 8 hrs/day) = $1,344 and in half the time! Much less than half of your direct cost and without the lost business opportunities!

Save time.

Save money.

Achieve your most important goals.

A Website Testing Service Is Sounding Pretty Good Right Now

I understand. We have a number of clients who came to us after they tried testing their site in-house.

We can help in a number of different ways:

  1. We can answer your questions. Just ask, and we’ll be happy to answer.  No charge!
  2. We can help with your research. Don’t want to figure out the right flavors? Let us tell you what we’d propose!
  3. We can test it for you. You’ll be surprised at how affordable we can be – we definitely cost less than what it would cost to do it yourself!

Here’s additional information about the TESTCo website testing service.

At Least Do Something!

Please, at least do a little testing on your website.  The rest of us who visit your site will be thankful.

If you can’t do it yourself, we can help you with our website testing services. It doesn’t hurt to talk. Click the green button in upper right of this page to request a call back, or reach out to me by phone right now. 888-254-9709

Mobile Testing Strategy

The Difference Between a Mobile Testing Strategy and a Mobile Testing Plan

In This Post

 

There is a big difference between a mobile testing strategy and a mobile testing plan. If you know the difference, your mobile software testing will be much easier and more valuable.

There are a number of ways of defining a strategy. One of the definitions that we’ve found useful is:

“Identify assets that have advantages that you can put into coordinated action to achieve your goal

Or, said another way, list and organize everything you think you’ll need to achieve your mobile testing goal and why you think you need it.

Your goal should be clear enough that you can quickly see what is, and is not, relevant to achieving your goal.

For example, if your mobile testing goal is to release your game every week with new features and fixes, your strategy might be different from a goal to release a zero defect trading app. Already, you can start to see that you might need different Assets for each of those goals.

Your Goal Will Dictate Strategy

One of the first challenges in building your mobile testing strategy will be to clarify and tighten your mobile testing goal. Your goal should clearly show what is and is not important to include in your mobile testing strategy.

The biggest and best tool you can use to uncover gaps or weaknesses in your mobile testing goal will be relentless Critical Thinking Questions.

“Why is this important and what, exactly does it mean?” is one of the most powerful questions you can ask about your mobile testing goal.

For example, which devices should you test against? The answer depends on which devices your current customers or prospects are most likely to be using. You know that mobile apps behave differently on different devices and operating systems, right? You won’t be able to afford to test against every device out there – you’re going to have to make some assumptions and then test their validity.

The more you can refine your mobile testing goal by clearly understanding what is directly relevant (need to have) and which things are “nice to have”, the more effective your mobile testing strategy will be.

Wait Just a Second – Why Bother with a Goal?

You don’t really have to have a goal to build a mobile testing strategy.

Your strategy could be “just test it”,or “get folks to bang on it a bunch”, or even “meh, just test it enough to make sure it doesn’t crash”.

Those are all valid mobile testing strategies and they have even been successful strategies – a couple times.

Here’s the problem that happens when you don’t have a goal.

You Don’t Know When You Are Done.

So, unless you want to test forever or don’t really care about your app or your customers, you’ll probably benefit from the 10-15 minutes it will take you to build a good goal for your mobile app.

A List of Things to Decide for Your Mobile Testing Strategy

Since you’ve made it this far, you probably realize that your questions are far more important than your answers!

Here is a list of questions that you can use to help you narrow your focus and build an effective mobile testing strategy:

  1. Which devices are important to my target audience?
  2. Do I have to have the real device or can I use an emulator?
  3. Can I use a tool for testing and do I have the experience to use it properly? Which tool will meet my needs and how can I tell that?
  4. What network connectivity is required for my app? Wifi? Cellular Data?
  5. Which parts should be automated testing and which should be manual testing? What’s the proper balance and how will I know?
  6. Will I need performance testing for my mobile app? Why would I need performance testing and which parts of my mobile app are subject to network congestion?
  7. What are the security requirements for my mobile app and how do they need to be tested? What is the probability and impact of a security breach of my mobile application?
  8. What sort of UX testing do I need and who is best qualified to give UX feedback on my mobile app?

Whew! Those are not easy questions!

And yet, you do need to know those answers if you want to avoid a “just get it tested” type of strategy.

So, is there an easy way to get started and build a great mobile testing strategy?

Additional Considerations when Selecting a Mobile Application Testing Company

When customers are selecting a mobile application testing company to work with, there are several key factors they should evaluate; failing to do due diligence on your mobile application testing company of your choice can lead to bad quality control and an overall negative experience with your app. A good mobile testing company will improve the functionality, usability and security of your app in general.

First, you should ensure your mobile testing provider has trained mobile testers or test engineers. This should be a given, but dealing with companies that don’t have trained mobile testers/engineers can be very expensive in the short and long-term health of your app. A company with competent mobile testers will have expertise in functional and usability testing. Additionally, companies with competent mobile testers will ensure that test optimization is done based on the current mobile device market.

Also, the company you work with should have the correct resources for your app’s testing. This can include a lab for device, emulator and simulator based testing. It’s important to talk with your provider about the specific tests you’re looking for and ask about any other testing they provide and how that can benefit your application. You should mention the platforms and operating systems that your app primarily runs on to ensure all testing is done across all verticals. The most important resource that a provider should have is test engineers, QA managers and other staff. For many businesses, it doesn’t make financial sense to hire more team members to their QA team so working with a provider that has all of the expertise you need is vital. With an expert QA team at your disposal, you can get daily status reports on your mobile testing and solve any issues that arise in the meantime.

Lastly, it’s key to work with a provider that understands your business goals and tailors their service to fit your needs. This seems intuitive, but when you get on a phone call with a provider, they should take some time to figure out your business model, specific application needs, etc. This will allow your provider to form the right QA coverage for your product and you can have a rough outline of how their services can fit your needs

A Simple Strategy is Simple!

One of the most common mistakes about strategies is that they are complex. Sure, your strategy can be complex but it doesn’t have to be complex. It depends mostly on the complexity and difficulty of your goal.

We prefer Simple Strategies and we can help you have one too.

For example, if your goal is to build a full-featured trading app for mobile devices, your strategy might be quite complex. But, if your goal is to launch an app that trades only 1 stock, your strategy might be simpler.

Our rule of thumb is that a strategy can be easily explained with three sentences or less. Sort of like this:

  1. we’re going to achieve THIS GOAL
  2. with these CONSTRAINTS
  3. by doing A and B at the same time and then C next and D last.

It should be clear and understandable to everyone involved in your project that doing A and B at the same time, followed by C then D, will achieve the GOAL within the CONSTRAINTS.

If it is not clear and understandable, then dig a little deeper, find the unknown or un-agreed upon aspect, and build a tighter, clearer strategy for your mobile testing project.

If you skimp on your strategy, you can expect to have problems with your plan.

If you invest wisely, and build a powerful but simple strategy, your plan will be obvious and tracking your mobile testing project will be very easy.

And, one more note about building a simple strategy – expect to rebuild it at least once.

Here’s why – the most unknown and uncontrollable part of your strategy will be the Environment. The Environment is everything around you that you can’t control. These can be as simple as a misunderstood requirement or an emergency family leave for a critical team member. They can also be as complex as a major business setback or the cancellation of a critical software license. These are all aspects of the “Environment” you’re working in and can have a big impact on your strategy. When the Environment changes, re-evaluate your strategy and rebuild it if the changes impact your mobile testing strategy .

Start with a Free Scoping Session with Me

I know, that sounds generous and it is.

And, we can do that for and with you in one of our standard 60-90 minute Scoping Sessions.

Most of our clients and prospects don’t have a quality goal prior to meeting with us. Only one or two have ever had a quality strategy when they first came to us.

So, we’ve become very adept at helping our clients and prospects define their quality goal and build an effective testing strategy.

We do this by gently asking you a lot of questions. Sure, we want to know the details about your mobile app and how you want it tested. We can and will do that for you.

And, we want to make sure we provide you with everything you need to achieve your goal. So, the first thing we do for you is clearly define your goal and then propose a couple of different strategies for you to consider. We’ll always recommend at least one of the strategies but we want you to know that there are different ways to achieve your goals and that you have the last word on how we work for you to achieve your goal.

If you’re curious about how a mobile testing strategy can improve your mobile app testing, achieve your goals and build your business stronger, please reach out and let’s talk about how we might help you. Send the form on this page to schedule a call, or give me a shout now at 888.254.9709 .

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

Quality Assurance Outsourcing

Quality Assurance Outsourcing Options

What is the “best” quality assurance outsourcing option? There are certainly a wide variety of lists that you can choose from.

But, only you can determine the “best” based on what YOU need.

Unfortunately, you really won’t know that until AFTER you’ve experienced the results.

But, there are some things you can consider (and questions you can ask) that will stack the odds of success in your favor.

Great Questions to Ask About Quality Assurance Outsourcing

  1. Expertise – Have the test engineers that will be working on your project worked on similar projects recently? What did they learn on those projects that will help your project be a success?
  2. Availability – Are the engineers with that expertise available when YOU need them? If there is a delay starting, will they still be available? How would that work?
  3. Price/Cost – Calculate the cost rather than decide based on the price.  Huh?  Yeah, who cares what the hourly rate is when you don’t know how much time it will take. Get an estimate and then decide based on the hourly rate multiplied by the number of hours estimated. Here’s a hint – talented quality assurance outsourcing engineers can build and execute test plans almost twice as fast as general testers – and you’ll get better result in this project and your next one!  Do the math!
  4. References – Do they have references for previous customers who wanted similar quality assurance outsourcing?  If so, then ask to talk with one or two. This can make a HUGE difference – and here’s why. You really want to hear two things from a reference. How well did they do meeting the goals? What did that person (the reference) do to make the overall project easier and better with the vendor they selected?

How TESTCo Answers Those Questions

At TESTCo, we have all those bases covered.

quality assurance outsourcing questions to askExpertise – we only use experienced software test engineers – no testers! We’ve been delivering software testing and quality assurance outsourcing since 2002 and we only hire experienced test engineers – and they DO make a difference.

Availability – TESTCo is specifically designed to provide on-demand software testing precisely when you need it. Sure, our rates are a little higher but we always have the talent when you need it.

Price/Cost – TESTCo only hires experienced software testing engineers and quality assurance managers. As a result, our prices are a bit higher than most quality assurance outsourcing providers. But, when you combine the test production capability of an experienced quality assurance engineer with the strategy and planning of an experienced quality assurance manager, your project will be completed quicker and with much better results.  The price is higher but the cost is lower.

References – every TESTCo customer is happy to share their experiences working with us. You’ll hear where we succeeded and where we didn’t. Nobody is perfect every time. But, what you will also hear – guaranteed – is how our customers appreciate what we did and how we worked with them. Listen closely to hear their tips and tricks for getting the most out of their TESTCo quality assurance engineers and managers.

And then what?

We’d like to be your next quality assurance outsourcing partner. Contact us to find out how we can make your next quality assurance project a success without hassles.

Automated Regression Testing for Software | TESTCo

Automated Regression Testing Dilemma

Nobody likes running long software regression testing cycles. It’s long, hard and boring.

And yet, nobody likes to release bugs either. NPS (Net Promoter Score) drop like a rock and the support phones light up like little annoying Christmas ornaments.

So, just grin and bear it or take the plunge into software test automation?

It depends on where you stand on these two dilemmas.

1. Business Speed Dilemma

This dilemma is about your cost and speed of producing software versus capturing more customers and larger market share before your competitors.

  • Adding customers, solving real problems and growing your market share requires more features in your software.
  • More software features require more software testing.
  • More software testing takes more time, people and delays releasing your new features.

So, faster software production equals more customers as long as you meet their minimum quality requirements. Otherwise, they dump your software or mobile app like yesterday’s leftover tacos.

2. People Versus Machines Dilemma

This dilemma considers that people are more adaptable but more expensive than machines that are more consistent but less expensive.

  • People are better at finding defects.
  • People are slower and more expensive than machines but require less “programming”.
  • Defects found late in the process are very expensive to fix.
  • Machines are better are consistently repeating sets of activities.
  • Machines are slower and less expensive than people but require more “programming”.
  • Defects found early in the process are cheaper to fix.

So, how to resolve your dilemma? My friend and business mentor, Keith Cunningham says

One choice is slavery. Two choices is a dilemma. Three choices is freedom.

Hybrid Software Regression Testing That Turns a Dilemma into Freedom

Consider a hybrid approach to software regression testing.

Use people for manual regression for all features in the current and previous version.

New(ish) features are where most of the defects lie in hiding. This leverages the human advantage of finding defects in new features.
This also minimizes the amount of time & money spent on people in the regression testing cycles. You will have the benefit of faster and cheaper software regression testing cycles.

Use Test Automation for regression testing all features released prior to the previous version.

Older features are where most software developers do damage. This leverages the machine advantage of consistently repeating activities. This also minimizes the amount of time between discovering a defect and fixing the defect – which dramatically reduces the cost of fixing the defect.

You and your developers will have the benefit of real time testing so that regression defects (where new features break older existing features) are much cheaper to fix.

The Drawbacks to Hybrid Software Regression Testing

  1. You may need to add Test Engineers to your software testing team. Successful test automation will require written test cases that can be easily automated. Test Engineers know how to write these types of test cases.
  2.  You will have to decide on which approach to use for Test Automation – Record/Play, Scripted or built-in APIs. You’ll need an experienced Test Automation Engineer to help you determine the best path for you and your business.

At TESTCo, we can help with both – call and let’s talk about how to implement or improve your automated regression testing.

agile software testing reportDownload our report that looks at the challenges and pitfalls of creating automated regression tests in an Agile environment.

QA Services

QA Services for the A-Team. A Founder’s Dream Comes True.

 

In This Post

As a founder myself I know first-hand how agonizingly difficult it is to build and retain an A-team of talent to run and grow my business – to make my dream a reality. If you’ve started a company that develops mobile apps, software, or websites you’re feeling the same pain every day. The pain is especially acute in the area of QA services for small companies.

It’s not just the shortage of talent that’s the problem. It’s the shortage of smart talent. You know, the proactive problem solvers and opportunity achievers. The type of people that bring a lot to the table. In short, the A-team.

Putting All-Stars At Every Position

In 80% of the conversations I have with founders and CEOs they point with pride at the skills and innovativeness of their engineers. But when the conversation turns to their QA services team, whether internal or outsourced, the mood changes. By and large most founders believe they have competent people in the QA slots, but they don’t have enough A-players in those roles to take the QA function to the next level.

The really savvy founders I know understand that the dev cycle is streamlined in direct relation to just how sharp their QA team is and how well they work with Engineering. Those same founders know that the quality of their product becomes their brand and defines their dream. On the other hand,  bad reviews, poor customer loyalty, extensive support costs threaten to destroy their dream. No wonder a lack of QA talent causes more than a little anxiety for these folks.

Your Dream is My Dream

The dream I’ve built–my company–actually helps founders build and maintain their dreams by providing the smartest, most goal-driven QA service teams on the planet. Give me a shot at a project and if we don’t perform according to plan, you pay nothing. You understand correctly. That’s an old-fashioned money-back guarantee.

I’m not desperate for your business. I’m confident. Confident in the ability of my teams to delight.

You don’t hear the word “delight” associated with software QA much, do you? Well, that word and many like it surface in our customer reviews. Here are a few reviews from founders of small companies like you.



Attitude, Consistency, Intelligence - The TESTCo Difference

What makes TESTCo different? After all, the world is filled with software testers and outsourced QA services companies. Some of which even proclaim to serve small companies.

First, I like to describe us as a boutique software QA company. We’re not a QA factory. I have no interest in running that kind of business. We provide highly personalized services, crystal-clear communication, and top-drawer project leadership. (At affordable rates I should add). TESTCo's nimbleness and size dovetail well with small and mid-sized companies.

Second, I employ only A-team caliber people. My QA Managers (provided with every project at no additional cost) are brilliant at setting the right testing strategies to deliver value to you every day. They are true leaders.  Our Test Engineers are bonafide engineers who love to test. They don’t sit back and wait to be told what to do. No way. They work closely with the QA Manager to develop and implement the perfect test plan to achieve the project goal.

Third, we are awesome communicators. You receive status reports twice a day. My QA Managers participate in (and often lead) project postmortems. The feedback they provide to Engineering actually helps shorten the Dev cycle. The QA Managers are fluent in English. Plus we’re available to chat, email or talk when you are. TESTCo QA Managers are located in the Central time zone.

Fourth, we deliver expected results because the results are expected. That’s a clever way of saying we really excel at understanding the business goals (not just the testing goals) and creating test plans that support the business goals within the known restraints. Your team knows what to expect by when. And we deliver.

When was the last time you talked to a software tester who wanted to know about the business goals associated with the project? Never, right?

On-Demand, or On-Going QA Services for Small Companies on a Budget

Here's the other good thing about TESTCo QA services. On very little notice (often as little as one day's notice), we can parachute in to rescue a project. Even for small projects. The other way we provide value is to be an on-going extension of the QA team, or be the QA team for your organization. I have many clients who have relied on TESTCo for all of their testing requirements for years. They receive value, reliability, and intelligence all for 30% - 50% less than an internal team.

A-Players for QA. No Risk. Make the Call.

And that’s the primary difference between B- and C-level QA people and the A-team at TESTCo. We care a lot about your dream.

Earlier in the post I made an offer. I’ll make it again. Try us for a project. If we fail to perform according to the goals of the project, the work is free.

Go ahead, schedule a call with me to see if I stand behind my promises. I look forward to speaking with you – founder to founder. Just click the green button on this page to schedule a conversation. Talk to you soon.

Mobile App Performance Testing

Do I Need Mobile App Performance Testing?

In This Post

Mobile app performance testing is the process of testing and reporting the time it takes your application to process a request or take an action – especially when large groups of users perform the same or similar action simultaneously.

Performance testing answers the question, “When and where does the performance and speed of my application degrade the user’s experience?” It also answers the question, “How many users can I have before my application crashes?”

Performing “At Scale”

“At Scale” is the current lingo for “many, many, many users and transactions”. Performing “At Scale” is a big concern when building software and especially mobile apps. Mobile app performance testing helps you understand the scale your mobile app can withstand before degrading or crashing. Most software development teams invest significant time and money engineering their mobile apps to perform at scale from the very beginning. This is generally a wise investment but only if you are willing to apply mobile app performance testing throughout the software development process. Otherwise, the software development team will not have the feedback they need during the software development process to measure and correct the scaling assumptions they had to make while building your software.

Performing “Good Enough”

If “At Scale” is not a critical business and technology driver for your mobile app, you still might need to be concerned about performance and mobile app performance testing.

Here’s why:

  • All mobile applications have performance limits
  • When mobile application performance degrades and slows down, users abandon mobile apps.

You’ve invested serious time and money building your mobile application. Don’t you want to know how many people you can satisfy with your mobile application before they become dissatisfied?

There’s a big difference between engineering and performance “At Scale” and “Good Enough”.

Engineering and mobile app performance testing “At Scale” is an ongoing endeavor to insure that your mobile application will always be available to as many users as possible. This is an expensive process but worth it when your goal is performing “At Scale”.

Mobile app performance testing  for “Good Enough” is an end-of-cycle process that determines “How many users can I handle before I need to turn on more servers?” This is a much simpler and less expensive process that gives you a finite number and an alert for when you need to add more servers in your AWS or Rackspace cloud.

If you aren’t required to engineer, build and deliver “At Scale”, then “Good Enough” may work best for you. A short engagement to determine “Your Maximum Number” will help you recognize and avoid a disaster where your mobile application performance degrades and you lose customers. You’ll use “Your Maximum Number” to alert you to add more server capacity before your known performance threshold and prior to any perceived slow downs by your customers.

What Does Mobile App Performance Testing Look Like?

Mobile app performance testing is a simple process but it’s not easy.  Here’s one way of looking at the process:

  1. Build your mobile app features
  2. Add “Instruments” at locations within your mobile app that will measure throughput
  3. Build or find a “Pump” to push specific user scenarios through your mobile app
  4. “Load” the “Pump” with one or more test cases or user scenarios
  5. Tell the “Pump” the volume and timing of test cases to push through your mobile app
  6. Record the readings from the “Instruments” as the “Pump” pushes a measured volume of test cases through your mobile app.
  7. Analyze the readings from the “Instruments” to determine if
    • throughput performance was acceptable – add more volume and retest
    • throughput performance was not acceptable – determine bottlenecks to discuss with your mobile app developers to fix for greater throughput.

Simple But Not Easy

Yeah, it’s simple but it’s not easy. Generally speaking, finding the “Pump”, placing the “Instruments” and building the “Load” of test cases is straightforward. You’ll wind up with a big pile of data from the instruments and you’ll have some early anecdotal evidence of how your mobile application performs under a load.

But, it’s seldom actually that simple because mobile applications almost never just fail due to a high load. It’s the nuances of what happens under one set of load circumstances that look just fine and another set of load circumstances that crashes your mobile app. This is when a trained and experienced Performance Testing Engineer can really help you and your software development team quickly find, test and fix the performance bottlenecks in your mobile application.

Mobile app performance testing can be a critical component of testing and launching your mobile app. Not every mobile app needs performance testing, but when you expect a large volume of users or heavy usage, mobile app performance testing by experts can save you from a major crash and downtime where you can lose customers and prospects.

Look Before You Leap

You want good testing results, of course. Or put another way, you want good testing value. That’s why it’s crucial to define the mobile testing strategy first, which includes performance testing, before thinking about a test plan.

Want to discuss your situation? Call me 888-254-9709. Or, click the blue and green button on this page to request a call back.

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.

Checklist for Finding the Best Software Testing Company

Checklist for Finding the Best Software Testing Company

After your web search for a software testing company reveals a long list of company names, how do you select the one that is right for your business? Here’s some guidelines and a check list.

How to Initially Screen Software Testing Companies

You may or may not know exactly what you need.  If you do, then please skip to How to Select a Software Testing Company. If you’re not sure what you need, then please read on.

First, do your choices have references and testimonials from clients where they solved a similar problem? Take note of where they solved a business problem, not just a software testing problem.

Next, do they share their knowledge? Knowledge sharing is an important indicator of where the software testing company believes their value lies. If they share software testing knowledge and know-how with you then they are likely a company that values their people and commitments more than their intellectual property. If they don’t share their knowledge of software testing with you, then they probably value their intellectual property more than their people and commitments.

Lastly, is software testing their primary focus? Many companies provide a wide variety of technical services – everything from ITIL to software development to business processing outsourcing. Unfortunately, software testing is seen as a commodity by many people.  We have found that many outsourced technical companies that offer software testing along with a variety of other services tend to see software testing as a commodity as well.  This leads to their top talent and most attention going to somewhere other than software testing. That may be fine to build a business but it probably won’t be your best choice to solve your current software testing and business problem.

Ready to put TESTCo on the list of software testing companies to consider? Just send the form from this page to schedule a call.

How to Select a Software Testing Company

By now you should have a handful of good choices that you are confident in. According to your research each company on your short list

  • Has solved similar problems successfully in the past,
  • Has shared their knowledge about software testing with you,
  • Has focused on software testing as a priority

Now, how to select the winner.

A Check List for Selecting the Best Software Testing Company

  1. Do they perform an effective needs analysis? Do they ask you and then clearly understand why you need help, your business goals related to this problem and the constraints you have? This needs analysis should take no more than about 30 minutes over the phone. If you aren’t convinced they clearly understand your problem then you should move on with another choice.
  2. Do they offer smart choices and benefits? Since they understand your problem, goals and constraints, do they offer and explain the selection of choices they can offer and how each can solve your problem? If not, then you should move on.
  3. Do they answer all your questions? Are the answers clear and relevant to your situation? Do they seek additional questions from you or avoid them trying to close the deal? If you aren’t convinced these are the most curious creatures on the planet (all great software Test Engineers are hugely curious!) then you should move on.
  4. Do they make it easy to get started? Software Testing is one of the few technical activities that can begin almost immediately. But, without a good understanding of your business and technical problems, that testing may not produce the outcome you need. Gaining this understanding has to be done quickly and effectively so that time and budget constraints are met. They can’t go off to “train on your app” for a couple days. Are you confident that they know how to get your team producing real value as quickly as possible without taking a bunch of your time? If not, then you should move on.
  5. Do they clearly distinguish the value? Business is a game of value creation and transfer. Your software produces real problem-solving value for your customers. That’s why they keep buying it. Software testing is not just maid service for the coders! Software testing and quality assurance activities confirm and deliver the real value of your software application. If your software testing company prospect can’t clearly explain how this happens so that you see real value, then you should probably move on.

It is a simple checklist but it’s a tough one to pass.  If you make it through every step with a software testing company your odds are high that you’ve of identified the best software testing company for your business.

Ready to put TESTCo on the list of software testing companies to consider? Just send the form from this page to schedule a call.