Skip to content

Commit 6e56e50

Browse files
tobiashofmanntobiashofmann
authored
Merge pull request #29 from tobiashofmann/voting-2024.6
Voting 2024.6
2 parents d90e5f3 + 88eb25a commit 6e56e50

File tree

17 files changed

+268
-5
lines changed

17 files changed

+268
-5
lines changed

‎definitions/frameworks/abapunit.toml‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
[page]
2+
title = "ABAP Unit"
3+
description = "ABAP Unit is a unit-testing framework that is integrated into the ABAP language.<br/><br/>In unit testing, a developer ensures that the correct behavior of the smallest testable units – such as the methods of classes – of his or her code is verifiable. Unit testing makes it easier to verify quality, to refactor code, to perform regression testing, and to implement according to the test-driven development model."
4+
reason = "The way to do unit testing in ABAP"
5+
support = "Supported"
6+
7+
[links]
8+
"SAP Help" = "https://help.sap.com/doc/saphelp_nw75/7.5.5/en-US/4e/c18be06e391014adc9fffe4e204223/content.htm"
9+
"Unit Testing with ABAP Unit" = "https://help.sap.com/doc/saphelp_nw75/7.5.5/en-US/4e/c4a6e06e391014adc9fffe4e204223/content.htm"
10+
"ABAP Keyword documentation" = "https://help.sap.com/doc/abapdocu_752_index_htm/7.52/en-US/index.htm?file=abenabap_unit.htm"
11+
"Wikipedia (de)" = "https://de.wikipedia.org/wiki/ABAP_Unit"
12+
13+
[config]
14+
label = "ABAP Unit"
15+
ring = "USE"
16+
quadrant = "Frameworks"
17+
active = true
18+
moved = 0

‎definitions/frameworks/cleanabap.toml‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
[page]
2+
title = "Clean ABAP"
3+
description = "Programming languages enable us to say the same thing in different ways. While all of them may be correct, some may be more efficient, easier to understand, and more robust than others."
4+
reason = "Clean code guidelines for ABAP"
5+
support = "No real support. Best practice for writing ABAP code."
6+
7+
[links]
8+
"Homepage" = "https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md"
9+
"Blog: ABAP Tools for Clean ABAP" = "https://community.sap.com/t5/technology-blogs-by-sap/abap-tools-for-clean-abap/ba-p/13577378"
10+
11+
[config]
12+
label = "Clean ABAP"
13+
ring = "USE"
14+
quadrant = "Frameworks"
15+
active = true
16+
moved = 0

‎definitions/technology/soap.toml‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
[page]
2+
title = "SOAP"
3+
description = "Simple Object Access Protocol (SOAP), provides the definition of the lightweight protocol for XML based information, exchanged between parties in a distributed environment. SOAP version 1.2 supports major features, required for communication with other Web service vendors."
4+
reason = "SOAP failed to deliver on the promises and expectations. It is still widely used, also by S/4HANA public cloud.<br/><br/>As it was once regarded standard, many tools are available to develop apps that use SOAP. For new developments, it is recommended to use OData (v2/v4) as API. When possible, SOAP APIs should be replaced with RAP services."
5+
support = "Supported."
6+
7+
[links]
8+
"SAP Help" = "https://help.sap.com/doc/saphelp_nw75/7.5.5/en-US/48/52347a08e672d0e10000000a42189c/content.htm"
9+
"SAP Business Accelerator Hub" = "https://api.sap.com/content-type/API/apis/SOAP"
10+
Wikipedia = "https://en.wikipedia.org/wiki/SOAP"
11+
"SOAP Version 1.2 W3C recommendation" = "https://www.w3.org/TR/soap12/"
12+
13+
[config]
14+
label = "SOAP"
15+
ring = "HOLD"
16+
quadrant = "Technology"
17+
active = true
18+
moved = 0

‎definitions/tools/abapcleaner.toml‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
[page]
2+
title = "ABAP Cleaner"
3+
description = "ABAP cleaner is a configurable tool with the ambition to automate whatever can be automated with respect to ABAP code style.<br/><br/>With ABAP cleaner, you can clean any amount of code from a single statement to an entire code document with one keystroke. ABAP cleaner then applies 70+ different cleanup rules to your code section, cleaning approx. 1 MB of code per second."
4+
reason = "Useful tool for clean code. Align ABAP coding with best practices. Use it together with ADT."
5+
support = "Supported by the community"
6+
7+
[links]
8+
Homepage = "https://github.com/SAP/abap-cleaner"
9+
10+
[config]
11+
label = "ABAP Cleaner"
12+
ring = "USE"
13+
quadrant = "Tools"
14+
active = true
15+
moved = 0

‎definitions/tools/atc.toml‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
[page]
2+
title = "ABAP Test Cockpit"
3+
description = "The ABAP Test Cockpit (ATC) is a tool for doing static and dynamic quality checking of ABAP code and associated repository objects."
4+
reason = "The way to for quality checking ABAP Code."
5+
support = "Supported"
6+
7+
[links]
8+
"SAP Help" = "https://help.sap.com/docs/ABAP_PLATFORM_NEW/ba879a6e2ea04d9bb94c7ccd7cdac446/62c41ad841554516bb06fb3620540e47.html?locale=en-US"
9+
"ABAP Keyword documentation" = "https://help.sap.com/doc/abapdocu_758_index_htm/7.58/en-US/index.htm?file=abenabap-testcockpit_guidl.htm"
10+
"DSAG Leitfaden (de)" = "https://www.dsag.de/wp-content/uploads/2021/12/dsag_leitfaden_atc_2020_06.pdf"
11+
12+
[config]
13+
label = "ATC"
14+
ring = "USE"
15+
quadrant = "Tools"
16+
active = true
17+
moved = 0

‎definitions/tools/ecatt.toml‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
[page]
2+
title = "Extended Computer Aided Test Tool (eCATT)"
3+
description = "Use extended Computer Aided Test Tool (eCATT) to create and execute functional tests for software. The primary aim is the automatic testing of SAP business processes. Each test generates a detailed log that documents the test process and results.<br/><br/>eCATT provides a environment for developing functional tests. Rather than create a single object that defines every aspect of a test, eCATT has four separate object types. The first three form the building blocks of a test, and the fourth combines the others into a complete test case. The following graphic summarizes the development process and how the different eCATT objects fit into that process."
4+
reason = "Recommended for testing Reports"
5+
support = "Supported"
6+
7+
[links]
8+
"SAP Help" = "https://help.sap.com/docs/ABAP_PLATFORM_NEW/c6663103e6ad47dcb8bb830d85137077/496d2fa0e0221ec6e10000000a42189b.html?locale=en-US"
9+
"Wikipedia (de)" = "https://de.wikipedia.org/wiki/ECATT"
10+
11+
[config]
12+
label = "eCATT"
13+
ring = "USE"
14+
quadrant = "Tools"
15+
active = true
16+
moved = 0

‎definitions/tools/kapsel.toml‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
[page]
2+
title = "Kapsel SDK"
3+
description = "The Hybrid SDK (Kapsel) is a set of SAP plugins for Apache Cordova.<br/><br/>The Hybrid SDK (Kapsel) leverages the Cordova application container and provides Kapsel plugins to make the Cordova container enterprise-grade, allowing it to more seamlessly integrate with SAP Mobile Platform Server and mobile service for development and operations. The Hybrid SDK (Kapsel) plugins provide capabilities like application life cycle management, implementation of a common logon manager and single sign-on (SSO), integration with SAP Mobile Platform Server-based push notifications and so on. Since the Hybrid SDK (Kapsel) is implemented without modifying the Cordova container, it is compatible with anything else you develop with Cordova, and allows you access to the latest Cordova features and bug fixes when you build your application."
4+
reason = "Legacy and not recommended. Switch to one of the native Fiori SDKs or better to MDK. SAP abandoned the hybrid app development path (as did other, see Cordova). Kapsel for hybrid apps is not recommended. If MDK is not an option, maybe PWA for UI5 apps can be used."
5+
support = "EOL 31.12.2025"
6+
7+
[links]
8+
"SAP Help" = "https://help.sap.com/doc/f1944845cb7b4cb886ebfbd5fa720c64/3.0.14/en-US/7c03a218700610149f94dd65a52e798f.html"
9+
"Kapsel App Development" = "https://help.sap.com/doc/d9c75eebcfa840c8a4aa4b0e6a8136de/3.0.14/en-US/7c05514870061014ae31b35a27134786.html"
10+
11+
[config]
12+
label = "Kapsel"
13+
ring = "STOP"
14+
quadrant = "Tools"
15+
active = true
16+
moved = 0

‎definitions/tools/sapgui.toml‎

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,16 @@
11
[page]
2-
title = "SAPGui"
3-
description = "Proprietary client from SAP for connecting to an SAP system and run e.g. transactions or reports."
4-
reason = "For development: use ADT first. Adopt reports to Fiori for end users. When reports: use Web Gui mit Personas"
2+
title = "SAP GUI"
3+
description = "Proprietary client from SAP for connecting to an SAP system and run e.g. transactions or reports. This here refers to SAP GUI for Windows and SAP GUI for Java.<br><br>SAP GUI is SAPs universal UI technology for working with SAP systems, such as SAP ERP or SAP Business Suite.<br><br>SAP GUI is used to display dynpro-based applications created in the SAP NetWeaver Application Server ABAP"
4+
reason = "SAP GUI is used to display dynpro-based applications. These are deprecated. Applications should be using different technology and adhere to the Fiori UX.<br><br>For development: use ADT first. Adopt reports to Fiori for end users. When reports: use Web Gui mit Personas<br><br>Application should be at least accessible by a web browser. Accessing an SAP S/4HANA Public Cloud system via SAP GUI is not possible."
55
support = "Supported for Windows. For MAC: constant pain."
66

77
[links]
8-
"SAP Help" = "https://help.sap.com/docs/sap_gui_for_windows?locale=en-US"
8+
"SAP Help" = "https://help.sap.com/doc/saphelp_nw75/7.5.5/en-US/9a/d405e746ef43288755cb80a14be542/content.htm"
9+
"SAP GUI for Windows" = "https://help.sap.com/docs/sap_gui_for_windows?locale=en-US"
910
Wikipedia = "https://en.wikipedia.org/wiki/SAP_Graphical_User_Interface"
1011

1112
[config]
12-
label = "SAPGui"
13+
label = "SAP GUI"
1314
ring = "STOP"
1415
quadrant = "Tools"
1516
active = true

‎definitions/tools/segw.toml‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
[page]
2+
title = "SEGW"
3+
description = "SAP Gateway Service Builder is a design-time environment, which provides developers an easy-to-use set of tools for creating services. The Code-based OData Channel consumes it and supports developers throughout the development life cycle of a service.<br/><br/>Service Builder caters need of both experienced and less experienced developers for exposing the data for an easy consumption, using a variety of platforms, frameworks, and devices, in a single transaction. While experienced developers have maximum flexibility to define a new service and integrate their own source code, less experienced developers can reduce the time and effort involved in creating services by importing existing definition files and implementing content generators.<br/><br/>Service Builder provides an OData-compliant modeling environment for creation and maintenance of OData services without any need for programming. Service Builder visualizes all the development artifacts that developers need to create a service."
4+
reason = "OData sevices should be developed using RAP. SEGW is not in active development since a few years. Not recommended for OData v4 services."
5+
support = "Legacy."
6+
7+
[links]
8+
"SAP Help" = "https://help.sap.com/doc/saphelp_nw74/7.4.16/en-us/cd/dd22512c312314e10000000a44176d/content.htm?no_cache=true"
9+
"SAP Note 2485370" = "https://me.sap.com/notes/2485370/E"
10+
11+
[config]
12+
label = "SEGW"
13+
ring = "STOP"
14+
quadrant = "Tools"
15+
active = true
16+
moved = 0

‎definitions/tools/ui5linter.toml‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
[page]
2+
title = "UI5 linter"
3+
description = "UI5 linter is a static code analysis tool for UI5 projects. It checks JavaScript, XML, JSON, and other files in your project and reports the findings. It lists problematic code, which is not following the UI5 best practices."
4+
reason = "New tool. First version recently released.<br><br>From the announcement blog: While the initial version of UI5 linter already provides good value, it is not yet covering all aspects and not all best practices for UI5 2.x."
5+
support = "Supported"
6+
7+
[links]
8+
Blog = "https://community.sap.com/t5/technology-blogs-by-sap/introducing-ui5-linter/ba-p/13633898"
9+
GitHub = "https://github.com/SAP/ui5-linter"
10+
11+
[config]
12+
label = "UI5 linter"
13+
ring = "ADOPT"
14+
quadrant = "Tools"
15+
active = true
16+
moved = 0

0 commit comments

Comments
 (0)