Skip to content

Unit Testrun - Handle development package hierachies  #5

@andau

Description

@andau

Currently the Unit Testrun is only executed for the package the ABAP development object is assigned. Also a triggered Unit Testrun of an eventually parent package is desirable.

Example
MainPackage
-> Subpackage
-> Development object (class_of_subpackage.class)
-> Development object (class_of_mainpackage.class)

Everythink works perfect if only the Subpackage(s) is (are) added to the Unit testrun.

If the MainPackage is added to the Unit testrun too, an eventual error in the Development object of the class_of_subpackage.class is counted twice and stays in the mainpackage when fixed in the subpackage as only the Unit Testrun of the subpackage is triggered.

Therefore an option would be to only include the main package and get the Unit Testrun for the MainPackage executed when a development object of this package or a subpackage is activated. But as the MainPackage is currently not triggered thats not an option.

Current code in SapConnection.java:
IInactiveCtsObject ctsObject = ...
IAdtObjectReference ref = ctsObject.getObject().getRef();
String packageName = ref.getPackageName()
// --> TODO how to get an eventually existing parent package of the packageName

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions