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

fix(ios): track hierarchy artifacts #4365

Merged
merged 1 commit into from
Feb 11, 2024
Merged

Conversation

noomorph
Copy link
Collaborator

Description

This pull request addresses absent UI hierarchy artifacts in our Allure reports.

It should be helpful for anyone who's using: https://github.com/wix-incubator/detox-allure2-adapter

Copy link
Collaborator

@d4vidi d4vidi left a comment

Choose a reason for hiding this comment

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

Approving even though this makes me wonder: Can artifact creation be made more seamlessly? Namely, improve the infra such that this would happen in a very fundamental place, where every artifact creation is reported as an event.

I know this might be a bit naive on my part, but I need to ask this.

@noomorph
Copy link
Collaborator Author

This is a mere fix, @d4vidi, not an attempt to reimagine the subsystem. I have a vision regarding the new iteration of artifacts, and it is based on making all artifact creating APIs public, plus a thin integration attaching to test runner lifecycle to call those API.

Anyways, here I just align the implementation with my initial API design in 2019. All artifacts undergo track/untrack, but it seems that I was a bit slack last time (the UI hierarchy is one of the last plugins we added), and simply forgot to add it.

We use tracking and untracking to make sure that artifacts get cleaned up even if the artifact plugin forgets to do that.

Allure integration just hops on trackArtifact to spy on artifact.doSave whenever an artifact is created. I hope that explains.

@noomorph noomorph merged commit b6aaf30 into master Feb 11, 2024
3 checks passed
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.

2 participants