I follow Talend Lab and the following video to build Test Case. https://www.youtube.com/watch?v=Ygeg8Xt1x88 It works, but I fail to understand when to use this TESTCASE feature in the development cycle.
Scenario 1: Automatically run Unit Tests in Step 5 of this Talend CI procedure.
"Step 5 Run Tests
Scenario 2: Implement Test driven development.
Take my example, generating input_file1/input_file2 and reference_file1 first before developing the component tMap_1.
Scenario 2 makes a bit more sense. I'm struggled to find how Scenario 1 will work in the real life.
* Developer develops the job, and create many TESTCASE on each key component ;
* TESTCASE can only apply single component. If developer modifies the logic of one component, developer must modify all three files accordingly. Otherwise, TESTCASE will fail. If no logic is changed within this component, surely the TESTCASE will success.
In Scenario 1, what are the benefits from TESTCASE to justify the extra work?
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Part 2 of a series on Context Variables
Learn how to do cool things with Context Variables
Find out how to migrate from one database to another using the Dynamic schema