Software testing

Why do we need software testing?

Have you ever found a bug while trying to transfer money via e-bank, or ordering something from a webshop like Amazon? If yes, then you know how annoying it is, and how it can destroy the reputation of a vendor. We put great emphasis on avoiding situations where the end-user is the first person to try out how the application works. Therefore, we test our software on different levels: our developers write unit tests to ensure that all the smallest items in the code work fine; integration tests, which check whether these items are working together as a system; then come our manual testers, who put the entire product under the microscope again.

Software testing methodology 1

The team

The testing team was founded with a focus on diversity: our testers have very different backgrounds, education and personal interests. They each use their unique views and thought processes to discover errors and mistakes, which couldn’t have been found by programmers. We also have some things in common: curiosity, a strive for continuous improvement and an internal education of software testing methodology.

Combine these, and you have a team of ISTQB certified testers at your service, who can flexibly apply the most fitting tools and methods to your project.

Software testing methodology 2

Testing types

Our activities cover the following testing types during a software development project:

  • functional testing:we verify if the new functionalities required by you are working as designed
  • regression testing:we verify if the previously working functionalities are still able to perform unchanged, even after the introduction of new features
  • compatibility testing:we verify if the application runs correctly on all of the browsers, devices and platforms that you requested

You are not sure what the things above mean? Or what the difference between a sanity and a smoke test is? Worry not, you can trust us with building the whole testing process.

Software testing methodology 3

How does the whole process look like?

  1. Create the testing strategy to define the best fitting approach, necessary test levels and types, and the required tools
  2. Set up the test plan so that you can always track the progress
  3. Prepare the written test scenarios, which you will be able to review
  4. Execute the test cases, document defects and re-test solved issues
  5. Provide a test report, which includes information about the state of the project so that you can make your decisions based on actual data
Software testing methodology 4

What if my software is not being developed by you?

Having your own software is not an issue either; we offer several options that you can profit from:

If you have a software being developed for you but don’t want to employ your own full-time testing team, we can take over the user acceptance tests and give you the objective information you need. In this case, we set up the testing process as described above. With this method, you will get access to our fully trained testers at the fragment of the cost of setting up a whole team.

if you have a software being developed for you but don’t know which approach or tools to pick for testing, we can support you with setting up the best fitting strategy and educating your team on how to apply it.

Software testing methodology 5