Bryntum Support Forums

Posted: **Wed Jun 20, 2018 6:57 pm**

Hello,

We create an HTML report after our automated tests in Jenkins. They tend to provide more context than the stack traces we get with the JUnit report.

However, one friction point we've noticed is that errors/failed assertions within nested it/describe blocks are often hidden from view, requiring the user to search through the assertion tree to find what went wrong.

Would it be possible for the UI to automatically expand to the error in the report?

Thanks,

Chauncey

Posted: **Mon Jun 25, 2018 10:19 am**

Hi,

Sure, we'll add this feature. Ticket created: https://app.assembla.com/spaces/bryntum ... rt/details

Posted: **Mon Jun 25, 2018 2:19 pm**

As a hot-fix, you can tweak the siesta-all.js file in this way:

Update

            var data            = {
                id                  : me.idGenSequence++,

                leaf                : !isSubTest,
                expanded            : expanded            : isSubTest && assertionNode.bddSpecType != 'it'
            }

to

            var data            = {
                id                  : me.idGenSequence++,

                leaf                : !isSubTest,
                expanded            : isSubTest && (assertionNode.bddSpecType != 'it' || !assertionNode.passed)
            }

Bryntum Support Forums

Expanding errors in HTML report

Expanding errors in HTML report

Re: Expanding errors in HTML report

Re: Expanding errors in HTML report