Integration Tests
Java Async testing
A Java Spring Boot powered REST Api has operations, which require minutes to finish, because of multiple HTTP connections and database queries with lots of data.
These tasks are executed Asynchronously.
The functionality needs to be tested in the integration tests (using less data, so the operation runs in seconds).
Now we use Thread.sleep(…) and the tests take 10minutes to finish every time, while we see the operations finished sometimes for 2-3 seconds and the overall required time would be 5minutes. Bu we also observe flakey tests from time to time, because the operations take 100ms more than out waiting time.
How can we test waiting time that is close to the real waiting time and remove the cause of the flakey tests?
Taggings:
Integration testing with RabbitMQ and Postgres in Spring Boot when using CI (and not only)
The application to test uses Postgres and RabbitMQ. It also uses “spring-boot-starter-amqp” and its “RabbitTemplate”. The app runs migrations with Flyway and uses Postgres syntax.
Because of inconvenience and since there is CI (Continuous Integration) in a remote server, running RabbitMQ and Postgres instances can’t be provided. How can we set up our test environment to provide those RabbitMQ and Postgres DB instances, so it is clean on each test suite run?
Taggings:
How to setup a Canoo Webtest Environment
I am working as part time softwaretester in a software development company.
In the last months the main part of my work was testing the same testcases over and over again.
All startet with a few testcases for a relatively small frontend. But as time goes by, the software developed and the functionality grew...and so grew the frontend of the application and the complexety of the testcases.
At the beginning i only had about 30 testcases which covered the overall functionality of the application. Now i have to test about 100 testcases in the same time.
So some solution had to be found.
The great thing of the application i have to test is, that most of the navigation and layout stays the same, even when new functionality is implemented. That makes an automatic regression very easy.
My goal was now to find a free, easy to understand, easy to install and easy to use test tool which fits my requirements.
I chose "Canoo Webtests". It's an XML based test tool, which is really great.
It produces very good testreports, it generates screenshots during the automated testing and it is relatively easy to install.
Because its XML based the testcases are very easy to implement, and persons who are not so familiar with programming can understand and implement the testcases very easy.
Taggings:
