Allow unimplemented interface methods in test classes

[sbcgua]

[larshp]

in 702, I don't know any way to get around the syntax warnings

for abapGit I do prefer to not have syntax warnings in the source code. Its a mess and a lot of work to add empty methods, but PARTIALLY IMPLMENTED, https://syntax.abaplint.org/?filter=interface#/statement/InterfaceDef, only works from 740sp02 and up

[sbcgua]

hmm, that's interesting ... in my system "Validate" does not give the warning for a test class. However SCI does. And seems that cannot be disabled by params. That's very unfortunate. I was so happy to find that test classes implicitly support "partial implemented" on 731. Otherwise all methods of the interface must be redefined as empty methods which sucks.

Hmmm, i don't know. What do you think ? The test classes works with partially implemented and at least does not show this error on Ctrl+F3. And this makes sense. Maybe create an option in the rule ?

class ltcl_da_stub definition final for testing duration short risk level harmless.
  public section.
    interfaces zif_ede_data_accessor. " HAS MANY METHODS AND JUST ONE IMPLEMENTED
    " AND NO WARNINGS FROM CTRL+F3
endclass.

[larshp]

we can add an option no problem, but I prefer not enabling it for abapGit

long term solution is moving abapGit to 740 syntax, and then automagically downporting it

[sbcgua]

hmmm, ok.

[pokrakam]

After implementing 76 empty IF_HTTP... methods, I would welcome an option to disable this. I can see abaplint can ignore it for test classes but downporting fails.

[larshp]

PARTIALLY IMPLMENTED, https://syntax.abaplint.org/?filter=interface#/statement/InterfaceDef, only works from 740sp02 and up