Abstract
This document specifies the test cases that were used for testing privacy filtering and implementation of presence privacy policies in the presence server.By default, the assumption is the presentity is someone@example.com and watcher is user@example.com . Any exceptions are specified in the test case description.
Testing Process
Unit testing for each of the modules was done parallel to implementation. However, once all modules were ready, the process flow was tested as an independent system.Once integrated with the presence server, subscribe and publish requests were generated for various presentities and subscribers and with various policy documents and RPIDF documents, the rulematching, rule combination and filtering was tested. Also, subscription authorizations were also tested under various conditions.
Test Cases
TEST CASE 1
DESCRIPTION
This test provides a case where occurences of device-id, activities, sphere and mood are allowed to be present in the document while the rest are removed.
COMPOSED RPIDF POLICY DOCUMENT FILTERED RPIDF
rpidf_input_1.xml input_filter_1.xml output_rpidf_1.xml
TEST CASE 2
DESCRIPTION
This test case has a policy which occurences of relationship,class and note elements are allowed while the rest would be removed.
COMPOSED RPIDF POLICY DOCUMENT FILTERED RPIDF
rpidf_input_2.xml input_filter_2.xml output_rpidf_2.xml
TEST CASE 3
DESCRIPTION
This test provides a case where the policy specifies all attributes and elements to be allowed for the watcher. The resulting output RPIDF would be the same as input RPIDF.
COMPOSED RPIDF POLICY DOCUMENT FILTERED RPIDF
rpidf_input_3.xml input_filter_3.xml output_rpidf_3.xml
TEST CASE 4
DESCRIPTION
This test case provides a policy wherein provide-privacy, provide-place-is, provide-status-icon, provide-timeoffset, provide-placetype permissions are true so the corresponding elements are allowed in the presence document but the rest are removed.
COMPOSED RPIDF POLICY DOCUMENT FILTERED RPIDF
rpidf_input_4.xml input_filter_4.xml output_rpidf_4.xml
TEST CASE 5
DESCRIPTION
This test case brings up a situation where class, relationship, activities, device-id,note elements are allowed to be present. However user-input element permission is bare i.e. this element has to be removed from the RPIDF.
COMPOSED RPIDF POLICY DOCUMENT FILTERED RPIDF
rpidf_input_5.xml input_filter_5.xml output_rpidf_5.xml
TEST CASE 6
DESCRIPTION
This test case is a variation of test case 5 with <provide-user-input> being thresholds. This means that the threshold attribute of user-input,if present is allowed, all other attributes are removed. There is <provide-note> which is explicitly set to false in this document which results in <note> getting removed for RPIDF
COMPOSED RPIDF POLICY DOCUMENT FILTERED RPIDF
rpidf_input_6.xml input_filter_6.xml output_rpidf_6.xml
TEST CASE 7
DESCRIPTION
This test case is a variation of test case 5 with <provide-user-input> being full. This means that the user-input element , if present is allowed with all its attributes.
COMPOSED RPIDF POLICY DOCUMENT FILTERED RPIDF
rpidf_input_7.xml input_filter_7.xml output_rpidf_7.xml
TEST CASE 8
DESCRIPTION
This test is a variation from all other previous testcases. This test concentrates matching on the identity condition and variations in subscription handling.In this policy document, it specifies that for any subscriber in the domain columbia.edu except sn2189@columbia.edu and for the subscriber user@example.com, the rule with id 1 applies and subscription handling is confirm.
POLICY DOCUMENT
TEST CASE 9
DESCRIPTION
This test combines all 3 conditions namely identity of the watcher, sphere and validity-period of the rule. This test concentrates on rule matching process.
In this sample policy document,the rule with id 1 applies to all subscribers except sn2189@columbia.edu and subscribers with domain yahoo.com. It holds good for the subscriber user@example.com. Moreover this rule holds good only when the presentity's sphere is bowling and this rule is valid from 2005-11-10 12:00+5:00 and 2005-11-10 15:00+5:00 .When this rule applies subscription handling is confirm.
POLICY DOCUMENT
TEST CASE 10
DESCRIPTION
This test concentrates on rule combination process when there are more than 1 rule that applies to a watcher depending on identity,sphere and date-time. It also demonstrates other forms of handling elements to test subscription handling and authorization for different subscribers of a given presentity If multiple rules match, then the maximum sub-handling value among all the matched rules is taken for subscription handling. For other entities, a logical BIT-OR is done for boolean values , maximum for integer values and unions for sets. The files below show some examples of such filters. It covers all basic entities of policy filtering. So, this case was thorougly experimented upon during testing.
COMPOSED RPIDF POLICY DOCUMENT FILTERED RPIDF
rpidf_input_10.xml input_filter_10.xml output_rpidf_10.xml
ANOTHER VARIATION