Hi Zoli,
your approach sounds not bad. If we need to go one step further we could
a) build a static library from the object files in src and
b) link against it.
It has the nice point that we can override every function from the
library with our own stubs (e.g. in your mentioned global.c)
Hi Tom,
I have checked your approach. I think the following combination of both
could work
- one test harness like my run.c + the (generated, if poss) test defs
- global data (mostly from src/main.c) in a global.c
- functions that use network/hamlib/curses mocked/wrapped in global.c
Hi Zoli,
I just pushed my own 'tests' branch which I mentioned yesterday to
https://github.com/dl1jbe/tlf/tree/tests
I uses cmocka-1.1.1 as test framework. It needs to be installed by hand
before, as I did not integrate the check for it into configure.ac
until now.
Maybe we can integrate
Tom, cloned your repo and Travis CI works quite well.
I'll try to add a CUnit test as per docs. Not all of Tlf
can be tested that way, but let's see how far we can get.
The .astylerc you shared looks OK to me.
(yes, I meant indent of 4 spaces)
73,
Zoli
On Fri, Jan 26, 2018 at 02:42:41PM +0100,
Sorry for being not quite clear in my last mail.
Am Fri, 26 Jan 2018 10:25:16 +0100
schrieb Ervin Hegedüs :
> Hi Thomas,
>
> On Thu, Jan 25, 2018 at 07:31:00PM +0100, Thomas Beierlein wrote:
> > Hi all,
> >
> > just for testing I set up a copy of TLF's code at
> >
Hi Thomas,
On Thu, Jan 25, 2018 at 07:31:00PM +0100, Thomas Beierlein wrote:
> Hi all,
>
> just for testing I set up a copy of TLF's code at
> https://github.com/dl1jbe/test-travis .
>
> Atm it has a very simple setup: configure and build TLF without hamlib
> support. You can check it out,
Hi all,
just for testing I set up a copy of TLF's code at
https://github.com/dl1jbe/test-travis .
Atm it has a very simple setup: configure and build TLF without hamlib
support. You can check it out, provide a pull request and see
what happens.
73, de Tom
--
"Do what is needful!"
Ursula