terrypacker,
excuse me for the delay. It was a busy time the last few weeks and I am now evaluating internally whether we are at the same stage we were when I first posted here...
Thanks for the link, I will be watching this branch.
terrypacker,
excuse me for the delay. It was a busy time the last few weeks and I am now evaluating internally whether we are at the same stage we were when I first posted here...
Thanks for the link, I will be watching this branch.
Sadly, we are tied to the legacy M2M architecture (Mango M2M v. 1.2.4). Are you familiar with it? I have had just a cursory look into the current Mango Automation code so I do not know which parts changed substantially / which parts stayed the same sufficiently. I am sure they diverged quite a bit... Do you think it would be feasible to start on a common subset of the code if there is any? I could think of Spring Testing framework (v. 1.2.4 uses Spring 2.5.3 IIRC) as a start for the Spring parts that did not change(?).
My priority would be to write tests that faciliate new data source implementations, e.g. event based data sources could be checked with a controlled timer in terms of data point setting. Also, to have known system states (i.e. data bases), I thought of using http://dbunit.sourceforge.net.
I will be on holidays the next week so in case you think this is worthwile, let me know and I will check back.
I am interested in working with you. Do you want to discuss things right here or via PM?
FWIW, I bump this since we are in a similar situation.