Software testing tips before outsourcing

Here at eTestware, our testing experts are often called upon to assist in a ‘right-sourced’ capacity. In those scenarios we provide support to existing IT teams to ensure products and systems are ready for launch. On occasion, it is clear that there have been few or zero sense-checks carried out before we are called in. Some software bugs can be detected from even the most basic of initial sweeps. Here then, are some simple software testing tips before outsourcing becomes a consideration.

NB: We neither engage in nor champion ‘outsourcing’. For us, it is ‘right-sourcing’ or DIY only.

Conduct basic functionality testing

Start by checking all screens to ensure each button works. You must also test to verify that simple text can be entered into the relevant fields without causing the software to crash. If API access is key then test the basic API functionality ahead of more intense testing efforts. If you find a fault, simply notify the testing team about it.

Deploy static code analysis tools

We recommend that you deploy static code analysis tools to enforce coding standards. You should also consider configuring these tools to run automatically within the build process. They are great at identifying security vulnerabilities in the source code.

Review your code

After the functional software testing steps have been taken, it is time to enlist another to look at the source code. This extra pair of eyes can help to uncover errors and we highly recommend it before you give your code to testers.

Run unit tests

Whether the unit is a method, class, or component, unit tests should be carried out. You must verify that all is working as expected, testing across a range of valid and invalid inputs. Ideally, tests should be completed each time there is a change to the source code repository. Run the tests on the development machine also – unit tests need to be extensive. If they fail, either fix them or flag them.

Conduct single-user performance testing

We have encountered many organisations placing great emphasis on load and performance testing in the back-end but overlooking the importance of single-user performance on the front end. Tackling the back-end is one thing, but what if displaying a web page on a local web server takes too long? Always check this and fix the issue that is slowing things down before you hand over to a right-sourced team.

Conclusion

So there you have it, software testing tips before outsourcing. We love testing; the process, the attention to detail, these are things we relish tackling. However, we know all too well that our experience should be utilised in the right way. Our testing experts should not be deployed to flag incorrect spellings in comments within your code. This is a key aspect of right-sourcing. Hopefully the tips above will help you generate some quick wins, whilst allowing us to focus on what we do best.