As denoted in this comment we should have a testing framework (at the xeus-cpp level or at the overall xeus-stack level) that would accept a kernel ( Maybe different xeus kernels and their different possible versions) and a demo notebook and return some jsons for confirming the expected outputs.
This would ensure consistency for the kernels over the long run.
As denoted in this comment we should have a testing framework (at the xeus-cpp level or at the overall xeus-stack level) that would accept a kernel ( Maybe different xeus kernels and their different possible versions) and a demo notebook and return some jsons for confirming the expected outputs.
This would ensure consistency for the kernels over the long run.