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 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?
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”.
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.
Security is a difficult topic to control for software projects, as is proven by the constant reports of data leaks in the media. For software developers, it is difficult to oversee the sort of influence that their daily work, which is not directly linked to security issues, has on the security of their applications.
The first article in this series – “Version names with Maven: Creating the version name” –shows how during the build, and with Maven’s help, a version number, enriched with further information can be written into a manifest, properties or HTML file. Based on the first article, this second one describes how it can be read from within the application. This is helpful in many cases: You can immediately see which version is deployed on which stage, the version information can avoid misunderstandings in error reports, etc.
In many cases, it may be useful to be able to extract the current version number of an application: You can immediately see which version is deployed on which stage, the version information can avoid misunderstandings in error reports, etc.
80% of lifetime costs goes to maintenance and hardly any software is maintained for its whole life by the original author. Therefore it is crucial that code is written in a comprehensible manner. Code conventions help to achieve this.
Although Apache Shiro includes a powerful and flexible tool for fine-grained allocation of authorizations with its WildcardPermissions, one is faced with its limitations when it comes to complex scenarios. This article shows how any authorization checks can be implemented autonomously using the Permission interface.
