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

Property allure.results.useTestStorage doesn't seem to work #70

Open
1 of 3 tasks
vrnvorona opened this issue Apr 8, 2022 · 4 comments
Open
1 of 3 tasks

Property allure.results.useTestStorage doesn't seem to work #70

vrnvorona opened this issue Apr 8, 2022 · 4 comments

Comments

@vrnvorona
Copy link

I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

Currently setting allure.results.useTestStorage=true doesn't change how app under test saves report.
By that I mean that report is still in /data/data/package/files folder, not in /sdcard. allure.results.directory works as expected, changes folder name just fine.
I use latest atm 2.3.1 version and can't find traces of this property in it, while readme tells me to use this property if I use orchestrator. Seems like it's not yet merged into release.

Allure version 2.3.1
Test framework [email protected], no idea about junit
Allure integration [email protected]
testRunner AllureAndroidJUnitRunner
@Mishkun
Copy link

Mishkun commented Apr 15, 2022

It seems like pull-request with this feature was merged and not yet published as a new version

@Mishkun
Copy link

Mishkun commented Apr 18, 2022

@vrnvorona New release just published, try using that

@vrnvorona
Copy link
Author

@Mishkun It seems it's not yet on maven repository. When it hits I will surely try.

@vrnvorona
Copy link
Author

@vrnvorona New release just published, try using that

Works like a charm now, thanks for release 🚀

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

No branches or pull requests

2 participants