Read Blockchain testing

Continuing with our revisit of past articles, next up is a piece first published all the way back in August 2018 on QA Testing. More specifically, our experts looked at how the idea of outsourced QA Testing should be presented to an organisation with an internal testing team, and an organisation without one, as this presentation is a crucial factor in maximising your testing output. The full article can be read here, otherwise read on for a summarised version…

Before we get started, it might perhaps be worthwhile asking a simple question: What is QA testing?Simply put, Quality Assurance testing is a process that ensures products or services are of the highest possible quality for customers (‘QA’ describes the techniques used to prevent issues with them).

Now that has been cleared up, the original article began by making a very important point; namely, that in any test scenario, all changes must be communicated in a very clear fashion, otherwise the success of the project as a whole can be placed into jeopardy.

Clearly outsourcing is a major change and the article focussed in on that in particular, applying two different example scenarios in order to make everything as clear as possible…

Outsourcing QA Testing when an internal QA team is in placeStep 1.

- Gather factual data around code coverage
- Document the types of testing the internal team carries out, along with all internal tasks that will become the outsourced team’s responsibility

A basic example was then provided for Step 1:

Internal QA Team:

New feature functional testing
New feature integration testing
Regression testing

eTestware QA Team:

Daily smoke testing
Security testing (thus assigned as it is our speciality)
Performance & Load testing (this requires development experience and / or specialised tools)
Regression testing

Both teams:

Test parties / Bug hunts (If scheduled, both teams should be involved)

The article then featured a shortlist of FAQs any outsourced team should be ready to answer, including:

Q. Can you train us to perform load, performance and security testing instead of performing it yourself?

A. Providing specialist training is an expensive endeavour, so it is much more cost effective to implement outsourced, specialist resources.

Step 2.

- Appoint someone from your organisation to be the single point of contact for assistance, questions and support

This second step is crucial, because without a sole point of contact, the outsourced team will take longer to integrate and become effective.

Outsourcing QA Testing when there is no internal QA team in placeStep 1.

- Gather factual data around code coverage
- Document the types of testing to be carried out and map out all tasks that will become the outsourced team’s responsibility
The article went on to describe how even without internal resources, the outsourced team will still need training from those inside the organisation, along with the second step…

Step 2.

- Appoint a sole contact point from within

Important points to note in this second scenario were then shared:

If there are no existing test cases, training and accurate documentation become even more critical; the outsourced team will still require detailed instructions on network systems, network rules & more; the outsourced team should be invited to all relevant meetings and discussions; the method of communication is even more important, make sure that an established communication protocol is adopted by all.

The bottom line is this: in order to maximise your test spend, you must give your QA Testing team all the tools they will need to succeed…

eTestware is part of theICEway ecosystem of companies

GlossaryFunctional testing – A QA process that bases test cases on the specs of the software component being tested

Integration testing – A phase in software testing which sees individual software modules combined and then tested as a group

Regression testing – A process in which functional and non-functional tests are re-run to ensure that the test subject performs once again after a change has occurred

Daily smoke testing – A non-exhaustive software analysis that tests the most crucial functions without going into the finer details

Security testing – A process designed to identify flaws in the security mechanisms of an information system

Performance & Load testing – Performance testing is conducted on systems to assess factors including speed and reliability. Load testing assesses how a system behaves when being accessed by multiple users at the same time

Top TipIf QA testing is on your horizon, our experts will be happy to guide you through no matter what the nature of your set up might be. Contact us today for more information…