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
Create a Testing Lab #479
Comments
15 tasks
Hmmm, a testing lab platform:
Regarding the continuous-"build" stack:
|
This was referenced Apr 29, 2018
Hmmm, you could run Jenkins JNLP slave on the EV3 or other board. |
This was referenced Nov 4, 2018
Added Testing lab: Network:
Bricks:
|
Using this infrastructure, it is possible to improve the testing for the project in this iteration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem to solve:
Problem description:
The project continue adding process to increase the quality of the deliverables but at the end of the process, one human has to ensure that the library run on the devices. One interesting idea could be have a physical installation with:
From the Small computer a Jenkins job could be launched once the system detect a new event from the SCM and in that moment, Jenkins send a set of physical tests to run on the device.
Similar ideas:
https://codelabs.developers.google.com/codelabs/cloud-test-lab/index.html?index=..%2F..%2Findex#0
http://www.datacenterdynamics.com/content-tracks/design-build/facebook-runs-massive-mobile-test-lab-in-prineville-data-center/96594.fullarticle
Inventory:
The text was updated successfully, but these errors were encountered: