Skip to content
This repository has been archived by the owner on Nov 8, 2024. It is now read-only.

More meaningful test names in report #430

Open
lippea opened this issue Mar 30, 2016 · 4 comments
Open

More meaningful test names in report #430

lippea opened this issue Mar 30, 2016 · 4 comments

Comments

@lippea
Copy link

lippea commented Mar 30, 2016

I have some cases feeding into one url with different data.

This ends entries as below in default report:
pass: POST /endpoint duration: 206ms
pass: POST /endpoint duration: 182ms
pass: POST /endpoint duration: 77ms
pass: POST /endpoint duration: 71ms

In my CI tool with junit report, it's like this:
OK (4 runs) POST /endpoint

I'm wondering is there anyway to use transition path as test names. Thanks!

@honzajavorek
Copy link
Contributor

Hi, that's a good point. I'll ask @netmilk about pointers on how we could improve this. Feel free to use --reporter=apiary as a workaround for better debugging (you don't need Apiary account for that).

@lippea
Copy link
Author

lippea commented Apr 1, 2016

Hi @honzajavorek Thanks! I have used beforeEach hook to print the name before every case for a debugging, but it doesn't help with CI build report. I'll try -reporter=apiary as well.

@honzajavorek
Copy link
Contributor

@lippea That is also a nice work around suggestion, thanks! 🎈

@beyourselfman
Copy link

Hi all,

I am also using hooks, like this:

beforeEach(function (transaction) {    
    transaction.id = getRequestNameFromId(transaction);    
});
function getRequestNameFromId(transaction) {
    return transaction.origin["actionName"] + "_" + transaction.expected["statusCode"];
}

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants