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

How to publish my test results? #3

Open
pmarcinkiew opened this issue Jul 7, 2017 · 4 comments
Open

How to publish my test results? #3

pmarcinkiew opened this issue Jul 7, 2017 · 4 comments

Comments

@pmarcinkiew
Copy link

I would like to publish my test results for Tizen RT IoT.js here but I see that you overwrite history here at daily basis.

How should I publish my test results here?

@pmarcinkiew
Copy link
Author

It will be nice to write this in README.md. I can create short guide but please first explain this flow.

@yichoi
Copy link

yichoi commented Jul 10, 2017

cc @rtakacs

@LaszloLango
Copy link
Contributor

@pmarcinkiew check https://github.com/rtakacs/remote-testrunner first. I think you need to use that tool.

rtakacs added a commit that referenced this issue Aug 22, 2017
Add missing dependencies to build IoT.js for Raspberry PI2
@rtakacs
Copy link
Contributor

rtakacs commented Aug 31, 2017

Note that I've removed the https://github.com/rtakacs/remote-testrunner repository, because the code is moved to this repository.

To publish all the results, the driver.py should be started with --public flag that can be found in the README.md file. Need to mention that the publish requires a serviceAccountKey.json named file in the root folder. This file can be downloaded from the firebase admin interface and holds all the required permissions to modify the database. Since the currently used firebase account is created by our team, just we can modify the database.

First, we should decide how we store the test results. Together, under the same firebase account, or separately, so you could have an other firebase account with an own database. In the latter case the webpage should be modified to read test results from the appropriate database.

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

4 participants