We need to define proper release testing cycles when publishing new version of Nutrition Framework. Too many times have we run into releasing bugs that should have been caught.
Traditionally, it's been difficult to do it because the process cannot be automated. But it seems I have to take on the manual work of making sure everything is working on new versions.
We will use this issue to track how we can create a rigid test cycle and a suite of functionality to test for each shortcut involved in the framework
We need to define proper release testing cycles when publishing new version of Nutrition Framework. Too many times have we run into releasing bugs that should have been caught. Traditionally, it's been difficult to do it because the process cannot be automated. But it seems I have to take on the manual work of making sure everything is working on new versions.
We will use this issue to track how we can create a rigid test cycle and a suite of functionality to test for each shortcut involved in the framework