Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Testing Process Part 1 Draft 2 Comments"
(→Jonathan West) |
(→Paul Slauenwhite) |
||
Line 23: | Line 23: | ||
--[[User:Jgwest.ca.ibm.com|Jgwest.ca.ibm.com]] 11:59, 29 November 2007 (EST) | --[[User:Jgwest.ca.ibm.com|Jgwest.ca.ibm.com]] 11:59, 29 November 2007 (EST) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Paul Slauenwhite == | == Paul Slauenwhite == |
Revision as of 16:10, 29 November 2007
Jonathan West
Here are my section 5 comments, as requested:
BTW, 5.1 section has a typo, should read the 'JVMPI tests' rather than the 'JVMTI' tests.
5.2 JVMTI Profiler Test Suites:
Like the JVMPI Profiler tests, the JVMTI profiler tests are run like regular JUnit tests, but require manual configuration of a local configuration file. Unlike the JVMPI tests, it is not required to install a test server on the remote machine, or to edit remote configuration files, as these functions are now fully integrated into the local test installation.
5.3 Platform.Communication.Control.Channel.Test automated test:
The control channel tests are run like a regular jUnit test, with test execution being fully automated. The jUnit test will connect to the remote hosts being tested, configure the environment, run the test, and compare the results from the hosts. Presently, z/OS on zSeries and AS400 are not supported. Execution results must still be generated manually.
'5.4 Platform.Communication.Request.Peer.Monitor automated test
While request peer monitoring is still a manual test, it is a tool-assisted manual test, meaning that through automation of installation, configuration, and execution, the total test run time is reduced by about 80% versus a fully-manual run. Execution results must still be generated manually. z/OS on zSeries and AS400 are not supported.
--Jgwest.ca.ibm.com 11:59, 29 November 2007 (EST)
Paul Slauenwhite
- We need to document the BVT process:
- The root-level test suites for BVTs.
- The test infrastructure will execute the
org.eclipse.hyades.tests/AllBVT<test type>Tests.testsuite
test suites. - We do not need to check-in the execution results to CVS due to disk space limitations and polluting of our test pass results.
- Each developer can rerun the automated tests to reproduce a failure.