Skip to content

Include class name level grouping in Packages view even when package present (Spock2 + Allure + Groovy) #850

Description

@karltiirik

Is your feature request related to a problem? Please describe.
Project with Spock2 + Allure + Groovy. I want to have 2 ways of looking at the tests. 1. is behaviors view using the Epic, Feature, Story annotations (this works). 2. is code structure level. Packages view makes the most sense for this purpose. When you have no packages, then the tests are grouped under test class name:
Kuvatõmmis 2022-11-17 225636
But once you add at least one depth of package hierarchy, all the tests are grouped under package name, so you lose test class name level grouping:
Kuvatõmmis 2022-11-17 225412

Describe the solution you'd like
Class name level grouping present even when packages are present. This can by a configurable feature if needed.

Describe alternatives you've considered
Using the Suites view as an alternative. In that case there needs to be a intermediate class for each sub-package. So if you initially have:

class PostTest extends Specification {...}

in package posttests, then you need to add

class PostTests extends Specification {...}
class PostTest extends PostTests {...}

so then the Suites view will match the structure. But this means effort to keep the package structure and the inheritance structure in sync.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions