Moving actions at #AbapConf with Martin Johnen and his talk on Fucus and clean code

Looking forward to our Keynote at #ABAPConf Tomorrow at 10:30 CET with @peter-langner.bsky.social
Watch live at:
www.youtube.com/live/SncN0yl...

6. Add Methods in Classes.
Created nice Method definition. Great would be if it automatically creates an empty body as well.

6. Unit Test create test double

the proposal does not make sense at all.

cl_abap_testdouble=>create( cut )->expect( 'get_wbs_supplier' )->and_return( wbs_supplier_tab ).

It would be a person I'd say he have any clue about unit tests

5. Value Statements

cp invents datatypes that do not exist. This is not of help.
The intention is to use cp to do the writing data ...
But somehow it needs to finde the data types
or ask for them

4. unit test Part 2

"create mock data for my unit test using cl_osql_test_environment and the following tables
zgt_wbs_archive zgt_wbs_customer zgt_wbs_supplier"
The result was not so much usable. Insert of test data was wrong... But I guess there is only a very little codebase as reference.

3.1 Additional

There is an Interface... but looks like copilot can not access the cotext attound ... to find the interface ... I will try again after opening those interfaces etc...

3A. Code completion for test class is not that great.

- here it looks like the copilot does not understand what a test class does. Syntax makes sense using "for testing ..." but implementation of the (not existing ) business interface does not make sense.

3. Test Classes

Using the chat the generation of a basic test class was working. An interface Type was invented that does not exist but anyway...

It would be great if you could write in the code the comad for copilot to generate a full test class.

I will,
here is my first feedback:
1. installation is simple and fast, nice

2. Code completion are displayed and helpful. but sometimes not "intelligent" enough. But othen very helpful.
you will take some time to get used to it.