You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be possible to set up continuous integration/automated unit tests for any pushes to the repo. Here's my idea:
Write a series of unit tests on the firmware.
Set up a testing server with an attached PSoC and a Flask app that handles incoming and outgoing requests.
Set up a webhook that sends a payload to the Flask app when a push on the repo is initialized.
On receiving the payload, have the Flask app download the corresponding .cyacd file corresponding to the push.
Use cyflash or a similar utility to flash the .cyacd file to an attached PSoC over serial.
Run the unit tests on the PSoC (let's assume that the tests write to an influxdb database).
Use Kapacitor to capture the database writes and send the result back to the Flask app
Evaluate which tests have passed (e.g. maxbotix_depth must be within range 0-9998, etc.).
I'm not sure how Travis CI does it, but we could also display the results of the test on any pending pull requests in order to ensure that incoming pull requests won't break the master branch.
The text was updated successfully, but these errors were encountered:
It should be possible to set up continuous integration/automated unit tests for any pushes to the repo. Here's my idea:
I'm not sure how Travis CI does it, but we could also display the results of the test on any pending pull requests in order to ensure that incoming pull requests won't break the master branch.
The text was updated successfully, but these errors were encountered: