[Libstoragemgmt-devel] Should we ship plugin_test.py in rpm like 'libstoragemgmt-test'?

[Gris Ge]

Hi,

I am wondering whether we can ship plugin_test.py in rpm package like
'libstoragemgmt-test'.

QE could use it for auto-test.
Plugin dev could use it for pre-release/commit test.
These people use released version in stead of git tree. It seems not
good idea for them to keep a local git repo for plugin_test.py only.

If we are about to save it in /usr/bin, it could better if we change
it to more common name like 'lsm-pluing-test'.

Any thoughts?

Thank you.
Best regards.

[Tony Asleson]

Post by Gris Ge
Hi,
I am wondering whether we can ship plugin_test.py in rpm package like
'libstoragemgmt-test'.
QE could use it for auto-test.
Plugin dev could use it for pre-release/commit test.
These people use released version in stead of git tree. It seems not
good idea for them to keep a local git repo for plugin_test.py only.
If we are about to save it in /usr/bin, it could better if we change
it to more common name like 'lsm-pluing-test'.
Any thoughts?

I'm not really sure if I've seen any other projects ship test code in
the form of RPM's. My main concern would be for user to accidentally
run the test on a production server and destroy data. Not likely, but
possible.

Anyone else have thought on this?

Regards,
Tony

[MaShimiao]

Hi all,

IMHO, test code is used for checking whether we have a correct design.
And it helps us to provide trustworthy software to users.
It should be used by developers.
So, I think it's not necessary to ship test code in the form of RPM.

That's my own opinion.

Best Regards

Post by Tony Asleson

Post by Gris Ge
Hi,
I am wondering whether we can ship plugin_test.py in rpm package like
'libstoragemgmt-test'.
QE could use it for auto-test.
Plugin dev could use it for pre-release/commit test.
These people use released version in stead of git tree. It seems not
good idea for them to keep a local git repo for plugin_test.py only.
If we are about to save it in /usr/bin, it could better if we change
it to more common name like 'lsm-pluing-test'.
Any thoughts?

I'm not really sure if I've seen any other projects ship test code in
the form of RPM's. My main concern would be for user to accidentally
run the test on a production server and destroy data. Not likely, but
possible.
Anyone else have thought on this?
Regards,
Tony
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Libstoragemgmt-devel mailing list
https://lists.sourceforge.net/lists/listinfo/libstoragemgmt-devel

[Gris Ge]

Post by MaShimiao
Hi all,
IMHO, test code is used for checking whether we have a correct design.
And it helps us to provide trustworthy software to users.
It should be used by developers.
So, I think it's not necessary to ship test code in the form of RPM.
That's my own opinion.
Best Regards

Post by Tony Asleson

Post by Gris Ge
Hi,
I am wondering whether we can ship plugin_test.py in rpm package like
'libstoragemgmt-test'.
QE could use it for auto-test.
Plugin dev could use it for pre-release/commit test.
These people use released version in stead of git tree. It seems not
good idea for them to keep a local git repo for plugin_test.py only.
If we are about to save it in /usr/bin, it could better if we change
it to more common name like 'lsm-pluing-test'.
Any thoughts?

I'm not really sure if I've seen any other projects ship test code in
the form of RPM's. My main concern would be for user to accidentally
run the test on a production server and destroy data. Not likely, but
possible.
Anyone else have thought on this?
Regards,
Tony

Hi Tony and MaShimiao,
Thanks for the valuable input.

I will suggest them to use source rpm and use plugin_test.py there.

Best regards.