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

[Question] Snaphots not visible in AWS console #83

Open
fvisticot opened this issue Dec 11, 2019 · 2 comments
Open

[Question] Snaphots not visible in AWS console #83

fvisticot opened this issue Dec 11, 2019 · 2 comments
Labels
question Further information is requested

Comments

@fvisticot
Copy link

I would like to see the snaphot files I'm taking from the test using the method:
where path is the filename without any directory before.

Is there a specific path to specify to see the snapthot files in the AWS console ?

Future<void> _takeScreenshot(FlutterDriver driver, String path) async { final List<int> pixels = await driver.screenshot(); final File file = new File(path); await file.writeAsBytes(pixels); print(path); }

@mmcc007
Copy link
Owner

mmcc007 commented Dec 11, 2019

That's listed as an enhancement in #22. Also checkout https://github.com/mmcc007/screenshots which should run faster.

@mmcc007
Copy link
Owner

mmcc007 commented Jan 16, 2020

When #22 is implemented, you would have to deposit your artifacts in a known directory. Will probably add a config for this. May provide a helper function for writing to the artifacts dir from tests. Not clear at this point. Otherwise would have to handle in your tests.

In the meantime, Device Farm has a 'default' artifacts directory that you can write to, that might work. Try writing your artifacts to $DEVICEFARM_LOG_DIR.

Let me know how it goes.

@mmcc007 mmcc007 added the question Further information is requested label Jan 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants