Integration Tests - 2

Commits

• integration tests - get_encode_port: 80da75070f0c0c0d3c7a3f32e3a6350804a60984
• fixed problems in comparing lists: 749a3e35a9938a67d09734ec3d303ce49f7ea35c
• fixed problems in comparing lists: 00dfafe4f0999aa446d517d73027aed1e4f3ac96
• Added Integration tests for get_compose_port: 7c4e616dfa0ebb9eb65d09aeecc16458dac219a7
• establish_connection tests: e4ee184a72e8534854bbdb8105442edc66f178e3

Things completed -

• Integration tests for getting the current compose port of gst-switch. The compose port is returned as an integer when gst_compose_port method is called on the Controller. I observed that its value is one greater than the video_port paramater of the gst-switch-srv. So if the value of video_port is 3000, get_compose_port should return 3001. The tests are run for multiple values of video_port. For each of these ports, the get_compose-port method is called multiple times. For the test, I have two constants, NUM and FACTOR. These can be found here. NUM denotes the number of video_port (testcases) values that are taken. NUM*FACTOR is the number of times the get_compose_port method is called in each test case. After trying out multiple values of NUM and FACTOR, I found that after a product value of NUM*FACTOR greater than about 400, I get an exception - ConnectionError: unix:abstract=gstswitch (Could not connect: Connection refused).
• Integration test for getting current encode port. The encode port works the same as get_compose_port method. Here the encode port is generally 2 ports more than video_port. The test cases were made similar to get_compose_port.

Working on

The rest of the methods of gst-switch