****Week 2**** This week, I finished setting up Ring project for launching my tests:
- I deleted some old video tests because they crashed when I build them. - I modified my test/sip/Makefile.am to allow the inclusion of all Ring files (by using globals.mk) - Add the “ring” namespace in the test files. CppUnit is set up too, we can easily add some tests to the test suite in the test_SIP.h file and they will automatically be build by typing the make check command line. I began to try to build the different tests: - testSimpleOutgoingIpCall, testTwoOutgoingIpCall and testHoldIpCall build but failed to pass the tests. The tests failed to create an outgoing call by using manager. - testSIPURI and testParseDisplayName failed to build because of the modifications made on sip_utils - testSimpleIncomingIpCall, testTwoIncomingIpCall and testIncomingIpCallSdp failed to build due to the modification of SIPVoIPLink The actual patch: https://gerrit-ring.savoirfairelinux.com/#/c/6972/7 For the next week, I will try to make my sip test work. To do that, I will begin by the tests who actually build. After that, I will try to adapt the other tests with the new SIPVoIPLink and sip_utils files. On 9 June 2017 at 18:05, Gregoire Olivier <[email protected]> wrote: > The coding phase of the Google Summer of Code has officially begun on may > 30. > > Now, I will write an article every week on what I have done. > > I hope you’ll like it! > > > > ****Week 1**** > > The first phase of my GSoC, is to make some tests on the sip part. Some > code has been done a long time ago for doing that. It has been removed > because he didn’t work with the actual ring (you can found it here: > https://gerrit-ring.savoirfairelinux.com/#/c/6972/2 ). I will use it to > retrieve some ideas. For example, it uses SIPp to test the sip protocol and > I think it’s a really good idea. > > > > But, for this first coding week, my principal difficulty was to use > autotools. The files configure.ac and Makefile.am can be difficult to > understand when you work on it for the first time. I begin to understand, > how all this work and I pushed a patch where the build work for my “test” > folder https://gerrit-ring.savoirfairelinux.com/#/c/6972/3 . We can > create our Makefile.in and Makefile files by using autogen and configure > script. > > > > For the next week, I will finish to understanding how autotools work on > Ring project. The goal is to do the tests when we write “make check”. Once > it will be done, I will begin to work with SIPp. > > > On 9 May 2017 at 15:17, Olivier GREGOIRE <[email protected]> wrote: > >> Hello, >> I am Olivier Grégoire (you can find me on IRC with the name Gasuleg). I'm >> a Canadian student from École de Technologie Supérieure but I will be in >> the French time zone during all the summer long. I will work for GNU on the >> Ring project. >> >> Ring is, at the moment, unstable due to a lack of automated tests. Only a >> part of the code is tested. I Need to improve this. >> To do that, I need to: >> - Reimplement some unit tests to check the components of the SIP pure >> account. >> - Research and test automation strategies that integrate the >> compilation system and Jenkins verification. >> - Write more unit tests for the critical functions in order to increase >> the code coverage. >> (You can found out my full proposal here >> <https://github.com/Gasuleg/proposal-GNU/blob/master/proposalGNU.pdf> for >> more information) >> >> I am very happy to work with you, >> Olivier Grégoire >> > > > > -- > Cordialement / Best regards > > *Olivier Grégoire* > *Technologie de l'Information - Information Technology* > > Tel. : +1 (514)-710-3142 <(514)%20710-3142> > <[email protected]> > <https://ca.linkedin.com/in/gregoireolivier> <https://github.com/Gasuleg> > <https://gasuleg.github.io/> > -- Cordialement / Best regards *Olivier Grégoire* *Technologie de l'Information - Information Technology* Tel. : +1 (514)-710-3142 <[email protected]> <https://ca.linkedin.com/in/gregoireolivier> <https://github.com/Gasuleg> <https://gasuleg.github.io/>
