I recently got pulled into a rabbit hole when I read an article about the PiDP8i project. I didn't have the money to get the real thing so this post will chronicle my experiences setting up a similar experience using the blinkenbone project instead.
While going through Appendix C I quickly ran into trouble with the mocky Unit test for the new list view when I converted it to a class based view. the following is a description of how I made it work.
Jenkins runs it's build shell scripts with /bin/sh -xe which means any command that runs tests that has failing tests will abort the entire build and you likely won't see the JUnit reports for your entire test suite.
I've come up with some simple shell functions that will allow all of our test commands to run and then still allow the build to still fail like it's supposed to when we are ready for it.
I recently grabbed an old VGA flatscreen monitor (HP 2011x) third hand to use as a second display.
Right out of the gate I had a problem: Under Ubuntu 16.04LTS KDE would not see it as anything other than a 1024x768 monitor Even though it supports 1600x900. After some playing around I think I have a way to manage things that makes sense for me under KDE.
You can ...
This article describes my Jenkins setup for going through the book Test-Driven Development with Python
We will discuss the following steps: