patrickkaleta
commented
4 years ago Status report:
I decided to implemented a Testing service, which is triggered in each Cron run. It either triggeres Emikat to start the calculations or it checks if results for the calculation are available.
- Once a day this service will trigger Emikat to recalculate this test study (study itself will not contain any changes, to ensure test conditions are always the same).
- During every other Cron run (happen every 3 hours) the service checks if there are results available (should always be the case, since calculations take around 10-15 minutes and results are checked at the earliest 3 hours after Emikat was triggered).
ATM the current batch jobs and the table for HC local effects are tested. I want to add tests for the EE and RIA tables as well. Then I will deploy this feature (should be done by end of this week).
Important note: We are only testing if updating a study still works. We are not testing if adding new studies is working, since that would generate a lot of junk studies on both sides!
@DenoBeno suggested that we should have some kind of automated testing, that would on a regular basis check if the communication between CSIS and Emikat is working and if Emikat produces results.
I suppose one way of how we could achieve this is by creating a custom service in our csis helpers module. That service could be called either by accessing a specific URL or triggered by a cronjob (might be better to instead use a queue as shown here).
Example of how to build a service here and here.