This is an automated email from the ASF dual-hosted git repository.

jgallimore pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomee-tck.git


The following commit(s) were added to refs/heads/master by this push:
     new 3943495  Added about_tck.adoc and updated REAME.adoc
     new b25fb24  Merge pull request #8 from 
cesarhernandezgt/update-readme-tck-structure
3943495 is described below

commit 3943495dbe9c347c924b7e572de9331577353fcc
Author: CesarHernandezGt <cfhernan...@gmail.com>
AuthorDate: Thu Jan 31 16:27:10 2019 -0600

    Added about_tck.adoc and updated REAME.adoc
---
 README.adoc    | 28 ++++++++++++++++++++++++++++
 about_tck.adoc | 37 +++++++++++++++++++++++++++++++++++++
 2 files changed, 65 insertions(+)

diff --git a/README.adoc b/README.adoc
index 00ec265..d6ce764 100644
--- a/README.adoc
+++ b/README.adoc
@@ -177,6 +177,34 @@ to delete the "#java" part and then it will work.
 
    ./runtests --web tomee-plume 
com/sun/ts/tests/ejb30/lite/stateful/concurrency/accesstimeout/annotated/Client#beanClassLevel_from_ejbembed
 
+## TEST DEBUG
+
+The following are the flags the scrip `runtests` accept for debuggin purposes:
+
+
+    -d,--debug              Enable Server and TCK appclient debug options 
(5005 and 5003)
+    -de,--debug-embedded    Enable TCK embedded ejb debug options (port 5001)
+    -dh,--debug-harness     Enable TCK harness debug options (port 5002)
+    -da,--debug-appclient   Enable TCK appclient debug options (port 5003)
+    -dj,--debug-javatest    Enable TCK javatest debug options (port 5004)
+    -ds,--debug-server      Enable Server debug options (port 5005)
+    --connector             deploy connectors for connector tests
+
+You can attach to the ports via your IDE remote debugger options.
+Example:
+
+    ./runtests --web tomee-plume -c -d 
com.sun.ts.tests.ejb30.lite.stateful.concurrency.accesstimeout.annotated.Client#beanClassLevel_from_ejbembed
+
+Depending on the IDE, you will need to attempt twice to connect to the exposed 
port.
+
+## WHAT TO TEST
+
+The test that needs to be tested are the one having the following `keywords`:
+
+    javaee_web_profile, ejb_web_profile, jacc_web_profile, jaspic_web_profile, 
javamail_web_profile, jaxr_web_profile, xa_web_profile, jaxrpc_web_profile, 
jaxws_web_profile
+
+For more information about TCK structure and tests attributes check the 
link:about_tck{outfilesuffix}[about_tck] documentation.
+
 ## WHAT NEXT
 
 Getting from zero to passing is a long road.  Failures and the
diff --git a/about_tck.adoc b/about_tck.adoc
new file mode 100644
index 0000000..335891f
--- /dev/null
+++ b/about_tck.adoc
@@ -0,0 +1,37 @@
+# About JakartaEE TCK
+
+## CTS
+
+The JakartaEE Test Compatibility Kit (TCK) is conformed by a Compatibility 
Test Suite (CTS).
+
+CTS is a set of tools and tests used to verify that a licensee's 
implementation of Java EE 8 technology conforms to the applicable specification.
+
+Java EE 8 CTS includes version 5.0 of the JT harness.
+
+## Tests organization
+
+The JakartaEE TCK is conformed by a total of 47,219 tests that can be divided 
in two subset: one set for Web Profile and other for Full Profile.
+
+Each test has a set of attributes like id, keyword, testName, test_directory 
and classname among others.
+The `keyword` attribute can be used to differentiate the test that belong to a 
Web and/or Full Profile, and if they are optional base on the type of profile.
+
+The following are the `keywords` related with Web Profile:
+
+    javaee_web_profile, ejb_web_profile, jacc_web_profile, jaspic_web_profile, 
javamail_web_profile, jaxr_web_profile, xa_web_profile, jaxrpc_web_profile, 
jaxws_web_profile
+
+## JT Harness UI
+This is a useful UI tool that comes in handy when one needs to know if a 
specific test is or not part of a specific profile.
+
+## start JT Harness UI
+From the `$TCK_HOME` execute:
+
+    cd bin
+    ant gui
+
+The UI shows all the TCK test and you can navigate to an specific test and 
view the Test Description tab that contains the test attributes described above.
+
+
+
+
+
+

Reply via email to