OK so I just did something really stupid and I'm looking for help.
I opened my roof, unparked the scope and slew to a target. It was still twilight so I thought While waiting I'll do apt-get upgrade....
Now I cant restart indi services.
I'm getting this error from the celestron driver. Unfortunately this leaves me with a scope pointing up, a roof open and a possible 1hr drive....
2016-06-03T21:26:44: Driver indi_celestron_gps: snooping on GPS Simulator.TIME_UTC
2016-06-03T21:26:44: Driver indi_celestron_gps: XML error: Line 17: No value for attribute On
2016-06-03T21:26:44: Driver indi_celestron_gps: XML read: <?xml version='1.0'?>
<defSwitchVector
device='Celestron GPS'
name='TELESCOPE_BAUD_RATE'
label='Baud Rate'
group='Options'
state='Idle'
perm='rw'
rule='OneOfMany'
timeout='60'
timestamp='2016-06-03T21:26:44'
>
<defSwitch
name='9600'
On
</defSwitch>
<defSwitch
name='19200'
Off
</defSwitch>
<defSwitch
name='38400'
Off
</defSwitch>
<defSwitch
name='57600'
Off
</defSwitch>
<defSwitch
name='115200'
Off
</defSwitch>
<defSwitch
name='230400'
Off
</defSwitch>
</defSwitchVector>
<?xml version='1.0'?>
<defSwitchVector
device='Celestron GPS'
name='Hibernate'
group='Options'
state='Idle'
perm='rw'
rule='OneOfMany'
timeout='0'
timestamp='2016-06-03T21:26:44'
>
<defSwitch
name='Enable'
Off
</defSwitch>
<defSwitch
name='Disable'
On
</defSwitch>
</defSwitchVector>
2016-06-03T21:26:44: Driver indi_celestron_gps: Terminated after #10 restarts.
Sorry about that, my mistake, I really need to add autotests to the build. Will start to work on that once I have some free time. A new libindi is going to be built soon, will be available in an hour.
No problem, I wonder if I could somehow help with testing / test automation. My day to day job is in Java development so I have decent experience with unit/integration testing and continuous integration. I have no clue where to start with c++ unit testing though. Also testing drivers is tricky as its difficult to mock the hardware layer.
If you ever do get around to adding some unit tests let me know and maybe I can use them as an example to write more.
Derek
There is the
Google C++ Testing Framework
. I'm thinking of using that unless someone has better alternatives. You can discover a lot of issues from the simulators alone. That's why we have them, to test stuff.