[Chandler-dev] generating test data: osaf test accounts instead of example.com accounts

Katie Capps Parlante capps at osafoundation.org
Mon Apr 23 17:45:18 PDT 2007


Presumably, if we wanted to replace them with test accounts instead, 
we'd change this code in translator.py:

>      @eim.exporter(pim.MailStamp)
>      def export_mail(self, mail):
> +        # Move to a local variable for a slight performance increase
> +        obf = self.obfuscation
> +
> +        def format(ea):
> +            if obf:
> +                return u"%s at example.com" % ea.itsUUID
> +
> +            return ea.format()
> +

to use the OSAF test account names.

Cheers,
Katie

Morgen Sagen wrote:
> 
> On Apr 23, 2007, at 3:02 PM, Philippe Bossut wrote:
> 
>> Hi,
>>
>> Aparna Kadakia wrote:
>>> Since Brian Kirsch has confirmed that we can replace the real 
>>> accounts with test accounts, what are the next action items on this?
>>> I would like to solicit help from external users for providing their 
>>> real calendars for testing. Having this tool obfuscate real data will 
>>> encourage more people to share their calendars for testing.
>>
>> AFAIK, this has been fixed by bkirsch last week and committed to svn:
>>
>>    r13993 | bkirsch | 2007-04-17 13:45:43 -1000 (Tue, 17 Apr 2007)
>>
>> Is there anything else missing?
> 
> Technically, when doing an obfuscated dump (Tools > Save and Restore > 
> Obfuscated dump to file...) real email accounts are being replaced by 
> <random-long-uuid>@example.com, and not "test" accounts.  This appears 
> to be working fine.
> 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> 
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev



More information about the chandler-dev mailing list