Aprende en Comunidad
Avalados por :
ABAP Unit Test Blog Series: Implementing TDD for Legacy Code
- Creado 01/03/2024
- Modificado 01/03/2024
- 30 Vistas
0
Cargando...
ABAB Unit Test Blog Series
Finally done with my week 1 of the ABAP Unit OpenSAP course and thought of writing my idiotic rants:).
Actually I was thinking why all of a sudden this course was started by OpenSAP when we have our fellow mentor bfeeb8ed7fa64a7d95efc21f74a8c135 writing beautiful blog series long time back in 2013-2014. Even yesterday also he expressed his views about the same. I can relate in his blogs how OpenSAP course materials emphasize what he has been trying to convey for last so many years. The important question which I am struggling with is why NOW this course so late?
I wanted answer to it so the quest to understand the same started:)
This was the question which could actually help me in understanding the reason. Luckily I have access to ECC as well as 1709 system. So I thought of taking a look into the program structures of 1709. I checked my frequent used two programs one is tcode /UI2/FLIA(FIORI Launchpad intent analysis) and another is program /UI5/REPOSITORY*UPLOAD. And I can see the difference in the way the code is being structured. Usage of ABAP Unit classes is pretty clear as highlighted in screen shots.
It is pretty evident that for all new developments ABAP Unit test concept is being used exhaustively. I was also curious to know whether in VA01 our golden transaction has some change happened. Bingo, Even our VA01-SAPMV45A also has a unit test framework implemented as can be seen in screen shots.
It was clear that SAP is using it in most of the programs but still why this course NOW question remained unanswered. Still I was not able to connect the dots. Eventually my next thoughts went to what actually has changed?
If we look at the journey so far a lot has changed in the architecture of SAP. Two Important things which stand out are, one the frontend is decoupled from the logic and more processing has been pushed to the backend database. We are using FIORI Apps for almost everything and data is exposed via Odata framework. So SAP is gradually moving away from all the procedural codes towards more robust and solid foundation of object orientness. It is extremely tough to actually write Unit Test scripts with the existing procedural code containing thousands of global variables etc.
So now in era of simplification, it makes more sense for this course. ABAP Unit test adds more value with the current architecture of SAP.
Since at a higher level we are able to co-relate how the whole ABAP Unit test fits in the overall strategy of SAP. It makes more sense for me to at least investigate how to write testable code for our Odata services which we have created so far.
I hope to share that experience in my próximo blog . Please feel free to provide your feedback, I might be completely wrong:)
| 1 | Why SAP Started ABAP Unit Test - Current |
| 2 | ABAP Unit Test in Odata |
| 3 | ABAP Unit Test - Implementing TDD |
| 4. | ABAP Unit Test meets Legacy Code |
Finally done with my week 1 of the ABAP Unit OpenSAP course and thought of writing my idiotic rants:).
Actually I was thinking why all of a sudden this course was started by OpenSAP when we have our fellow mentor bfeeb8ed7fa64a7d95efc21f74a8c135 writing beautiful blog series long time back in 2013-2014. Even yesterday also he expressed his views about the same. I can relate in his blogs how OpenSAP course materials emphasize what he has been trying to convey for last so many years. The important question which I am struggling with is why NOW this course so late?
I wanted answer to it so the quest to understand the same started:)
¿Está SAP utilizando el concepto de unidad ABAP en sus desarrollos?
This was the question which could actually help me in understanding the reason. Luckily I have access to ECC as well as 1709 system. So I thought of taking a look into the program structures of 1709. I checked my frequent used two programs one is tcode /UI2/FLIA(FIORI Launchpad intent analysis) and another is program /UI5/REPOSITORY*UPLOAD. And I can see the difference in the way the code is being structured. Usage of ABAP Unit classes is pretty clear as highlighted in screen shots.
It is pretty evident that for all new developments ABAP Unit test concept is being used exhaustively. I was also curious to know whether in VA01 our golden transaction has some change happened. Bingo, Even our VA01-SAPMV45A also has a unit test framework implemented as can be seen in screen shots.
It was clear that SAP is using it in most of the programs but still why this course NOW question remained unanswered. Still I was not able to connect the dots. Eventually my next thoughts went to what actually has changed?
¿Qué ha cambiado realmente en el viaje de ECC a S4 HANA?
If we look at the journey so far a lot has changed in the architecture of SAP. Two Important things which stand out are, one the frontend is decoupled from the logic and more processing has been pushed to the backend database. We are using FIORI Apps for almost everything and data is exposed via Odata framework. So SAP is gradually moving away from all the procedural codes towards more robust and solid foundation of object orientness. It is extremely tough to actually write Unit Test scripts with the existing procedural code containing thousands of global variables etc.
So now in era of simplification, it makes more sense for this course. ABAP Unit test adds more value with the current architecture of SAP.
¿Entonces, qué sigue?
Since at a higher level we are able to co-relate how the whole ABAP Unit test fits in the overall strategy of SAP. It makes more sense for me to at least investigate how to write testable code for our Odata services which we have created so far.
I hope to share that experience in my próximo blog . Please feel free to provide your feedback, I might be completely wrong:)
Pedro Pascal
Se unió el 07/03/2018
Facebook
Twitter
Pinterest
Telegram
Linkedin
Whatsapp
Sin respuestas
No hay respuestas para mostrar
Se el primero en responder
contacto@primeinstitute.com
(+51) 1641 9379
(+57) 1489 6964
© 2024 Copyright. Todos los derechos reservados.
Desarrollado por Prime Institute
Hola ¿Puedo ayudarte?