5 Commits (95d67d636fdfff822d24f3c07c81ce12c0b3c025)

Author	SHA1	Message	Date
Gerhard Jungwirth	aec9443940	MT#15269 add restapi tests to stable set ... Change-Id: I39a47539c932d35383b44dcfbfbffd909f97c7a1	10 years ago
Alexander Lutay	8ab155a672	MT#15269 Restore possibilit to trigger one/specific REST API test ... Also fix the exit code for failed test which gone during refactoring. Change-Id: I56702b1247aa7fd157cdd2b556f629fd937ca693	10 years ago
Alexander Lutay	496aea8de8	MT#15269 Add REST API test support of Jenkins runner ... Change-Id: Ifa0a871f3d4432eda5db08c5b0864d25af0fea60	10 years ago
Gerhard Jungwirth	45115f5d6e	MT#15269 fix some api tests, add test selection ... by choosing "stable" (about 1m30s) or "fast" (about 30s) as second argument of testrunner, only tests are run, which are currently succeeding on a plain trunk vm using docker. (times are on my machine) I hope we can in this way re-enable them on nightlies (or even in gerrit) so that devs have some better feedback on the impact of our changes. Current status of tests (in trunk): | Problems: | api-callforwards.t | api-balanceintervals.t | api-faxes.t | api-journals.t | | Fixed: | api-all-links.t | api-contracts.t | api-customercontacts.t | api-customers.t | api-rewriterulesets.t | api-root.t | | Working: | api-billingfees.t | api-billingnetworks.t | api-billingprofiles.t | api-billingzones.t | api-calllists.t | api-calls.t | api-cert-auth.t | api-cfdestinationsets.t | api-ncoslevels.t | api-pbxdevicemodels.t | api-pbxdevices.t | api-peeringgroups.t | api-peeringrules.t | api-peeringservers.t | api-preferences.t | api-profilepackages.t | api-resellers.t | api-rewriterules.t | api-soundsets.t | api-subscriberregistrations.t | api-subscribers.t | api-systemcontacts.t | api-threads.t | api-topuplogs.t | api-trustedsources.t | api-valid-patch.t | api-vouchers.t Change-Id: I74e672d9dc6bcccfd3ace2fe233dbcf325c6fc4d	10 years ago
Michael Prokop	968ed762e6	MT#15071 Docker setup for api-rest tests ... For usage instructions please look at the bottom of the Dockerfile, usage similar to what we already have for the docker selenium tests. Known problems: 1) In t/api-rest/api-journals.t there's a failure, though all the tests actually seem to run fine then: | encountered object 'true', but neither allow_blessed nor convert_blessed settings are enabled at /usr/share/perl5/JSON.pm line 154. | # Tests were run but no plan was declared and done_testing() was not seen. | # Looks like your test exited with 255 just after 1130. | [...] | t/api-rest/api-journals.t (Wstat: 65280 Tests: 1130 Failed: 0) | Non-zero exit status: 255 | Parse errors: No plan found in TAP output | Files=25, Tests=8363, 347 wallclock secs ( 1.14 usr 0.11 sys + 32.59 cusr 2.23 csys = 36.07 CPU) 2) Failures in t/api-rest/api-balanceintervals.t, might be caused by timing issues/rerunning them, needs investigation though: | t/api-rest/api-balanceintervals.t (Wstat: 65024 Tests: 1875 Failed: 318) | Failed tests: 51, 56-59, 62, 67, 70, 75-80, 83, 88, 108-109 | [...] Change-Id: I5d697cab4a1a4c6697857fc63c03b8d3fd8965d2	10 years ago