testco-software regression testing | agile software testing | agile testing

Agile Testing Doesn’t Have To Be Complicated

Agile Development methodologies have become widely used and accepted as industry standards across the world. The flexibility to grow and adapt software development organizations is one of the most attractive features of Agile development. The price paid for this flexibility is buggy software. While most Agile development teams are able to produce features at a higher rate than traditional development teams, they also deliver more defects than a traditional development team. Software quality for Agile testing is needed.

Agile Software Testing Services

Agile testing involves testing from the customer perspective as early as possible, testing early and often as code becomes available and stable enough from module/unit level testing. Since working increments of the software are released often in agile software development, there is also a need to test often. Taking an agile testing for software quality control approach is key.

Why Have an Agile Testing Methodology?

  • Early in the lifecycle teams don’t realize the severity of existing defects, and do not put a large effort into finding them.
  • When Critical Mass is reached, customers begin using the product in unexpected ways.
  • As product development becomes steady, the effort necessary to find the defects is not constant throughout the release cycle, and a steady team of Test Engineers is too much for some stages and not enough for other stages.
  • When the product matures, automation test scripts that have been relied on in the past no longer provide sufficient coverage, and cannot find all of the defects.

On Demand Agile testing solves these problems, it keeps product quality in step with your engineering team. TESTCo’s QA testing will make this happen.

Share This:
Software Test Outsourcing

The Costly Learning Curve of Software Test Outsourcing

There are three things you can do to avoid the costly learning curve of software test outsourcing initiatives. Why does a learning curve exist? Software is getting more complex every day.  This makes software testing even harder. The learning curve for any software testing team can be steep and it is even steeper and more costly for software test outsourcing teams.

When the learning curve to begin testing software is steep due to complexity, everybody on the team feels the cost – especially the project manager! Software engineers experience interruptions which degrades their concentration, business analysts get frustrated covering old ground and project managers churn through project timelines and budgets trying to get everything to match up.

You can’t make software less complex and you can’t roll back time (unless you have a time machine that you’re keeping secret from the rest of us!). If you can’t compress the size of the problem or flatten the learning curve then all you’re left with is tools.

Three Key Tools to Shorten the Learning Curve of Software Test Outsourcing

Here are the things we use regularly at TESTCo that have proven effective in reducing the learning curve of software test outsourcing.

  1.  Use a Functional Map – create an index of user stories/scenarios as compared to primary function points in the software where the intersection of a user story and a function point denotes a test case or collection of test cases. This index provide multiple benefits starting from Day 1. Contact Us to see how a Functional Map could help your software testing team.
  2. Build a Value Proposition – when your entire software test outsourcing team understands and is aligned behind BOTH your technical and business goals, your QA team becomes a key strategic lever to move your software project directly towards your business and technical goals every day. Reach Out to Us to learn more about our Value Proposition Process.
  3. Add a QA Manager for your software test outsourcing team. At TESTCo, we believe that managers manage and engineers engineer. Engineers almost always perform at a higher level when they are led and managed by an experienced technical manager. We believe so strongly in the value and benefit of a QA Manager that we provide one, at no additional cost, for every TESTCo client.

If the learning curve of software test outsourcing is holding you back, we’d enjoy the opportunity to share how we’re different and more successful for our clients.

Automatic Software Testing | Automated Software Testing | Software Test Automation

Calculating the Maintenance Costs of Automatic Software Testing Suites

Is maintaining automatic software testing* an investment, expense, or just a problem? You’ve paid a lot of money to automate software testing and all was working just fine,  but as time goes on and new features are added to your application, the automatic software testing suite is breaking more often and you’re getting frustrated.

Software Test Automation Tools are Changing Rapidly – Double Check

Before you jump off into a test automation rebuild project, it’s worthwhile to do a little bit of due diligence to make sure your platform and software test automation tool will continue to serve you into the future.

  • Your choices for software to automate your testing activities is growing and changing rapidly.  There are literally new software test automation tools announced every month. They tend to be born or created from a need to solve a unique test automation problem. Make sure your software test automation tool is synchronized with your technical needs and supports your technology platform.
  • Software test automation tools change versions and compatibility frequently. As new software technologies are built and release, software test automation tools change to accommodate those new technologies.  In some cases, these upgrades can cause havoc with the scripts you’ve already built for the previous version. How stable and “future proof” is your selected tool?
  • Software test automation tools also fail frequently as businesses. How can you tell if the company you purchase your tool from will be in business next year? There are many open source choices for software test automation but those tools have a risk as well. Will the open source community continue to be interested enough in that test automation tool to keep it working with the current changes in technology?

Maintaining Software Test Automation is Not Easy

  • You probably paid a lot of money to get your software test automation working properly but the return on your initial investment is fading as time goes by – surely that’s not how it is supposed to go.
  • Your software test automation suite worked just fine when it was originally built but today, it’s throwing more and more false errors – and that doesn’t help you achieve your business and technical goals.
  •  Your software development team is too busy writing new features to keep the test automation updated and, they aren’t really interested in working with those tools.
  • Your internal QA Team has trouble finding, selecting and keeping someone talented enough to maintain your software test automation suite – the learning curve is steep and maintaining code is much more challenging than just writing new code.
  • You’ve looked for outsourced help (again) but your software test automation maintenance project just isn’t quite big enough to interest the big offshore technology firms.

Push the Reset Button for Automatic Software Testing

  1. Build a business case – nothing complex – back of the napkin calculations should be sufficient. Gain a deeper understanding of your specific technology and business goals and how they relate to continuing to invest in software test automation. Once you are clear on your specific goals and expected returns, your choices will become much more distinct and easy to evaluate.
  2. Treat test automation false alerts as defects – just like you do with your application software. Use a defect tracker just like you do with your application software. Then, simply cross check application defects reported by your software test automation with the software test automation defects and automatically rule them as false and then use manual testing to verify. This won’t eliminate the time waiting problem but it will reduce it and stop the confidence erosion.
  3. Move your test automation engineer into the software development team. When your test automation work is aligned with the development project timeline and not the QA team timeline, your software test automation will be ready when the software is ready, not a few weeks later.
  4. Start building a software Test Automation Team. Hire a Jr Test Automation engineer to learn from your current Test Automation engineer. Not only is this a great strategy for succession, your software test automation suite will suffer fewer issues and grow quicker to match your software application.
  5. Find an outsourcing partner (not a”vendor”) to work with you over time to specifically meet your business and technical goals. Most outsourcing companies try to be as large and broad as possible to meet every need possible. A few outsourcing companies specialize in automatic software testing and test automation. We specialize so all of our talent will be perfectly suited to solving your software test automation maintenance problem.
^Most readers will dislike my use of the term, “automatic software testing suites”, in this post. The term is not accurate. “Automated software testing suites” is the accepted phrase used in the software testing world. Accepted or not, our research indicates that “automatic software testing” is used by a large number of folks as they search for information on the topic. Therefore, I’ve devoted this post to the folks who prefer “automatic” over “automated”. We do a great job for both. -JCH