link to testing guides (smoke tests) for JEE package; rename and convert from md to adoc for the JS test doc; add names so we know who's doing the testing / maintaining the docs
Change-Id: I33665787cee0f1305387195da36c6b3052e4ef6e
Signed-off-by: nickboldt <nboldt@redhat.com>
diff --git a/packages/org.eclipse.epp.package.javascript.tests/README_Testing.adoc b/packages/org.eclipse.epp.package.javascript.tests/README_Testing.adoc
new file mode 100644
index 0000000..5e2c5c0
--- /dev/null
+++ b/packages/org.eclipse.epp.package.javascript.tests/README_Testing.adoc
@@ -0,0 +1,53 @@
+= Testing the Java EE Developers package
+
+Running manual tests is very expensive. The test cases below should be considered for automation!
+
+NOTE: TODO: Automate tests
+
+Any failure to those test cases should be reported to the Eclipse.org project causing the error, and to the link:https://accounts.eclipse.org/mailing-list/epp-dev[EPP mailing-list].
+
+There is room for improvement in these test cases (more test cases, more detailed steps). Feel free to contribute!
+
+
+== How to test the Eclipse IDE for Javascript Developers package
+
+
+=== Startup
+
+. Startup package on a new workspace
+. Check: error log doesn't report issue
+
+=== New Static Web Project enables HTML, CSS and JS
+
+. Create a new Static Web Project
+. Create/Open an HTML file => Check completion, highlighting and other features are enabled
+. Create/Open an CSS file => Check completion, highlighting and other features are enabled
+. Create/Open an JS file => Check completion, highlighting and other features are enabled
+
+=== Import an existing JS project
+
+. File > Open Projects from Filesystem... Pick a JS project such as mathjs (on GitHub), proceed
+. Check: Project has the JavaScript nature and right content
+
+=== Editing JS
+
+. From the mathjs project above, pick an interesting .js file
+. Check: syntax highlighting, completion... are enabled and work as expected
+
+=== Node/NPM actions
+
+. From the mathjs project above
+. Check: Run As actions are available on projet, package.json and work as expected
+
+=== Debug
+
+. From the mathjs project above
+. put a breakpoint, start debug
+. Check: breakpoint is hit, values are visibile, step into/over and debugger in general works
+
+
+---
+
+Process last documented by: link:mailto:mistria@redhat.com[Mickael Istria] & link:mailto:nboldt@redhat.com[Nick Boldt]
+
+Official Package Tester: link:mailto:ibuziuk@redhat.com[Ilya Buziuk]
diff --git a/packages/org.eclipse.epp.package.javascript.tests/TestCases.md b/packages/org.eclipse.epp.package.javascript.tests/TestCases.md
deleted file mode 100644
index 2a9f82b..0000000
--- a/packages/org.eclipse.epp.package.javascript.tests/TestCases.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# TODO: Automate tests
-
-Running manual tests is very expensive. The test cases below should be considered for automation!
-
-# Test Cases for JS EPP package
-
-Any failure to those test cases should be reported to EPP or other Eclipse.org project causing the error, and shared with EPP mailing-list.
-
-There is big room for improvements in these test-cases (more test-case, more detailed steps...). Feel free to contribute!
-
-## Startup
-
-. Startup package on a new workspace
-. Check: error log doesn't report issue
-
-## New Static Web Project enables HTML, CSS and JS
-
-. Create a new Static Web Project
-. Create/Open an HTML file => Check completion, highlighting and other features are enabled
-. Create/Open an CSS file => Check completion, highlighting and other features are enabled
-. Create/Open an JS file => Check completion, highlighting and other features are enabled
-
-## Import an existing JS project
-
-. File > Open Projects from Filesystem... Pick a JS project such as mathjs (on GitHub), proceed
-. Check: Project has the JavaScript nature and right content
-
-## Editing JS
-
-. From the mathjs project above, pick an interesting .js file
-. Check: syntax highlighting, completion... are enabled and work as expected
-
-## Node/NPM actions
-
-. From the mathjs project above
-. Check: Run As actions are available on projet, package.json and work as expected
-
-## Debug
-
-. From the mathjs project above
-. put a breakpoint, start debug
-. Check: breakpoint is hit, values are visibile, step into/over and debugger in general works
\ No newline at end of file
diff --git a/packages/org.eclipse.epp.package.jee.tests/README_Testing.adoc b/packages/org.eclipse.epp.package.jee.tests/README_Testing.adoc
new file mode 100644
index 0000000..3407fd4
--- /dev/null
+++ b/packages/org.eclipse.epp.package.jee.tests/README_Testing.adoc
@@ -0,0 +1,28 @@
+= Testing the Java EE Developers package
+
+Running manual tests is very expensive. The test cases below should be considered for automation!
+
+NOTE: TODO: Automate tests
+
+Any failure to those test cases should be reported to the Eclipse.org project causing the error, and to the link:https://accounts.eclipse.org/mailing-list/epp-dev[EPP mailing-list].
+
+There is room for improvement in these test cases (more test cases, more detailed steps). Feel free to contribute!
+
+
+== How to test the Eclipse IDE for Java EE Developers package
+
+
+. See https://wiki.eclipse.org/J2EE_Smoke_Tests[J2EE Smoke Tests]
+
+. Next, perform manual checks of general layout, preferences.
+
+. Finally, check for changes from integrated features like m2e, oomph, etc.
+
+Note: TODO: add more details here!
+
+
+---
+
+Process last documented by: link:mailto:cbridgha@us.ibm.com[Chuck Bridgham] & link:mailto:nboldt@redhat.com[Nick Boldt]
+
+Official Package Tester: link:mailto:cbridgha@us.ibm.com[Chuck Bridgham]
