Thank you for your feedback. I have emailed one of the maintainers Mark Vandervoord and he gave me some tips on how to improve my code. Once I make the changes he expressed interest in merging the code upstream. Once this is done I can start integrating the tool with rtems testing as mentioned I am planning to do. If you are interested the code is here https://github.com/marcinbujar/Unity . Currently there is no support for output buffering but I could add it if it is required.
Thanks, Marcin On 25 September 2013 01:05, Joel Sherrill <joel.sherr...@oarcorp.com> wrote: > Looking at the macros, it looks like some/all of the current test support > macros could be wrappers for Unity calls. > > Beyond that we need to look at some specific tests to see what other > things can be done based on patterns > > Also our tests can do printf, printk, or buffer a screen or so of output > and then print that at a more steady state time. > > --joel > > "Rempel, Cynthia" <cynt6...@vandals.uidaho.edu> wrote: > > > Hi Marcin, > > This looks interesting! How do I try out these changes? > > Could you tell us who the upstream maintainer is for Unity? > We may be able to get some feedback from him (and thus increase the > likelihood the changes will be upstreamed... :) > > Thanks! > Cindy > ________________________________________ > From: rtems-devel-boun...@rtems.org [rtems-devel-boun...@rtems.org] on > behalf of Marcin Bujar [marcin.bu...@gmail.com] > Sent: Monday, September 23, 2013 3:32 PM > To: rtems-devel@rtems.org > Subject: Re: [SOCIS] Testing Framework > > Hello all, > > > Another update on my SOCIS project. Last week I have been fixing bugs on > the modifications I have done to Unity to be used with the future RTEMS > testing framework. > > For those interested the changes I have made so far are here: > https://github.com/marcinbujar/Unity/compare/ThrowTheSwitch:master...master > > These additions to the unit testing tool will hopefully allow me work > towards higher automation of testing. > > This week I have been using the new waf build system to compile RTEMS so > that I can start using unity for testing. So far I am still working my way > through build errors but I am making steady progress. > > > Marcin > > > On 16 September 2013 21:53, Marcin Bujar <marcin.bu...@gmail.com<mailto: > marcin.bu...@gmail.com>> wrote: > > > > On 16 September 2013 12:31, Sebastian Huber < > sebastian.hu...@embedded-brains.de<mailto: > sebastian.hu...@embedded-brains.de>> wrote: > Hello Marcin, > > > On 2013-09-15 22:34, Marcin Bujar wrote: > Hi again, > > I would just like to update everybody that the work on my SOCIS project on > RTEMS testing framework is going well. This week I worked on adding new > features to the Unity unit testing tool, primarily adding JSON output > support > as mentioned in my previous update, but also looking how to compile the > program > on 16bit architecture so that it is executable on such RTEMS supported > platforms. > > it would be nice to know the work flow if I write tests for this new frame > work. Do I simply write C files according to the frame work requirements > and then run a script that generates the appropriate glue code? > > How are the RTEMS configurations provided for a particular test program? > > The plan is to have as much automation as possible, but we dont have all > the details yet. There will most likely be pre-generated skeleton test > files or templates to use to write new tests. This is the next step in my > project. I will post more information about this to ask for feedback once I > know more. > > > Next week I will be fixing any remaining issues with the output and also > implementing 16bit support for unity. Once complete this tool will > hopefully be > ready to use with RTEMS testing. > > Why does it matter for the test framework which word size an architecture > has? > > As far as I know Unity does not fully support some test functions specific > to 16bit, so my job is to make sure that it does. I will be investigating > this and other compatibility issues this week. > > -- > Sebastian Huber, embedded brains GmbH > > Address : Dornierstr. 4, D-82178 Puchheim, Germany > Phone : +49 89 189 47 41-16 > Fax : +49 89 189 47 41-09 > E-Mail : sebastian.hu...@embedded-brains.de<mailto: > sebastian.hu...@embedded-brains.de> > PGP : Public key available on request. > > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. > > _______________________________________________ > rtems-devel mailing list > rtems-devel@rtems.org<mailto:rtems-devel@rtems.org> > http://www.rtems.org/mailman/listinfo/rtems-devel > > > > And to answer the previous questions, I have forked Unity on github so any > features that I develop specifically for RTEMS can be pulled to the > upstream repository once they are ready and if the maintainers find it > useful. And finally I do not have a developer blog but I may actually > create one in the future! > > Thanks for the questions! > > Marcin > > > _______________________________________________ > rtems-devel mailing list > rtems-devel@rtems.org > http://www.rtems.org/mailman/listinfo/rtems-devel >
_______________________________________________ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel
