One level deep describe is ignored in suites view

[kirill-konshin]

I'm submitting a ...

• [x] bug report
• [ ] feature request
• [ ] support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

I have a test suite:

describe('TabPanel', () => {
    it('will work if appears several times at a page', () => {

It generates following JSON:

{
  "uuid": "c4d05013-b522-45f1-9860-a4fd58e2a4a5",
  "historyId": "TabPanel will work if appears several times at a page",
  "status": "passed",
  "statusDetails": {},
  "stage": "finished",
  "steps": [],
  "attachments": [],
  "parameters": [],
  "labels": [
    {
      "name": "parentSuite",
      "value": "TabPanel"
    }
  ],
  "links": [],
  "start": 1586542601975,
  "name": "will work if appears several times at a page",
  "fullName": "TabPanel will work if appears several times at a page",
  "stop": 1586542602032
}

When I open suites view in Allure EE this test does not belong to any suite:

What is the expected behavior?

I figured that you should have double describe in order to make Suite grouping work, like this:

describe('Store', () => {
    describe('cloning', () => {
        it('should provide a new store with the same data as source', () => {

Then json will be like this:

{
  "uuid": "f217cfaf-0c46-46db-90ea-38615cef4a29",
  "historyId": "Store cloning should provide a new store with the same data as source",
  "status": "passed",
  "statusDetails": {},
  "stage": "finished",
  "steps": [],
  "attachments": [],
  "parameters": [],
  "labels": [
    {
      "name": "parentSuite",
      "value": "Store"
    },
    {
      "name": "suite",
      "value": "cloning"
    }
  ],
  "links": [],
  "start": 1586542591551,
  "name": "should provide a new store with the same data as source",
  "fullName": "Store cloning should provide a new store with the same data as source",
  "stop": 1586542592553
}

[sseliverstov]

@kirill-konshin what framework is it?

[kirill-konshin]

"jest": "25.1.0",
"allure-jasmine": "^2.0.0-beta.6",
"allure-js-commons": "^2.0.0-beta.6",

[vovsemenv]

Report structure in testops is different. You can change structure to be the same as in Allure report by creating custom Tree

more info here https://docs.qameta.io/allure-testops/briefly/test-cases/trees/