Before the pandemic, people were used to travel to the training location to participate. Now, however, during the pandemic, things are a little different. Many companies now offer their training online.
This blog post shows the construction of a neural network for an artificial intelligence. In addition, it is explained by way of example how this AI can be trained with the help of training data, backpropagation and evolution, but also which dangers can occur in this process.
After the last article looked at important key figures from the static analysis of a code review, aspects of manual analysis are now highlighted. How does an architecture analysis work in a code review and what conclusions can be drawn from it?
This article describes which key figures can be collected by a static analysis and how these can be interpreted. The main focus is on technical debt and complexity.
This post follows on from the previous part. If you have not yet read it, we recommend you take a few minutes to do so now.
Unit tests can be useful for ensuring code quality and correctness. Not every unit test makes sense, however, and bugs often manage to escape detection by unit tests. How can test quality be increased so that programming errors are detected earlier and more reliably?
Naming conventions are an important part of coding conventions. Naming conventions are the rules for how “things” are named. In the case of a database, the “things” being named are schema objects such as tables, sequences, indexes, views, triggers as well as constraints. In a database it is essential to choose names with particular care.
With the automated integrative testing of software that works with a complex JPA data model, it is invariably the case that sooner or later, one will face the question of how it is possible to create semantically meaningful test data without great cost. This article shows how Groovy can be used in order to define a Domain Specific Language (DSL) that enables test data to be defined so that it is easily readable, modular and separate from the actual test code.ieren.
The Pipeline plugin (formerly Workflow plugin) for Jenkins revolutionises working with Jenkins by allowing for the creation of build jobs as code. As a result, build pipelines can be put under version control, become reusable,testable and more easily readable, among other things, as something “put together with mouse clicks”.
Software quality remains a topic that is constantly discussed within the developer community, because customers as well as developers are very much aware of what consequences faulty software can have.
In each project you face the same challenge again: creating a finished product that meets the requirements. In order to do this successfully, there are countless approaches and possibilities. A solution is the use of Redmine, an issue-tracking application that can be simply adapted to meet one’s own individual needs.
This article describes which key figures can be collected by a static analysis and how these can be interpreted. The main focus is on technical debt and complexity.
In this article, I am going to report on the test framework Gauge from the ThoughtWorks corporation. This is a tool which I met for the first time when I was writing automated end-to-end tests (E2E) for various web applications within a web platform. The purpose of the tests is to progressively check whether certain functions such as single sign-out, appropriate redirection to other pages or access authorisations to certain elements of a selected web application function as they should.
People often talk about high quality software products, but what is that? How can you measure or compare the quality of an application? Let’s take a closer look at this topic and discuss what quality is all about and how it can be improved.
