Re: How to properly write tests for kernel functions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Nov 05, 2015 at 12:26:01AM +0300, Maxim Pugachev wrote:
> Hi all,
> 
> I'm trying to understand is there any uniform way to write tests? For
> example, lib/ folder has a bunch of tests, but all of them use various
> technics:
> 
> - pr_warn/pr_err (i.e. printk) or WARN for assertions
> - just tens of functions that check something, or unified macros
> - no naming convention for test cases
> 
> So, I'm wondering, whether there is an example or guidelines that is
> worth to follow.

It all depends on what you want to test.  There is no "general" way to
do this as all subsystems / parts of the kernel are different.

thanks,

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux