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

Create a Testing Lab #479

Closed
4 tasks done
jabrena opened this issue Apr 15, 2018 · 6 comments
Closed
4 tasks done

Create a Testing Lab #479

jabrena opened this issue Apr 15, 2018 · 6 comments

Comments

@jabrena
Copy link
Member

jabrena commented Apr 15, 2018

Problem to solve:

  • Accelerate release certification process.

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:

  • Small computer (Save energy) with Jenkins installed
  • EV3 Brick with a Operating system to certificate + Sensors/Actuators connected

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:

  • EV3 Brick with Debian Jessie installed
  • EV3 Brick with Debian Stretch installed (Snapshot)
  • 2x USB 2.0 hub
  • 2x Wifi Dongle
@JakubVanek
Copy link
Contributor

Hmmm, a testing lab platform:

  • the EV3 testing platform could boot off a USB flash drive (maybe only as a bootloader?). That would flash the SD card with new ev3dev images and install java and the testing tools.

Regarding the continuous-"build" stack:

  • OS: we don't touch that, we'd just download the latest snapshot.
  • JVM: it could be built using some more powerful SBC, maybe ODROID HC2. Travis might be sufficient.
  • Library: that could be handled using ODROID too. Travis might be sufficient.

@jabrena
Copy link
Member Author

jabrena commented Apr 29, 2018

@jabrena jabrena self-assigned this May 1, 2018
@jabrena
Copy link
Member Author

jabrena commented May 7, 2018

@jabrena jabrena modified the milestone: v0.9.0 Aug 3, 2018
@JakubVanek
Copy link
Contributor

JakubVanek commented Aug 21, 2018

Hmmm, you could run Jenkins JNLP slave on the EV3 or other board.

@jabrena
Copy link
Member Author

jabrena commented Nov 24, 2018

Added Testing lab:

Network:

  • Domestic Router
  • 4x Ethernet cable
  • 2x USB Ethernet adapter for EV3

Bricks:

  • EV3 + EV3Dev Debian Jessie
  • EV3 + EV3Dev Debian Stretch
  • BrickPi+ Raspberry Pi 3 | Raspberry Pi 3 Model B+
  • BrickPi3 + Raspberry Pi 3
  • PiStorms v2 + RaspberryPi 2

@jabrena
Copy link
Member Author

jabrena commented Nov 24, 2018

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
Projects
None yet
Development

No branches or pull requests

2 participants