> > hi, > > > > http://ltp.sourceforge.net/ > > > > "The Linux™ Test Project is a joint project started by SGI™ and > > maintained by IBM®, that has a goal to deliver test suites to the open > > source community that validate the reliability, robustness, and > > stability of Linux. The LTP testsuite contains a collection of tools for > > testing the Linux kernel and related features." > > ----------- > > > > In the week leading upto 6.4, Christoph Galuschka and I had started > > looking at how we might be able to integrate those tests into what we > > are doing. Since the 6.4 sprint kicked in, we resorted to just running > > the tests manually; Which worked well. However, I feel its worth putting > > these tests into the harness we have in place, and making sure they are > > run whenever we call for 'distro tests' or 'update tests'. > > > > One option is to have the entire suite run as a single tests/r_ltp/ > > suiet under t_functional; the other is to either have its own suite, we > > can directly import from upstream, or have it be a part of the > > t_external/ test suite ( along with the likes of wordpress / drupal and > > other things ). > > > > Thoughts ? > > > > - KB > I would suggest to let LTP have its own (= t_external) suite. I think it would get less udpates than t_functional (and wouldn't need a testrun every time t_functional gets a new test), and running the LTP-tests within t_functional would increase the time needed by about 30 mins. cheers Christoph -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20130314/94c6b2a1/attachment-0007.html>