| Topic | Presenter | Summary | Duration |
| ------------------------------------------- | ------------ | ----------------------------------------------------------------------------------------------------------- | -------- |
| C4: Creating a New Systems Connector Part 3 | Johnathan L. | This video is the third and final part that briefly covers how to set up a new systems connector within C4. | 1:45 |00:00:07.920 --> 00:00:09.726 The final thing that you want00:00:09.726 --> 00:00:11.650 to do when you're creating a00:00:11.650 --> 00:00:13.612 new system connector for C4 is00:00:13.612 --> 00:00:15.839 create a testbed project for it.00:00:15.840 --> 00:00:18.192 Now, these are typically just simple00:00:18.192 --> 00:00:20.685 X unit projects which are added at00:00:20.685 --> 00:00:23.150 the same level as the ESM and types,00:00:23.150 --> 00:00:24.885 not projects within the same00:00:24.885 --> 00:00:26.273 repository and all that.00:00:28.750 --> 00:00:32.014 Then you just have a series of test00:00:32.014 --> 00:00:34.538 cases using typically test credentials00:00:34.538 --> 00:00:37.778 stored in a local Jason file.00:00:37.780 --> 00:00:41.284 There are helpers in the base test class.00:00:41.290 --> 00:00:43.880 Bug, which also the base test class00:00:43.880 --> 00:00:46.846 will give you this test output helper00:00:46.846 --> 00:00:49.950 stuff which will actually allow you to00:00:49.950 --> 00:00:52.766 capture all of the output of your test.00:00:52.770 --> 00:00:55.146 For example of the R0 logging.00:00:58.320 --> 00:01:00.567 Now this one doesn't actually use at00:01:00.567 --> 00:01:02.790 the moment, but over in Shopify we00:01:02.790 --> 00:01:04.740 see these fantastic reads for that.00:01:06.890 --> 00:01:08.954 So you just want to usually00:01:08.954 --> 00:01:11.249 try to write some test cases,00:01:11.250 --> 00:01:14.118 just basic stuff for different nodes.00:01:14.120 --> 00:01:15.736 It doesn't have to be anything too fancy,00:01:15.740 --> 00:01:17.964 because at the end of the day we're00:01:17.964 --> 00:01:19.720 talking about remote systems here.00:01:19.720 --> 00:01:22.408 Systems are always going to be a little00:01:22.408 --> 00:01:24.757 heart rate of battery of tests for.00:01:24.760 --> 00:01:27.328 Just try to make sure you have something00:01:27.328 --> 00:01:29.726 that's just goes through some of the00:01:29.726 --> 00:01:31.920 common cases as you're testing things.00:01:35.320 --> 00:01:37.840 Obviously I felt full pipeline00:01:37.840 --> 00:01:40.360 is usually the best tester.00:01:40.360 --> 00:01:43.016 But these are just for know level things.