directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (DIRSNICKERS-61) A Snickers Testing Framework
Date Wed, 02 Jun 2004 17:40:53 GMT
The following comment has been added to this issue:

     Author: Wes McKean
    Created: Wed, 2 Jun 2004 10:39 AM
I have quite a number of serialized PDUs that I created while I was doing some proof of concept
stuff for NIO streams.  I'll track these down and come up with a testing framework for SNICKERs.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: DIRSNICKERS-61
    Summary: A Snickers Testing Framework
       Type: Wish

     Status: Open
   Priority: Major

    Project: Directory Snickers

   Assignee: Alex Karasulu
   Reporter: Alex Karasulu

    Created: Fri, 28 May 2004 11:50 PM
    Updated: Wed, 2 Jun 2004 10:39 AM
    Due:     Sun, 1 Aug 2004 12:00 AM

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 decoders. 

We could create a simple XML based test case data file that contains base64 encoded raw data
elements like so:


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:

If you want more information on JIRA, or have a bug to report see:

View raw message