ngcp-panel

Commit Graph

Author	SHA1	Message	Date
Alexander Lutay	5988b51589	TT#22351 Fix ca76144c4a: API test trustedsources is also failing in stretch Docker image Change-Id: Idd6bdeff16bb34fbd7ed5fc7a281baa80921ed2d	8 years ago
Alexander Lutay	ca76144c4a	TT#22351 Disable API tests which are currently broken with stretch Perl New Perl in stretch doesn't provide the method/hack to access variable, we were using. Ira is searching for the fix here, so far temporary disabling the tests, as the fix is not approaching this week. The commit must be reverted soonish. Change-Id: Ib0fd290c6749df361638405589e9e5df6248394a	8 years ago
Andreas Granig	f9030b4f21	TT#4333 subscribers/customers/numbers/CF ACL * Implement r/o access to /api/customers for subadmin * Implement r/o access to /api/subscribers for subs * Implement create access to /api/subscribers for subadmins * Implement /api/numbers to re-assign a number * Implement CF endpoints access for subs * Implement new test framework to simplify testing * Fix updating number by using Utils to make sure allowed_clis etc are handled correctly * Install missing docker dependencies for new test framework * Add edr handling on /api/numbers/xx update Change-Id: I678da16cfb1361b2809780cba8c204ac90bb1736	8 years ago
Alexander Lutay	cccc6a9a41	TT#17032 prove STDERR output is not a part of Jenkins's result XML Which confuses developers which are debugging failed tests, as details like below are not a part of XML Jenkins displays on a WEB: > # Failed test 'create test customer w/o profile package' > # at t/api-rest/api-balanceintervals.t line 1578. > # got: '500' > # expected: '201' > Use of uninitialized value in concatenation (.) or string at t/api-rest/api-balanceintervals.t line 1580. > Thread 4 terminated abnormally: malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "<!DOCTYPE HTML>\n<!-...") at /usr/share/perl5/JSON.pm line 171. 'man prove' says: > -m, --merge Merge test scripts' STDERR with their STDOUT. Change-Id: I945d4d8867fc9c061f96d067be14125af7cc5a46	8 years ago
Rene Krenn	cdd054ef78	TT#13973 enable method-override test seems it was only part of the "all" suite. Change-Id: Ie9b87fbe24994bd1d887efa7903898873a499cf1	8 years ago
Alexander Lutay	c81a20dcf9	TT#3648 Add REST APT tests bannedips/bannedusers to stable and fast test groups * I had to fix api-bannedusers.t otherwise it failed: > ok 19 - bannedusers: check if all created test items have been foundin the list > is_empty:1;ok 20 - fetch uri: https://10.15.20.74:1443/api/bannedusers/?page=1&rows=1 (OK: ) > $VAR1 = undef; > ok 21 - Check that all added banned users were deleted 1..21 Failed 1/21 subtests Change-Id: Ic9578c9f1ab20b2abeaa51656ed5556804228981	9 years ago
Andreas Granig	ff110dca96	TT#2766 Implement inbound peering rules API. Implement API calls Add to testrunner Run various tests on reject code/reason Change-Id: I2a2d2548de09089e41aa2830450a8eb72432b423	9 years ago
Alexander Lutay	6d35b85a6b	MT#22099 Docker >=1.11 no longer has /.dockerinit, adjust docker run check accordingly File /.dockerinit no longer exists. With Docker versions 1.11 and 1.12 there's /.dockerenv available, though it's not yet sure whether this will be present in the future too, so check for either /.dockerenv or a proper cgroup setup inside the docker container. File /proc/1/cgroup with Docker version 1.12.1 on Debian/jessie looks like: \| root@4c3a1c6d773c:/# cat /proc/1/cgroup \| 8:freezer:/docker/4c3a1c6d773c1a5675f24ff58540ff1a290489e7325e1e66ec2c3392aa3a1145 \| 7:perf_event:/docker/4c3a1c6d773c1a5675f24ff58540ff1a290489e7325e1e66ec2c3392aa3a1145 \| 6:net_cls,net_prio:/docker/4c3a1c6d773c1a5675f24ff58540ff1a290489e7325e1e66ec2c3392aa3a1145 \| 5:cpuset:/docker/4c3a1c6d773c1a5675f24ff58540ff1a290489e7325e1e66ec2c3392aa3a1145 \| 4:blkio:/docker/4c3a1c6d773c1a5675f24ff58540ff1a290489e7325e1e66ec2c3392aa3a1145 \| 3:cpu,cpuacct:/docker/4c3a1c6d773c1a5675f24ff58540ff1a290489e7325e1e66ec2c3392aa3a1145 \| 2:devices:/docker/4c3a1c6d773c1a5675f24ff58540ff1a290489e7325e1e66ec2c3392aa3a1145 \| 1:name=systemd:/docker/4c3a1c6d773c1a5675f24ff58540ff1a290489e7325e1e66ec2c3392aa3a1145 See https://github.com/docker/docker/issues/18355 and https://github.com/docker/docker/pull/19490 for details. Change-Id: I79fff0eead1a11f80b461791b2285a65d706262a	9 years ago
Gerhard Jungwirth	cf845a9f71	MT#15269 increase stable tests, small fixes * fix api-root * fix api-balanceintervals * fix warning in Test::Collection (typo) * add new tests to stable: balanceintervals, customers, faxes, lnp, root * add new test to fast: root Change-Id: I058b586c6f2e166106194038de233126715121e8	9 years ago
Gerhard Jungwirth	aec9443940	MT#15269 add restapi tests to stable set Change-Id: I39a47539c932d35383b44dcfbfbffd909f97c7a1	9 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	9 years ago
Alexander Lutay	496aea8de8	MT#15269 Add REST API test support of Jenkins runner Change-Id: Ifa0a871f3d4432eda5db08c5b0864d25af0fea60	9 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	9 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

14 Commits (a0b9e64e9a87b79a7360166d97fc0f56e1b209b7)