On Thu, 2019-03-21 at 13:29 -0600, Logan Gunthorpe wrote:
On 2019-03-21 1:13 p.m., Knut Omang wrote:
> > Nevertheless, I don't really see KTF as a real unit testing framework
> > for a number of different reasons; you pointed out some below, but I
> > think the main one being that it requires booting a real kernel on
> > actual hardware;
> That depends on what you want to test. If you need hardware (or simulated or
> emulated hardware) for the test, of course you would need to have that
> but if, lets say, you just wanted to run tests like the skbuff example tests
> (see link above) you wouldn't need anything more than what you need to run
I'm starting to get the same impression: KTF isn't unit testing. When we
are saying "unit tests" we are specifying exactly what we want to test:
small sections of code in isolation. So by definition you should not
need hardware for this.
In my world hardware is just that: a piece of code. It can be in many forms, but
it is still code to be tested, and code that can be changed (but sometimes at a
slightly higher cost than a recompile ;-)
But that's not the point here: KTF can be used for your narrower definition of
unit tests, and it can be used for small, precise tests, for particular bugs for
instance, that you would not characterize as a unit test, still it serves the
same purpose, and I believe in a pragmatic approach to this. We want to maximize
the value of our time. I believe there's a sweet point wrt return on investment
on the scale from purist unit testing to just writing code and test with
existing applications. We're targeting that ;-)
> I have fulfilled that dream, so I know it is possible
> kernels from 2.6.39 to 4.8.x or so..) I know a lot of projects would benefit
> from support for such workflows, but that's not really the point here - we
> to achieve both goals!
This is what makes me think we are not talking about testing the same
things. We are not talking about end to end testing of entire drivers
but smaller sections of code.
No! I am talking about testing units within a driver, or within any kernel
component. I am sure you agree that what constitutes a unit depend on what
level of abstraction you are looking at.
A unit test is far more granular and
despite an infinband driver existing for 2.6.39 through 4.8, the
internal implementation could be drastically different. But unit tests
would be testing internal details which could be very different version
to version and has to evolve with the implementation.
> If your target component under test can be built as a kernel
module, or set
> modules, with KTF your workflow would not involve booting at all (unless you
> happened to crash the system with one of your tests, that is :) )
> You would just unload your module under test and the test module, recompile
> two and insmod again. My work current work cycle on this is just a few
Yes, I'm sure we've all done that many a time but it's really beside the
point. Kunit offers a much nicer method for running a lot of unit tests
on existing code.
Again, use cases and examples are the key here,..