Right Source Your Testing the Right way
“Right Source your testing”, you may have been advised. At eTestware we would agree. We would then go on to advise how you can do that in the right way. So here goes…
Why right source?
- Lower your operational costs
- Focus on your core business
- Leverage external knowledge bases
- Free up internal resource
- Mitigate risk
Right source with eTestware and we will work hard to understand you and your business. By working together in harmony, we’ll deliver:
Results | Insights | Gains | Help | Technical support.
Right Sourcing the Right Way
So, the leadership team has decided to outsource a portion of the QA testing to improve application testing coverage. How do you decide exactly what testing to right source? As a leadership team member, do you know precisely what QA testing is currently testing? If not, it’s time to gather a small team made up of developers, QA testers, and the Development and/or QA manager to find out.
You’ll need to understand what testing is currently executed and the scope, or depth of the testing effort. You can then determine the value you’ll get from the right sourced testing team.
Gather the team and determine what testing types are currently executed. Also identify what testing is missing, or fails to get executed frequently, if at all. By assigning this testing to your right sourced team, you will significantly increase your testing coverage from the off.
If you want to increase testing coverage even more definitively, start by:
- Reviewing existing test case (manual and automated) coverage including test type and depth
- Review unit testing coverage by development
- Determine what testing benefits the customer or end user the most and expand from there
- Review the application areas with the most reported defects. Determine if a certain type of testing covers that area.
The success of the application depends on keeping customers using it. Start by determining what testing provides the most positive outcome for your customer and then add on to it as the schedule allows. You may start by improving the customer experience and then move to testing that improves the organisation’s bottom line. If you expand the breadth of the mobile devices you test, can you sell more product? Or likewise, if the mobile application performance improves noticeably, and includes more device types, can you both improve customer retention and the business income?
Another consideration is what testing allows the outsourced testing team to be the most productive? What type of testing makes sense to start with from a training perspective? Once the team gains experience in the application then the testing type and schedule can expand.
Improving testing coverage by executing a larger variety of testing types improves application quality
It does so simply by having more testing with different patterns. Security, usability, accessibility, performance and varied platforms are all options that benefit the end user experience.
You may consider measuring defect count data and customer service escalations. This lets you see where you are currently having issues so you can measure the improvement with each release. Better testing coverage means fewer customer issues and complaint escalations.
In the end, the more testing executed, the better the application functions and performs and the more you expand your customer base.