directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Resolved: (DIRSNICKERS-61) A Snickers Testing Framework
Date Sat, 03 Dec 2005 15:00:31 GMT
     [ ]
Emmanuel Lecharny resolved DIRSNICKERS-61:

    Resolution: Fixed

We have a way to store encoded and decoded PDU as XML in the sandbox project Ldap Proxy.

So we can perfectly replay PDU easily. (even if some more work is to be done, this is going
in the good direction)

> A Snickers Testing Framework
> ----------------------------
>          Key: DIRSNICKERS-61
>          URL:
>      Project: Directory ASN1
>         Type: Wish
>   Components: General
>     Reporter: Alex Karasulu
>     Assignee: Wes McKean

> At the present moment the only thing really holding us in the incubator is the dependency
on SNACC4J.  Right now we don't really need to depend on it if we had a testing framework
in hand where static serialized PDU's with known values can be tested with Snickers.  Even
when Snickers is fully functional a testing framework will still be required.  We can't keep
SNACC4J lying around even if it is just there to test for correct Snickers operation.
> To solve this problem we can create a special test case data file.  These test cases
can contain a serialized copy of the Java object representing the Message and a copy of the
encoded PDU.  Bi-directional transformations can be performed and verified to test decoders
and encoders this way.  All that is needed is a utility for generating these test case data
files.  An extention to JUnit can be written to test correct encoding and decoding to and
from the target objects.  These tests can also be used test the performance of encoders and
> We could create a simple XML based test case data file that contains base64 encoded raw
data elements like so:
> <snickers-testcase>
>   <id>12345</id>
>   <object>[base64encoded]</object>
>   <pdu>[base64encoded]</pdu>
> </snickers-testcase>
> The base64 encoded data can even be split into separate lines to keep the file sort of
human readable.  We can build a UI to generate these files that uses SNACC4J and the project
can reside on  Once we have the set of test case data files we need snickers never
needs to look back at SNACC4J.  

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message