Read Blockchain testing

This week’s article is based upon a piece first published on August 14th, 2017, which posed a double-header of a question: “What testing should you outsource and how to break it down”?
There are over 25 million results to this query on Google and if you would like to see our original response, simply click here. Otherwise, kindly allow us to summarise it for you now…

That 2017 article started off with a hypothetical scenario, which it then questioned and rather handily answered, in one fell swoop:

The leadership team wants an improvement in their QA testing efforts and has therefore opted to outsource.

How do you decide what testing to outsource?
Do you know what QA testing is currently taking place?

Gather your team to establish the testing types currently being executed and the scope of those efforts. This will allow you to see what testing is missing and therefore how to get the best value out of the outsourced testing team.

The article continued by revealing the 3 most important types of testing:

1. Smoke testing
2. Functional regression testing
3. New feature testing

(For a full breakdown of each, please refer to the glossary)

Type 1 and 2 above are either scheduled before the release as part of a regression testing cycle, or they occur continuously. type 3 takes place during development cycles and is generally the focus of internal QA teams.

Our author then went on to describe how QA testing teams rarely have time to “execute full regression testing test suites”, going further to point out that a vast amount of other testing types are also only “touched upon within the general regression suite”, such as:

Performance testing
Load testing
Integration testing
Usability testing
Accessibility testing
Security testing

(For breakdowns refer to the glossary below)

With these tests not being covered in the hypothetical scenario used in our article, it was then revealed that the best course of action would be to assign load, performance and security testing to an outsourced testing team.

To take an even more effective stance, a number of tips to follow at the start were then provided:

- Review existing manual and automated test case coverage (including test type and depth)
- Review unit testing coverage by development
- Determine the types of testing that will most benefit the customer or end user
- Review the application areas with the most reported defects and see if certain types of testing will cover them

Wise words, we hope you will agree…!

Continuing on in their guise as the Mr Miyagi of the testing world, our author then went on to unveil even more handy hints…

- Consider what testing will allow for the outsourced testing team to be the most productive
- What type of testing makes the most sense to start with, from a training perspective?
- As the team gains experience in the application, expand the testing type and schedule
- Improve testing coverage by executing a larger variety of testing types
- Consider measuring defect count data and customer service escalations to see where you are having issues
- Measure improvement with each release

In a nutshell, the more testing that is executed, the better the application functions and performs.

eTestware is part of theICEway ecosystem, which has provided the cruise industry with a complete digital solution for more than 20 years. We work alongside your IT team to deliver:

Technology Projects | Cloud Strategy | Application Managed Service

Glossary

Smoke testing – Preliminary testing designed to reveal simple failures

Functional regression testing – Performed to ensure that application functionality is working as expected

New feature testing – The process of making changes in a software system to add new features or to modify existing features

Performance testing – Performed to determine system responsiveness and stability under a particular workload

Load testing – A type of non-functional testing performed under both normal and peak conditions to understand application behaviour under a specific load

Integration testing – Individual units are combined and tested as a group in order to expose faults in the interaction between integrated units

Usability testing – Performed with real users who must complete tasks while being observed in order to assess how easy something is to use

Accessibility testing – Performed to ensure that the application being tested is usable by people with disabilities

Security testing – Performed to discover system vulnerabilities

Top Tips

Please see above for quite a few ‘top tips’! Or if that has simply whetted your appetite, why not contact our testing experts for more information on how eTestware and theICEway can help you?