What is software testing?
This year we have spent a lot of time in our blog trying to provide insights on general testing and project frameworks, along with tips for the different types of test we deploy. Today though, in what is the first of a series of articles, we wanted to take a step back and give the eTestware answer to a much broader question that is no less important – after all, there are almost a billion Google search results to this very ‘poser’…
A standard definition of software testing would be something like this:
A software test is essentially an investigation carried out in order to analyse the quality of a product or service.
Pretty simple, and yet incredibly important in the grand scheme of things and an activity which requires a considerable degree of skill and experience – qualities that the team at eTestware have in abundance.
As part of theICEway ecosystem of companies, our testing experts have spent many years crafting and honing their abilities, all the while adhering to a strict ethos: SMART. Our outsourced software testing solutions are based around a fully SCALABLE approach which is completely MANAGEABLE for our team – leaving our clients free to focus their efforts where they are most needed. We are 100% AGILE and will tailor our efforts towards your unique position, supporting your own internal resource if required or taking all of the strain. We also pride ourselves on being both RELIABLE and TIMELY, which means that you can rest safely in the knowledge that all projects will be completed in the most efficient manner and on time.
There are a number of different testing types, methods and approaches that can be taken and we will look more closely at all of these in the weeks ahead but for now, here are just a few of each to ‘whet your appetite’:
Testing types: Manual & automated
The difference? Essentially a manual test sees the tester using a hands-on approach, often with the end user’s perspective in mind, whilst an automated test makes use of automation tools.
Testing methods: Static & Dynamic
The difference? Static testing involves the analysis of documentation and files to ensure that the product is being built correctly, whilst dynamic testing sees the actual product itself being tested.
Testing approaches: White box, black box & grey box
The differences? White box looks at an application’s internal code structure, black box does not and instead evaluates software functionality, whilst grey box combines both… Simple!
Next week we will go into detail on all of these but if you cannot wait until then, get in touch with eTestware today and we’ll be happy to guide you through!
If you need help with your own software testing, contact our test experts today and we’ll be glad to help; there has never been a better time to outsource, so let us take your hand and lead you out onto theICEway…