Designing Tests - Cloud - 8.0

Talend Software Development Life Cycle Best Practices Guide

Talend Big Data
Talend Big Data Platform
Talend Cloud
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend JobServer
Talend Management Console
Talend Remote Engine
Talend Studio
Administration and Monitoring
Design and Development
Last publication date
While designing the processes (Jobs and Routes), developers need to think of how to test them: Talend recommends you to use the Test Case feature: it automatically creates a Test Case with a skeleton in a Test Instance.

A Test Case is an executable test that consists of an immutable part extracted from the initial Job or Route, along with other editable components that form the skeleton of the Test Case.

A Test Instance is a set of data that allows you to run the Test Case with different parameters that you define (input, reference files, etc.).

Note: When building and deploying your project, Test Cases will be generated as JUnit files and thus will be built before the packaging Maven phase.
Best practices:
  • It is recommended to create and use a context adapted to your environment (a Test context to execute test Jobs and Routes with the metadata of this environment, and a Production context to execute Jobs in the Production environment).

  • When the feature is designed and tested, it is recommended to use the Talend Artifact Repository (Nexus, Artifactory) to publish items and retrieve them in the QA and Production environments via the Talend Cloud Public API. See Deploying to QA and Production environments for more information.