Updates

Take a peek under the hood

Individual test environments

Our development environment is going to contain individual test environments for every developer. This allows us to test different elements and features of the software simultaneously, allowing us to innovate quicker. Development goes hand in hand with extensive testing, whereby it’s very useful for every developer to have their own test environment. Having individual test environments is not as obvious as it seems, but it is definitely going to add to our innovative strength.

The importance of testing

Every new feature is tested according to DTAP (development, testing, acceptance, production). We thoroughly test our new features because we develop software for big companies and organisations that handle a large amount of customer contact every day. Is a new feature of the software not working properly? This risks that the chat cannot be used, a risk we try to minimise at all times.

The importance of multiple test environments

The problem of having just one test environment is that only one feature can be tested. As a consequence, a line of features to be tested is piled up. When every developer has their own test environment, our tester is able to test more as the waiting time of developers can be filled. It is In this environment that, initially, automated tests are executed. When the development code is passed on through the automated tests, the tester can then test the feature functionally. This provides every developer with their own test environment to make sure the tester can execute more tests simultaneously and developers can develop quicker. Conclusion, with more test environments we’re able to release features quicker.