Adding topology hiding no dlg tests for new one way hiding and compac…#32
Adding topology hiding no dlg tests for new one way hiding and compac…#32davidtrihy-genesys wants to merge 4 commits into
Conversation
…t encoding feature
|
Some setup-related issues before things started working on my end: Bad mpathThis was necessary in order to match the standard mpath found in SIPssert's existing "opensips.cfg" test files and in the image builds. This way, the same image can be used to run all tests. NOTE: Unrelated segfault in topology-hiding-no-dlg-legacy/15.This is how I run legacy test 15., with a local-built OpenSIPS image after merging PR #3908: ... and perhaps it crashes 1/5 times, in what looks to be a shutdown crash: Just curious if you ever got this one -- we will look into it separately, it looks to be TCP related. Anyway, I spent some time today getting the SIPssert corefile generation working properly while running the tests, fixed ulimit issues, directories, mounts, permissions, etc. before the cores started being preserved after the container is destroyed. I will push the corefile preservation patch to upstream Apart from this, all legacy tests are passing on my end as well, at a first glance. More feedback to come, of course, on the actual SIP signaling. And finally, on the |
|
We use a different module path so yeah sorry about that, before I commit any changes I'll change it to the default one, we're actually using jinja templating and we are forking sipssert to add new functionality and push it back upstream if we think it's valuable so we'll probably explicitly add that soon so these scripts come from a jinja template so I could template in a module path with the default in it. The 19 tests you ran are a subset of the other suite which has two additional tests, I'm actually going to add a new one based on one of the bugs from the main PR I fixed around checking buffer bounds. One additional thing is I AI generated some scenario markdown files which explain the scenario and they're actually decently descriptive, I can remove them or leave them, entirely up to you, just added them in the PR for you to be able to read them and get an understanding of the tests and what explicitly I am testing. |
|
@liviuchircu I added a new suite that does some validation of malicious input it is test 22 in the non legacy suite, I couldn't get the csv values working correctly with sipssert so I just unrolled the suite into a single xml file and it runs 14 different transactions verifying different assumptions, these are based off the feedback in the PR around the buffer boundary checking when decoding, the thinfo is precomputed with the default password, would be nice to make it dynamic moving forward, in fact I think adding support to the management interface to execute the decoding logic would be cool moving forward but for now I think just hardcoding is fine to verify. So let me know what you think of the tests and whether to keep the scenario.md files and we can move forward from that. Forgot to answer that question about the crash I have not seen that crash happen to me which is quite strange. |
1629cc7 to
ead120e
Compare
Tests for this feature OpenSIPS/opensips#3908
I added AI generated scenario details in each test directory to give an easier understanding of what the scenario is asserting, we can remove that commit before merging or keep it.