We have seen previously SONAR ‘Blockers’ for ABAP, whose name indicates that any such violation cannot be tolerated, and ‘Critical’ defects, severe enough to require immediate correction, but for which an exception can be accepted, if it is very rigourosly justified.
In our SONAR Quality Profile, ‘Blockers’ focus on anything that can stop a transaction or program and ‘Critical’ on programming practices that pose a risk to the performance.
We will conclude this series on best practices of ABAP programming with the remaining rules, which will mainly affect the maintainability of the code.
We have seen in the previous post the most important violations to best practices of ABAP programming.
These defects are ‘Blockers’: the code can not go into production until a correction is performed. No exception is permitted: zero tolerance, because the risk is too high to see a transaction aborted and the user unable to perform the desired treatment. Continue reading
After an interruption due to the reorganization of the blog – I hope you enjoy the new interface – we continues our series on the analysis of ABAP code.
We saw last time how to set up our first analysis of ABAP code with Sonar and Jenkins.
This week, we will examine the firsts ABAP rules, at least the most critical in terms of good programming practices. Continue reading
After seeing in the previous post how to extract the ABAP code, with the help of the extractor provided by Sonar, it’s time to start our first analysis … but not with the code previously extracted.
In fact, the first time I set up an analysis for a new technology, I will make a first test with some files which I am sure have no problem, because this code has already been tested and proven by Sonar, and is downloadable from this page: Sonar Project Examples.
In this page you will find links to other pages in which navigate to search for different examples of projects. Or simply click on the link to download a compressed file.
We continue our series of posts on ABAP code analysis with Sonar. Today: the extraction of code.
We have seen in our first article Sonar & ABAP – What you need to know, that the ABAP code is stored in the SAP Workbench, so that we’ll have to install a program in the Workbench to extract the code to analyze. Yes, we will have to connect to the Workbench to install and run this program. Continue reading
Let’s continue the previous post about the questions to prepare for the implementation of a process of analysis of ABAP code, which we have seen that it was largely based on use cases.
So I invited again Walter, Quality Director of Drago Solutions, who accompanied us since the beginning of this series of articles, to answer a few questions about this subject. Continue reading
We continue our series on the analysis of ABAP code.
We have seen in the previous post what you need to know about the SAP technology and ABAP code.
We will now list the questions to ask to the project teams in order to prepare the extraction of code, the analysis and their organization in the Sonar dashboard. Continue reading
We started in the previous post this new serie about ABAP code analysis, with the help of Walter Strobl, Director of Quality in Vision IT and specialist of SAP environments.
Today, we will see what is necessary to know to implement a process of ABAP code analysis with Sonar. Continue reading
My blog Qualilogy is almost one year old (at the end of the month), and I found that almost all the posts that I have written are about quality of code and applications and are intended primarily for two types of audiences:
- People familiar with the concepts of Quality, and the use of metrics, often beyond the field of code quality. They are often consultants or Quality managers, usually with the experience of various technologies and languages, able to interpret a dashboard and make audits. However, they are not all experienced in the use of code analysis tools, and sometimes feel that the J2EE world and Open Source tools are too technical for them.
I tried to show that it is actually very simple, even without technical knowledge, through several articles describing the installation and the use of tools as Sonar and Jenkins, and the benefits of many plugins created and maintained by the Sonar community.
- People who are users or even experts of these tools as they use them on their projects every day or on the J2EE applications of their company but do not have the experience of other technologies. When in fact, you just some basic knowledge in order to analyze the other code than J2EE.
For example, the series we did about Cobol analysis, starting with this post Cobol code analysis – What you need to know.
As I had plans to make a series of the same type for the SAP technology, I asked his participation to someone who is not only a friend but also an expert in the field of quality and SAP world, and the use of analysis tools code. Continue reading