The probe tests are internal whole-system type of tests that test functionality never exposed through normal integration testing. They exist at the level between unit tests and functional tests. For example, one of the probetests makes sure that asynchronous container updates actually happen. Unit tests aren't concerned with this sort of internal system integration test, and functional tests only test external functionality. The probe tests ensure that the interaction between the different swift processes are still functioning as expected.
At least that's the idea. If they are broken in master right now, then that shows how little they are checked. Unless the other swift core devs feel differently, I think they should probably be fixed up. --John On Jun 26, 2012, at 4:21 PM, Jay Pipes wrote: > Not that I know of. > > Best, > -jay > > On 06/26/2012 04:54 PM, Maru Newby wrote: >> Have I missed a response in the past week? >> >> >> On 2012-06-19, at 12:14 PM, Jay Pipes wrote: >> >>> On 06/19/2012 11:10 AM, Maru Newby wrote: >>>> The swift probetests are broken: >>>> >>>> https://bugs.launchpad.net/swift/+bug/1014931 >>>> >>>> Does the swift team intend to maintain probetests going forward? Given >>>> how broken they are at present (bad imports, failures even when imports >>>> are fixed), it would appear that probetests are not gating commits. That >>>> should probably change if the tests are to be maintainable. >>> >>> Hi Maru, cc'ing Jose from the Swift QA team at Rackspace... >>> >>> I don't know what the status is on these probetests or whether they are >>> being maintained. Jose or John, any ideas? If they are useful, we could >>> bring them into the module initialization of the Tempest Swift tests. >>> >>> Best, >>> jay >> >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
