# File Types and Extensions

```{index} single: files ; extensions
```

This appendix lists the file extensions of the different file types that
Reactis for C uses and creates.

## File Types Used or Created by Reactis for C

.c, .h
: C source and header files. Reactis reads these files but does not modify them.

.rsm
: Reactis build file. Stores information about how to compile and link C code for testing in
  Reactis for C.  See the [Reactis Build File Editor](build-file-editor) chapter for more information about creating build files.

.rsh
: Reactis harness Library. Stores test harnesses. Each test harness specifies
how the C code should be tested, such as the entry function, inputs, and
outputs. See the [Reactis Harness Editor](r4c-harness-editor) chapter for more
information about creating harnesses.

.rso
: Reactis object file. If **Create and use cache files for C code** is checked in **Edit > C Code** then Reactis will create a Reactis object file for each C source file in the code under test.

.rsld
: Dynamic library cache file. If **Create and use cache files for C code** is checked in **Edit > C Code** then Reactis will create a .rsld file for each dynamic library defined by a .rsm file.

.rsls
: Static library cache file. If **Create and use cache files for C code** is checked in **Edit > C Code** then Reactis will create a .rsls file for each static library defined by a `.rsm` file.

.rsi
: Reactis Info File. File created by Reactis for Simulink to store testing-related information for a Simulink model.  If using Reactis for C to perform back-to-back testing to check for conformance between C code and a model, then Reactis for C can inport information from the .rsi to create a C test harness.  This enables test suites to be shared between Reactis for C and Reactis for Simulink.

.rst
: Reactis Test Suite. Stores test data. Test suites are created by Reactis Tester. 

.csv
: Comma-Separated Value files. Simulator can import data from comma-separated value files into a test suite or export data from a test suite test suite to a comma-separated value file.

.rsp
: Reactis profile file. Stores information about previously opened build files, such as:

  * Error messages
  * Tester parameters
  * Watched variables
  * Scopes
  * Coverage highlighting settings

  Reactis automatically creates a profile file when a build file is loaded for the first time. The name of the profile file is equal to the build file base name, with extension `.rsp`. For example, if the build file is `cruise.rsm`, the corresponding profile file will be `cruise.rsp`. The profile file is stored in the same folder as the build file, unless specified otherwise in **Global Settings > Files**.

.rtp
: Reactis Tester parameter file. If the corresponding option in **Edit > General** is enabled, Reactis generates a parameter file every time a test suite is created via the Reactis GUI. The base name of the parameter file is equal to test suite file base name, with extension `.rtp`. For example, if the test suite is named `test1.rst`, the parameter file will be named `test1.rtp`. The parameter file contains all information necessary to re-create the same test suite, including a copy of all relevant settings in the current test harness library. Note that parameter files can only be used to re-create test suites within the same major version of Reactis. When using a parameter file with a different version of Reactis, the re-created test suite may differ from the original.

