Test the Blueprint itself
novusnota opened this issue · 7 comments
Otherwise we have a very peculiar example of a testing framework, which doesn't spot no tests itself. They would help uncover much more bugs than trial-and-error approach.
@novusnota Could you expand on what you mean here? A testing framework for a general purpose language that does not test itself sounds a bit like nonsense, indeed. However, Blueprint is a tool to help with testing DSL programs (smart contracts) and not general purpose programs.
@anton-trunov for example, it could have e2e CI tests with Tact and FunC: to create new projects, change compiler versions, and check that everything builds and tests.
Because as of now it's somewhat annoying to debug the Blueprint in a pipeline, especially when the target OS is inaccessible:
@novusnota that's more or less issue #115
Yup, but there are unit tests too, which can help make sure (or at least more confident than before), that the internals work fine
Unit tests are double-edged things -- they can sufficiently slow down project development by unnecessarily fixing its internal structure. End-to-end tests are something that I personally would prefer.
I guess this one can be closed indeed. But please do could share some more concrete suggestion in #115