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

Add continuous integrated testing using Travis CI and PlatformIO #12

Merged
merged 2 commits into from Aug 10, 2016

Conversation

Projects
None yet
2 participants
@photodude
Contributor

photodude commented Aug 10, 2016

Add continuous integrated testing using Travis CI and PlatformIO. Requires signing up for the free service details can be found in the docs

This is a low-level continuous integrated testing the ensures the library functions and PR's are valid.
The low-level Testing verifies the library against the supplied example demo.ino

You can see the passing build with this link to my Travis CI branch which has been configured to test https://travis-ci.org/photodude/DualVNH5019MotorShieldMod3/builds/151091859

Currently, this only tests against 2 boards (uno and megaatmega2560) additional boards can be added for tested. (example with more boards https://travis-ci.org/photodude/DualVNH5019MotorShieldMod3/builds/151090810)

photodude added some commits Aug 10, 2016

Create .travis.yml
Add file necessary of continuous integrated testing using [Travis CI] and [PlatformIO](https://github.com/platformio/platformio).
Tests the library against the supplied example
Add Travis CI badge
Add badge to show build status

@ryantm ryantm merged commit f38ec94 into pololu:master Aug 10, 2016

@ryantm

This comment has been minimized.

Show comment
Hide comment
@ryantm

ryantm Aug 10, 2016

Member

Cool; thanks for the contribution!

Member

ryantm commented Aug 10, 2016

Cool; thanks for the contribution!

@photodude

This comment has been minimized.

Show comment
Hide comment
@photodude

photodude Aug 10, 2016

Contributor

You are welcome.

I've got an updated version that breaks the boards out individually and will allow failures for boards that support is in development for (or to just show that the boards don't work). See this example build https://travis-ci.org/photodude/DualVNH5019MotorShieldMod3/builds/151094125

If you want I can submit a new PR for that.

Contributor

photodude commented Aug 10, 2016

You are welcome.

I've got an updated version that breaks the boards out individually and will allow failures for boards that support is in development for (or to just show that the boards don't work). See this example build https://travis-ci.org/photodude/DualVNH5019MotorShieldMod3/builds/151094125

If you want I can submit a new PR for that.

@photodude photodude deleted the photodude:patch-3 branch Aug 10, 2016

@ryantm

This comment has been minimized.

Show comment
Hide comment
@ryantm
Member

ryantm commented Aug 10, 2016

@photodude

This comment has been minimized.

Show comment
Hide comment
@photodude

photodude Aug 11, 2016

Contributor

Those are some nice modifications and simplifications that @DavidEGrayson has made, I have incorporated those into my .travis.yml to make my version more portable for adding testing to my other projects.

Contributor

photodude commented Aug 11, 2016

Those are some nice modifications and simplifications that @DavidEGrayson has made, I have incorporated those into my .travis.yml to make my version more portable for adding testing to my other projects.

@ryantm

This comment has been minimized.

Show comment
Hide comment
@ryantm

ryantm Mar 13, 2017

Member

@photodude I mentioned you in the blog post I wrote about us using this in our Arduino libraries. By the way, we've updated the script on master to set some shell options so the script properly fails when the board compilations fail. Here is an example of the problem: https://travis-ci.org/pololu/balboa-32u4-arduino-library/builds/208827161

Member

ryantm commented Mar 13, 2017

@photodude I mentioned you in the blog post I wrote about us using this in our Arduino libraries. By the way, we've updated the script on master to set some shell options so the script properly fails when the board compilations fail. Here is an example of the problem: https://travis-ci.org/pololu/balboa-32u4-arduino-library/builds/208827161

@photodude

This comment has been minimized.

Show comment
Hide comment
@photodude

photodude Mar 14, 2017

Contributor

Thanks for the mention @ryantm glad the contribution was helpful. I'll definitely make that update for my scripts too.

Maybe someday actual unit testing of the arduino libraries can be added.

Contributor

photodude commented Mar 14, 2017

Thanks for the mention @ryantm glad the contribution was helpful. I'll definitely make that update for my scripts too.

Maybe someday actual unit testing of the arduino libraries can be added.

@photodude

This comment has been minimized.

Show comment
Hide comment
@photodude

photodude Mar 14, 2017

Contributor

@ryantm one correction on the blog post spelling, my last name is Sorensen. Not a big deal, it's a common difference of e vs o. Again, thanks for the mention in the blog post.

Contributor

photodude commented Mar 14, 2017

@ryantm one correction on the blog post spelling, my last name is Sorensen. Not a big deal, it's a common difference of e vs o. Again, thanks for the mention in the blog post.

@ryantm

This comment has been minimized.

Show comment
Hide comment
@ryantm

ryantm Mar 14, 2017

Member

@photodude Sorry! We fixed it!

Member

ryantm commented Mar 14, 2017

@photodude Sorry! We fixed it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment