You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by ji...@apache.org on 2004/05/29 08:52:00 UTC
[jira] Created: (DIRSNICKERS-61) A Snickers Testing Framework
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/DIRSNICKERS-61
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DIRSNICKERS-61
Summary: A Snickers Testing Framework
Type: Wish
Status: Open
Priority: Major
Project: Directory Snickers
Components:
General
Assignee: Alex Karasulu
Reporter: Alex Karasulu
Created: Fri, 28 May 2004 11:50 PM
Updated: Fri, 28 May 2004 11:50 PM
Due: Sun, 1 Aug 2004 12:00 AM
Description:
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:
<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 SF.net. Once we have the set of test case data files we need snickers never needs to look back at SNACC4J.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (DIRSNICKERS-61) A Snickers Testing Framework
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Alex Karasulu
Created: Sun, 30 May 2004 6:59 PM
Body:
It might be better to not serialize the Java Objects since they might change and break tests. Perhaps we should just use XML to represent the parameters of the LDAP message. We could make up our own or just use DSML if its still used. Last I looked DSML was in trouble. Basically instead of serializing an BindRequestImpl object in the ldap/common API we would just store it like so:
<BindRequest>
<version>3</version>
<name>uid=akarasulu,dc=example,dc=com</name>
<simple>password</simple>
</BindRequest>
Or whatever the XML is to represent the request object rather than serialize it.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/DIRSNICKERS-61?page=comments#action_35826
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/DIRSNICKERS-61
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DIRSNICKERS-61
Summary: A Snickers Testing Framework
Type: Wish
Status: Open
Priority: Major
Project: Directory Snickers
Components:
General
Assignee: Alex Karasulu
Reporter: Alex Karasulu
Created: Fri, 28 May 2004 11:50 PM
Updated: Sun, 30 May 2004 6:59 PM
Due: Sun, 1 Aug 2004 12:00 AM
Description:
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:
<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 SF.net. Once we have the set of test case data files we need snickers never needs to look back at SNACC4J.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (DIRSNICKERS-61) A Snickers Testing Framework
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Wes McKean
Created: Wed, 2 Jun 2004 10:39 AM
Body:
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:
http://issues.apache.org/jira/browse/DIRSNICKERS-61?page=comments#action_35874
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/DIRSNICKERS-61
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DIRSNICKERS-61
Summary: A Snickers Testing Framework
Type: Wish
Status: Open
Priority: Major
Project: Directory Snickers
Components:
General
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
Description:
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:
<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 SF.net. Once we have the set of test case data files we need snickers never needs to look back at SNACC4J.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (DIRSNICKERS-61) A Snickers Testing Framework
Posted by di...@incubator.apache.org.
Message:
The following issue has been re-assigned.
Assignee: Wes McKean (mailto:wmckean@logictrends.com)
Assigner: Alex Karasulu (mailto:aok123@bellsouth.net)
Date: Thu, 29 Jul 2004 6:58 PM
Comment:
Hopefully Wes you'll take care of this one.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/DIRSNICKERS-61
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DIRSNICKERS-61
Summary: A Snickers Testing Framework
Type: Wish
Status: Open
Priority: Major
Project: Directory Snickers
Components:
General
Assignee: Wes McKean
Reporter: Alex Karasulu
Created: Fri, 28 May 2004 11:50 PM
Updated: Thu, 29 Jul 2004 6:58 PM
Due: Sun, 1 Aug 2004 12:00 AM
Description:
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:
<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 SF.net. Once we have the set of test case data files we need snickers never needs to look back at SNACC4J.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira