Skip to content
Snippets Groups Projects
Commit c70fc28d authored by balaskoa's avatar balaskoa
Browse files

Fix some broken links in UG


Signed-off-by: default avatarbalaskoa <Jeno.Balasko@ericsson.com>
Change-Id: Ib258ef878dc97d9e7b8ba1009cf23c4dfe8476dc
parent de9d0714
No related branches found
No related tags found
No related merge requests found
......@@ -37,7 +37,7 @@ image::images/titanexecutor_structure_x.png[title="Titan structure"]
Creating a TTCN–3 test suite involves building an executable from the initial modules (TTCN–3, ASN.1 or both) and test port files. The process basically comprises creating and modifying a `Makefile` and using the `make` command to build the executable.
For detailed information, refer to <<3-creating_executable_test_suites_from_the_command-l.adoc, Creating Executable Test Suites from the Command-line>>.
For detailed information, refer to <<3-creating_executable_test_suites_from_the_command-l.adoc#creating-executable-test-suites-from-the-command-line, Creating Executable Test Suites from the Command-line>>.
== Executing Test Suites
......@@ -45,4 +45,4 @@ After the test suite has been created a suitable configuration file has been bui
The test executor can operate in single or parallel mode. The single mode—also called non-parallel mode—is thought for TTCN–3 test suites built around a single test component. It is forbidden to create parallel test components in single mode: the test suite is not supposed to contain any `create` operation otherwise the test execution will fail. The parallel mode, on the other hand, offers full-featured test execution including distributed and parallel execution. The goal of introducing the single operating mode was to eliminate redundancies and thereby increase the speed of execution. It is possible to execute non-parallel test suites in parallel mode, but doing so results in unnecessary overhead. The {cpp} code generated by the compiler is suitable for both execution modes, there are no command line switches to select mode. The only difference is that different Base Libraries must be linked in single and parallel modes.
For detailed information on executing test suites in single or parallel mode, refer to <<4-executing_test_suites.adoc, Executing Test Suites>>.
For detailed information on executing test suites in single or parallel mode, refer to <<4-executing_test_suites.adoc#executing-test-suites, Executing Test Suites>>.
= Creating Executable Test Suites from the Command-line
[[creating-executable-test-suites-from-the-command-line]]
= Creating Executable Test Suites from the Command line
This section describes the elementary commands that comprise the build process. The primary audience of this section is the group of users who want to integrate TTCN–3 to a new or an existing build system.
This section describes the elementary commands that comprise the build process.
The primary audience of this section is the group of users who want to integrate TTCN–3 to a new or an existing build system.
== Using `make`
......
[[executing-test-suites]]
= Executing Test Suites
This chapter describes the modalities of test suite execution.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment