Important thing which missed to add in post is , we do maintan notebook code as .scala under resources and maitian in github. Files(.scala) from resources gets deployed as notebook using github action.
With my approach of moving under package, I will have to go with new apporach for deployment(use my action copy the .scala files under my pakage --> github action --> notebook), instead of my older apporach (resources --> then action --> notebook).
With my new apporach I was able to somehow manage write test case and cover it, but there are certain difficulties with my new approach where some of hte notebook native commands(run etc) are not being able to test
With this I am trying to do test my notebook code and as well deploy as notebook and continue to be interactive.
In order to avoid certain diffculties with my new approach, I was trying to look for some ideas that would cut my time