| 1 | | = Welcome to Trac 0.12.3 = |
| 2 | | |
| 3 | | Trac is a '''minimalistic''' approach to '''web-based''' management of |
| 4 | | '''software projects'''. Its goal is to simplify effective tracking and handling of software issues, enhancements and overall progress. |
| 5 | | |
| 6 | | All aspects of Trac have been designed with the single goal to |
| 7 | | '''help developers write great software''' while '''staying out of the way''' |
| 8 | | and imposing as little as possible on a team's established process and |
| 9 | | culture. |
| 10 | | |
| 11 | | As all Wiki pages, this page is editable, this means that you can |
| 12 | | modify the contents of this page simply by using your |
| 13 | | web-browser. Simply click on the "Edit this page" link at the bottom |
| 14 | | of the page. WikiFormatting will give you a detailed description of |
| 15 | | available Wiki formatting commands. |
| 16 | | |
| 17 | | "[wiki:TracAdmin trac-admin] ''yourenvdir'' initenv" created |
| 18 | | a new Trac environment, containing a default set of wiki pages and some sample |
| 19 | | data. This newly created environment also contains |
| 20 | | [wiki:TracGuide documentation] to help you get started with your project. |
| 21 | | |
| 22 | | You can use [wiki:TracAdmin trac-admin] to configure |
| 23 | | [http://trac.edgewall.org/ Trac] to better fit your project, especially in |
| 24 | | regard to ''components'', ''versions'' and ''milestones''. |
| 25 | | |
| 26 | | |
| 27 | | TracGuide is a good place to start. |
| 28 | | |
| 29 | | Enjoy! [[BR]] |
| 30 | | ''The Trac Team'' |
| 31 | | |
| 32 | | == Starting Points == |
| 33 | | |
| 34 | | * TracGuide -- Built-in Documentation |
| 35 | | * [http://trac.edgewall.org/ The Trac project] -- Trac Open Source Project |
| 36 | | * [http://trac.edgewall.org/wiki/TracFaq Trac FAQ] -- Frequently Asked Questions |
| 37 | | * TracSupport -- Trac Support |
| 38 | | |
| 39 | | For a complete list of local wiki pages, see TitleIndex. |
| | 1 | A CO Tester checks a software component for basic conformity with CAPE-OPEN standards. A CO Tester prepares a report which enables any developer to assess the compliance of a piece of software with the CO interface specifications. |
| | 2 | A CO Tester acts as a basic simulation environment where software components can be plugged in. It is designed to automatically carry out a number of scenarios. First, A CO Tester checks for the existence of the required CO interfaces within the tested software. This constitutes the Basic test. Then each method of each interface is tested on its arguments (existence and type), and on its functionality. This constitutes the Function test. Any developer is also able to run self-designed tests through the Integration test part, where the developer defines the test scenarios. |
