Hi Olivier,
I think that it is great that we clean up all the old codes and have them
revive. I believe that your suggestion makes sense and as long as we can have
the consistent testing directory structures, there would be no arguments on
this.
Regards,
--
- DongInn
On Nov 27, 2013, at 5:30 AM, LAHAYE Olivier <olivier.lah...@cea.fr> wrote:
>
> Hi,
>
> I'm currently working on step 8 (test_cluster), and I've discovered that
> there are 3 testing cases/environments.
>
> 1/ /usr/share/oscar/testing/ (test_cluster, ssh_user_tests, unit_testing, ...)
> This is the main test structure. test_cluster runs all the other tests
>
> 2/ /var/lib/oscar/testing/<pkgname>/{test_user,test_root}
> These are the tests for installed opkgs.
>
> 3/ apitest.
>
> ===> Many tests are obsolete (don't work with current versions of software or
> distro)
> ===> Many tests are not reliable (passes once, but fail after).
> ===> test_root tests are not ran (test_cluster).
> ===> Fixing this is difficult and duplicate work: fix old script then later
> migrate to apitest...
>
> Aside that, the location of tests are in many different places that are not
> consistent and also not LSB compliant. For example, some tests are located in
> /var/lib/oscar/testing while other are located in /usr/share/oscar/testing.
> /var should only contains data, not "static" software (LSB).
>
> Also, we have tests in /usr/share. those tests are a kind of library and
> should be better placed in /usr/lib/oscar/testing (or something similar).
>
> IMHO, for a clean structure, we should have:
> /usr/lib/oscar/testing/ => all oscar testing scripts and files (one
> single place)
> /usr/lib/oscar/packages/ => api-{pre,post}-*, configurator.xml and such
>
> /usr/share/oscar/images (no change)
> /usr/share/oscar/oscarsamples (no change)
> /usr/share/oscar/prereqs (no change)
>
> /var/lib/oscar/cache/ (no change)
>
> Thus, IMHO, cleaning up the directory structures, and fixing testing (easy to
> fix directory changes (scripts+packaging)) will help a lot in fixing the test
> scripts and port to apitest.
>
> What is your opinion about that?
>
> Best regards,
>
> Olivier.
> --
> Olivier LAHAYE
> CEA DRT/LIST
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk_______________________________________________
> Oscar-devel mailing list
> Oscar-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oscar-devel
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel
