* there is a catch when changing the admin password;
first of all, according to TT#76110 only own admin
users can change the password via PUT/PATCH;
secondly, inside the code, for PATCH to work we need
a dummy 'password' key on the old resource which has
been set to the saltedpass; when updating the admin,
if the password is still equal to saltedpass, no change
is made to the password
Change-Id: I423ebe13988c58b527db65d666f09b73a483422d
* According to TT#78557, webpassword is not returned at
GET request for subscriber so it's now manually added
in test from the content used at creation
Change-Id: I0835d7830bad31ad20451a758a5044e0f40015bf
Otherwise on jenkins in test 'ngcp-panel-test-rest-api-docker':
> not ok 57 - check for 'activesubscriberpreferences' collection in Link
> # Failed test 'check for 'activesubscriberpreferences' collection in Link'
> # at ./t/api-rest/api-root.t line 176.
Change-Id: Ic694f025291490e7c0415e8210180fdd8c6cfe1b
- Add 'enabled' column to the request content to
mitigate error that appeared after adding the
column
Change-Id: I5de3e52e7fab34c4bad8497630684f0d221f11e4
* Add the new fields to the Billing fees form
* Add the new fields to the csv order for
download and upload to work
* Change tests to include the new fees fields
Change-Id: If45bfe4f39ccd0283c72071489f5930eab2c37e9
* Change order of deleting subscribers to
delete other subscribers before the pilot
according to task 60965
Change-Id: Ic4f4ddb23876a470aba5398d48a7c3439167c117
* Kamailio location accepts location based on
ngcp_panel.conf: sip.usrloc_expires_type option,
that is taken from config.yml
kamilio.proxy.usrloc_expires_type.
* adjust api-subscriberregistrations.t to support
sip.usrloc_expires_type
Change-Id: Ia040c63ef2e0cc711812f4a4d17093ae753531aa
the client cert serial was taken from epoch time in secs.
if a computer is fast enough, there is the chance a
subsequent POST /admincert did not invalidate the old cert
properly (as expected by api-cert-auth.t), but created an
identical one.
Change-Id: Ifd906489029efd17df0997c5aceec3ac1db08fb1
XML files generated by prove will contain the time we spend in every
test case, it allows us profile our tests and fix the most slop parts.
Change-Id: I965af2d95f57d8975613da0f46ce8abf1be4c114
The main difficulty is that peeringserver has hardcoded reseller_id = 1 in the preferences update logic to check provided soundset ownership.
Peeringserver sound_set preference => should have reseller_id = 1
Subscribers & profiles sound_set preferences => should have appropriate to subscriber or profile reseller_id
It makes creation of the test data more sophisticated, specially considering that sound_set has both reseller_id and customer_id and they should be coordinated (customer should belong to the reseller)
Change-Id: Id7a299cb828144281f078c706ba7048ccfc58e82
PATCH "remove by value" will from now remove values even if provided hash has less keys, than original value
Change-Id: I2ee04fa279580d662e167c3a0b160fe29d8d79ef
name is unique per group in provisioning.voip_peer_hosts,
but not unique per group in kamailio.lcr_gw, that is filled after provisioning.voip_peer_hosts
by trigger voip_phost_urepl_trig
Change-Id: I005b97fc9b0aea84586ba23a57bcb070e5391ee0
Add test script for API
Fix DateTime create/update issue in TimeSets API (get2put case)
(add and edit functionlity used raw/inflated data respecively)
Add datetimepicker field
Change-Id: If724b7350658c306dbbecbc04309d1d1c0b4a3e2
Unify UI and API code to make subscriberadmin behavior with profile_set and profile common
Change alias_numbers input field to embedded RepeatableJS so it pass form validation
Change-Id: I1b3dc6f88cc6c1f43d76acc8e339dbb664c166a3
We have added new dependency in commit 2930237, but we also need to bump
Dockerfile version so Jenkins will rebuild docker container.
Change-Id: I1655af44d9e71c49473596a25e1cc9dbe617dbfa
* when fetching data from the journals tables
the start test time is used to filter out possible
existing records with the same resource ids
to address the mysql auto increment reset behaviour
Change-Id: Id048b97809628bbbcef9724ae0cf4eae39f7f0fa
one was actually a true positive. the others were false positives
and are going to be silenced for the time being, while we try to find
an upstream solution. more details can be found in the ticket.
Change-Id: Iae8df7606774a9d26e4d44dbba557c9fe62d2252
this is to fix the TAP tests of the sipwise QA chain
fixed (or ignored):
- ControlStructures::ProhibitMutatingListFunctions
- Documentation::RequirePodSections
- InputOutput::RequireEncodingWithUTF8Layer
- Subroutines::ProhibitSubroutinePrototypes
- BuiltinFunctions::ProhibitStringySplit
- TestingAndDebugging::ProhibitNoStrict
- TestingAndDebugging::ProhibitProlongedStrictureOverride
- InputOutput::ProhibitTwoArgOpen
- CodeLayout::ProhibitQuotedWordLists
Change-Id: I7dce4ce123bad40de2d9b51ba5b1a141e20c3783
* enables fetching captured sip data
GET all collection returns JSON with available SIP messages
GET item collection requires a valid call-id and
returns pcap data generated from the packets of the call-id
Change-Id: I552ee9a312a4b9acf95bde93f6c584bbf82f9ea9
this is to clean the Sipwise TAP tests for this repo
the critical places where undef is really the intended return value (because
a scalar should always be returned) the rule has been overridden
Change-Id: I66e217a03a00e0f366db9c0cbc5007dd15cd9f96
Fake_data keeps own test_machine, and when we change user
using runas in other test_machine instance - we need to
reinit cert files before request.
Change-Id: Idddeef2b0c10521c71ce5d77c5010f89c620185c