[Chandler-dev] generating test data
bkirsch at osafoundation.org
Thu Apr 12 16:16:31 PDT 2007
>> - Should we tweak mail addresses to use test accounts? (looking to
>> Brian Kirsch here)
So to make sure I have this correct. You are advocating replacing
real user email addresses
with the OSAF demo account email addresses when generating /
obfuscating the test data.
+1 I don't see an issue with this. We do need to be careful with
in general though since they are used by our CATS testing framework
On Apr 11, 2007, at 11:29 AM, Aparna Kadakia wrote:
> +1 on using the same test data for both Desktop and Server
> Also we could use our test accounts demo1, demo2 etc for email
> addresses in case we cannot replace it with some junk.
> (bkirsch, can you confirm....in case you missed there is a question
> waiting for your confirmation at the end of this email)
> On Apr 10, 2007, at 3:28 PM, Katie Capps Parlante wrote:
>> As the desktop team turns attention to performance, we're
>> revisiting the
>> test data set that we've been using for performance metrics.
>> I'm not sure if we ought to coordinate desktop and server team
>> wrt test data -- sending this to both teams in case this turns out
>> to be
>> the case.
>> Previously, we generated a set of calendar data and have stored
>> that in
>> an ics file (tools/cats/datafiles/Generated3000.ics). The size of the
>> calendar and some of the characteristics were based on Mitch's
>> at the time.
>> We're now at a point where we'd like to have a data set that is
>> - based on real users' data
>> - contains multiple collections
>> - contains tasks, notes, messages in addition to calendar data (a
>> set that reflects the Preview feature set)
>> Instead of storing test data in .ics files, it makes sense to use our
>> new eim-based format. We'd like to start out with real user data,
>> obfuscate the data to protect the innocent.
>> Morgen has checked in a tool that allows us to obfuscate a "dump"
>> from the desktop app. (Thanks Morgen!)
>> From Morgen:
>>> So yesterday I checked in Tools > Save and Restore > Obfuscated dump
>>> to file...
>>> It sets an obfuscation attribute to True on the translator object,
>>> and then the various exporter callbacks honor its setting, instead
>>> emitting X's for the appropriate fields, and skipping a bunch of
>>> types such as accounts and passwords altogether. The one thing I'm
>>> not sure about obfuscating is the mail item and all its various
>>> fields. Does it matter if email addresses are included in these
>>> dumps? If so, someone will have to go and tweak export_mail( ) in
>>> translator.py to obfuscate the appropriate fields.
>> So from here:
>> - Can we make use of this tool or data for server performance
>> efforts? If so, any next actions?
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>> Open Source Applications Foundation "chandler-dev" mailing list
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Open Source Applications Foundation "chandler-dev" mailing list
More information about the chandler-dev