Expanding errors in HTML report

Get help with testing, discuss unit testing strategies etc.


Post Reply
User avatar
chauncey-garrett
Posts: 38
Joined: Fri Oct 21, 2016 6:26 pm

Expanding errors in HTML report

Post by chauncey-garrett »

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

User avatar
nickolay
Core Developer
Core Developer
Posts: 3447
Joined: Mon May 16, 2011 10:48 am

Re: Expanding errors in HTML report

Post by nickolay »

Hi,

Sure, we'll add this feature. Ticket created: https://app.assembla.com/spaces/bryntum ... rt/details
We offer training in both Ext JS and our products, read more here.
Read the API documentation

User avatar
nickolay
Core Developer
Core Developer
Posts: 3447
Joined: Mon May 16, 2011 10:48 am

Re: Expanding errors in HTML report

Post by nickolay »

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

Update

Code: Select all

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

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

Code: Select all

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

                leaf                : !isSubTest,
                expanded            : isSubTest && (assertionNode.bddSpecType != 'it' || !assertionNode.passed)
            }
We offer training in both Ext JS and our products, read more here.
Read the API documentation

Post Reply