Read Blockchain testing

It’s a difficult time for the world and last week we decided to lighten the mood with a piece about our extremely loveable mascot, Bacon the dog. There will be more on her in the future but for now, embracing ‘the show must go on’ as a theme, we continue with our series of revisited articles. Next up is one which was published back in September 2017, revealing the best practices to evaluate before making the decision to outsource testing services. You can read the original piece here or carry on down the page for our updated summary…

- 1. “SLA - The who, what, where, when, how and how much.

“The SLA… defines precisely or “legally” who does what, where, when, how and how much.”
And so began that article from two-and-a-half years ago, breaking down perhaps the most important part of any collaboration or project. Any SLA must be agreed to by both / all parties, and forms the very basis upon which all work is carried out – which is exactly why it needs to be the top priority for any company or organisation to contemplate when they are on the verge of outsourcing.

The article went on to list out the other key considerations:

- 2. You must evaluate QA skill levels to identify the right resource(s)
- 3. You must evaluate each release before moving on to the next
- 4. Communication is vital & change notifications are key
- 5. Your IP must be protected
- 6. Security must be taken seriously, your hardware must be protected
- 7. Flexibility is key
- 8. You must consider the location of your (potential) testing team
- 9. You must determine which devices need to be tested and with what settings / configuration
- 10. Any testing team must understand all of the requirements, so these need to be made clear

Not unexpectedly, the eTestware team went into a lot of detail for each point listed here, but nowadays people want even smaller sized bites and all of us on theICEway understand that; therefore, we will now break down those points ‘2020-style’:

1. You must have a Service Level Agreement in place which is clear, concise and understood by all

2. QA tester and development skill levels vary and it’s important to understand which level you require

3. To keep the working relationship working as seamlessly as possible, hold a discussion after each release to see what improvements / changes can be made

4. Communication is king in software development teams, and particularly when functionality changes, those changes must be communicated to the testing team to ensure the best results

5. When outsourcing, you’re hiring bright tech users and so a non-disclosure agreement is highly recommended to cover your business assets

6. Servers, firewalls and databases also need to be covered with a new or adjusted security plan

7. If you expect frequent changes in requirements, a flexible SLA and testing team are vital

8. Are your testers located globally or condensed in a specified area? It’s important to know where they are so that you are aware of any potential impacts on their use of the test environment

9. Determine the devices to be tested and the settings or configuration required, so that your test results are robust, clear and varied

10. A testing team needs prior knowledge of, or access to, acceptance criteria or application requirements in order to ensure the highest quality of test execution

So there you have it, a comprehensive list of things to think about before you select an outsourced testing team. For further guidance please contact our experts, or if you would prefer another ‘bite-sized’ piece of advice, please refer to our ‘Top Tip’ section below…