[
https://jira.jboss.org/jira/browse/DNA-455?page=com.atlassian.jira.plugin...
]
Brian Carothers commented on DNA-455:
-------------------------------------
I created this bug many moons ago before I understood what the TCK compat test looked
like. It turns out to be a web application that looks up a reference to your repository
in the JNDI tree. You then click a button to start the test. This would be fairly
painful to fully automate and would provide no gain over our current integration tests,
which run the exact same test cases and do so against a variety of repository
configurations.
Instead of writing a bunch of automated web-scripting code, I propose that we add a class
to the dna-jcr layer that allows access to our JCR repositories through JNDI. This would
make running the formal compatibility test require 5 steps:
1. Install a servlet container like Tomcat locally
2. Build DNA and copy the resulting JARs into the Tomcat lib directory
3. Modify the Tomcat context.xml to add the JNDI entry for DNA
4. Copy the TCK compatibility web app into the Tomcat deploy directory
5. Go to the test page and click the button to start the test.
Considering that we really only need to run this once, I think that's not too many
steps and it would add a deployment vector for DNA that could be reused.
Any thoughts?
Add Sub-Project to Execute Official TCK
---------------------------------------
Key: DNA-455
URL:
https://jira.jboss.org/jira/browse/DNA-455
Project: DNA
Issue Type: Sub-task
Components: JCR
Affects Versions: 0.5
Reporter: Brian Carothers
Fix For: 0.7
JSR-170 compliance is achieved when all tests in the official TCK are passed. This TCK
is distinct from (but related to) the "unofficial" JackRabbit TCK that DNA
currently runs each night. In order to achieve full compliance(and make sure that future
changes don't break it), an automated means of executing the official TCK (and passing
or failing based on the results) should be added.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira