# Example of Test case based on a Route

A Route called route\_file is created in a project called ci\_project. The Route aims at reading a file before converting its content to String rows, splitting it line by line and outputting the result in a log file.

![](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/Resources/images/sdlc-route_test_case-studio_repo.png)

The processing part (cConvertBodyTo and cSplit) is used to create a Route Test case called test\_route\_file and cMock components are used to simulate message generation and message endpoints, allowing developers to test and map any types of input and output messages.

![](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/Resources/images/sdlc-route_test_cases.png)

Note that the generated skeleton depends on the components selected in the Route to create the Route Test.

![](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/Resources/images/sdlc-route_test_cases_created.png)

Here, the Test case aims at:

* generating test message exchanges and reading input test data (cTimer and cMock\_1 components)

* transforming data with an immutable set of components (INPUT and OUTPUT items) based on the initial Route

* checking that messages have been routed as expected and validating the Test output result (message content, count, header, etc.) using the cMock\_2 component

Note that you can add as many instances of tests as you need, which means you can run the same test with different input and reference files.

The Test Case is ready to be executed once the data set has been defined in the Test Cases view. The data set consists of data files that you define as input and reference files to test your data.

![](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/Resources/images/sdlc-executing_route_tests-run_in_studio.png)

The Route Test Case was successfully executed on the Test Instance and the input and reference files are identical.

The Route Test Case was successfully executed on the Test Instance and the input and reference files are identical.

Once developers have designed the integration tests locally in Talend Studio, these tests need to be automated with continuous integration tools such as build systems. For more information, see [Building and Deploying](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/ci-build).