tod | A simple command line todo manager | Command Line Interface library

There are some issue with your code:

1. Required Fix: You can only bind to public properties and not fields. This means insumos must be a public property. Additionally the binding source, in this case the InsumosViewModel and the InsumoVM classes, must implement INotifyPropertyChanged (see Microsoft Docs for complete example) - even when you don't expect property changes.

InsumoVM.cs

Here I tried to reproduce your graph. The pattern of my ggplot graph and your Excel graphs are high similar, but I'm not sure what y-axis values are you using, the values range from 0 to 40 is not present in your dput().

You have to model a route which enriches the first web service result with the second one. The way you merge both responses has to be specified in your AggregationStrategy instance.

See the enrich EIP: https://camel.apache.org/components/3.14.x/eips/enrich-eip.html

the action "on exit" of the delay block occurs AFTER the selectOutput condition calculation, so if you change the value of your probability on the on exit action, it's too late... This is counterintuitive in anylogic but things happen in the reverse order of the flow... which is weird, but it is like that

So calculate it in the "on at exit" action instead, and everything will work

Use requestBodyAndHeader instead of sendBodyAndHeader so you get the response as return value and then you cans assert it.

See https://camel.apache.org/manual/producertemplate.html

Append -B to your command. Example: grep -i authorization -A4 -B4

It looks like you set the target filename into the header filename. Then you use it in the URI.

If you use the header name CamelFileName instead you can omit the fileName option from the URI because this is the standard header name of Camel and therefore used automatically if nothing else is overriding it.

You can try setting the throwExceptionOnFailure option to false. Http components in camel have this enabled on default, probably so that failures can easily be caught and handled like any other exceptions in camel.

When its enabled you can get the Exception and details about the exception through Exchange properties which in this chase you can probably cast to NettyHttpOperationFailedException to get more information about it.

Already provided you with some answers in your other question. Even added some code examples there to help testing routes with files albeit using more generic CamelTestSupport instead of Spring annotations.

Key thing to understand when writing camel unit tests is that you should focus on testing your routing logic not camel components. People maintaining camel have already written bunch of unit tests for camel and most if not all its available components.

To avoid over-complicating unit tests its good to understand different levels of testing along with their scope and purpose.

1. Unit testing
2. Integration testing
3. System testing
4. Acceptance testing

You can find more information about them from various online articles as well as from wikipedia.

There's usually not much business logic to test when it comes to routes that just send a file to blob storage or something similar. What you should test is that the azure-storage-blob endpoint actually receives the file. Additionally you may have business requirements requiring you to validate the file before sending (i.e are the contents valid, does the file/blob name follow required naming convention etc.)

1. Test that azure-storage-blob endpoint receives file
2. Test that azure-storage-blob endpoint receives valid data.
3. Test that route logs error or throws proper exception when it does not.
   • If monitoring is in use its possible that the error message needs to be in some specific format for alerts and whatnot to work.
4. Test that invalid data does not get send to the azure-storage-blob endpoint
5. Test that connection errors with azure logs error or proper exception.
   • These are very helpful for system and integration testing that can be done later if there are problems with integration configs, firewalls and whatnot.

Since your route has some dependencies like headers:

• CamelAzureStorageBlobSourceBlobAccountName
• CamelAzureStorageBlobContainerName
• CamelFileName

You could test that:

1. azure-storage-blob endpoint receives these headers when given
2. route logs error or throws proper exception if any of these headers are missing.

For these tests you can use use adviceWith and weave to replace the azure-storage-blob endpoint using weaveByURI or weaveByID and replace.