Skip to main content
Jump to: navigation, search

Difference between revisions of "OSEE/OTE/Users Guide/Getting Started"

(New page: Future Category:OSEE)
 
(Updated URL links)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Future
+
=Overview=
 +
 
 +
The OSEE Test Environment (OTE) provides a framework for the testing of complex software systems. The test environment manages models, messages, remote communication, and logging.
 +
 
 +
Environments provide the core configuration of the tests, there is generally a 1 to 1 mapping between environments and labs. Generally, tests are written which set input and check output against the unit under test. These tests are sent to the Test Environment which then will coordinate with the unit under test to run the submitted test, or set the requested input.
 +
 
 +
These outputs can be imported into the OSEE Disposition tool for multi-run disposition of the test failures.  And the OSEE Continuous Integration tool can accept changes, launch builds, run test scripts and report to common location for analysis.
 +
 
 +
The OSEE Coverage tool can take instrumented test output and determine Level A, B and C coverage throughout multiple runs.
 +
 
 +
=Related Documentation=
 +
 
 +
For overviews, tutorials, examples, guides, and tool documentation, please see:
 +
 
 +
Refer to the OSEE Team generated information included in the eclipse help subsystem.
 +
 
 +
[https://www.oracle.com/technetwork/java/langenv-140151.html White Paper - The Java Language Enviornment]
 +
 
 +
[https://docs.oracle.com/javase/tutorial/java/index.html Trail - Learning The Java Language]
 +
 
 +
[https://www.oracle.com/technetwork/java/javase/tech/index-137868.html How to Write Doc Comments]
  
 
[[Category:OSEE]]
 
[[Category:OSEE]]

Latest revision as of 13:34, 6 September 2019

Overview

The OSEE Test Environment (OTE) provides a framework for the testing of complex software systems. The test environment manages models, messages, remote communication, and logging.

Environments provide the core configuration of the tests, there is generally a 1 to 1 mapping between environments and labs. Generally, tests are written which set input and check output against the unit under test. These tests are sent to the Test Environment which then will coordinate with the unit under test to run the submitted test, or set the requested input.

These outputs can be imported into the OSEE Disposition tool for multi-run disposition of the test failures. And the OSEE Continuous Integration tool can accept changes, launch builds, run test scripts and report to common location for analysis.

The OSEE Coverage tool can take instrumented test output and determine Level A, B and C coverage throughout multiple runs.

Related Documentation

For overviews, tutorials, examples, guides, and tool documentation, please see:

Refer to the OSEE Team generated information included in the eclipse help subsystem.

White Paper - The Java Language Enviornment

Trail - Learning The Java Language

How to Write Doc Comments

Back to the top