Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Metadata for scenario added for json report #1368

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

justyna-olszak-wttech
Copy link

Project I use BackstopJS in required an option to pass some metadata for each scenario into the final JSON output, to be used by other monitoring tools. The solution is covered in this fork.
Such use case is for example JIRA ticket number. It allows to have additonal information next to tested pair for easier project maintenance and stories reference.

I believe it is valuable addiont, that can be used also by other teams. @garris

Copy link
Owner

@garris garris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for this PR. I don't think this is something I would want to add to the code base -- but it looks very interesting-- it would probably be more useful to others as a blog post if you can show more about how you will use the metadata in your project. If you create a post I am happy to add the link to the readme doc. Cheers!

@@ -9,7 +9,7 @@ ENV \
RUN apt-get update && \
apt-get install -y git sudo software-properties-common

RUN sudo npm install -g --unsafe-perm=true --allow-root backstopjs@${BACKSTOPJS_VERSION}
RUN sudo npm install -g --unsafe-perm=true --allow-root https://github.com/justyna-olszak-wttech/BackstopJS.git
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately we want to stay away from loading private libraries like this.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I was pretty sure it will not meet acceptance, but this was necessary to make fork use my code within Docker build.
Therefore I'll stay with this fork trying to pass JIRA ids to XRay reporting.

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

Successfully merging this pull request may close these issues.

None yet

2 participants