Blog

Often functional test automation (UI test automation, REST test automation) gets created in the next sprint after the feature has been completed and sometimes even released to production. The reason for this is that the many think a feature needs to be fully implemented before test automation is created. Another reason is that there is not enough time in the current sprint and creating automation is therefore pushed to the next one.

The last step is to setup a build and deployment pipeline which automatically builds the docker image and deploys it into the ECS cluster.

Now that we have configured AWS, we can start with the implementation of the application.

In this tutorial series we are going to deploy a microservice to the Amazon Web Services Cloud with one click. In order to do so, we are going to set up our AWS Account and configure CodeCommit, S3, SNS/SQS and ECR to fit our requirements. Then we are going to use the microservice provided by Spring's Spring Boot Docker example and modify Amazon's Reference Architecture for CloudFormation to deploy our service. To connect Jenkins to AWS we are going to use different plugins that act as interfaces. Finally, we are going to write a Declarative Pipeline that checks out our code from CodeCommit, builds it, tests it and deploys it to CloudFormation using the modified reference architecture.

How chatbots are used in recruiting and what trends are emerging through the advent of artificial intelligence is highlighted in our recent blog article.

After discussing the Antipatterns in the previous blog post, lets focus on getting things right in this one. There are many best practices and patterns when it comes to CI/CD - I tried to choose patterns that are either very important or often done wrong. The latter is the case for our first topic.

I'd like to start this blog with a post about CI/CD Patterns and Antipatterns. I guess all of them are in general well known but many of the Antipatterns still persist. Also, if you are looking for a quick fix, you should really check the list. If you are a newbie regarding CI/CD, then the list should at least help you to understand the fundamental concepts behind CI/CD, which will be explained in detail in future posts.

Nowadays customers expect IT-companies to deliver new features faster than ever. In the past, it might have been enough for enterprise companies to deliver a new version of a system every quarter. In the last few years, many of them had to switch to monthly releases to fulfill customer needs. Still that seems to be not enough. Lately customers start to expect a continuous flow of new features, like the big IT companies Google and Co. already do it for years.

From 25 May 2018, the EU General Data Protection Regulation will enter into force. Michael Reichenberger, Managing Director of Qualysoft GmbH Switzerland, has compiled the most important data protection questions of our customers and answered them for you.

Many companies complain about the IT labour shortage, which slows down their success-critical digital developments enormously. At the same time they shy away from nearshoring in neighboring countries. Why we believe that this is the best solution and how you can actually benefit from nearshore teams? We have summarized three powerful arguments that will convince for you.

The latest major release of Aurea CRM, version 10, provides new and improved features for even easier handling that enable you to finish your work faster. Highlights include the integration of Skype for Business and streamlined campaign management - read more in our compact summary.

Mag. Siegfried Ollinger, representative of our customer Wiener Städtische Versicherung, has summarized what you should consider not only in setting up, but also in the further development of your software test automation. Enriched with the experience our experts at Qualysoft, we present you the 10 Do's and Don’t’s of automated testing.